Closed Phiph closed 9 months ago
Hi @Phiph, A work around right now is to build the Dapr extension repo in local which will generate a Microsoft.Azure.WebJobs.Extensions.Dapr.99.99.99.nupkg
in a folder path\to\azure-functions-dapr-extension\local-packages
.
Edit the ~/.nuget/config/*.config
file as shown below.
<packageSources>
...
<add key="nuget.local" value="path\to\azure-functions-dapr-extension\local-packages" />
</packageSources>
Hey @ASHIQUEMD I think that won't work as the way the Host creates this Dynamic csproj file in the temp directory means that doesn't honour the solutions nuget.conf folder.
Have a look at the PR I've created - I've included some analysis and linked up the issues in the Azure/azure-functions-dotnet-worker repo :)
@Phiph Thank you for the PR, I will have a look at it.
To unblock you immediately without making change to WebJobs library, the steps I mentioned should work for you.
I also faced same issue in my local machine while validating 0.16.0-preview01
, this happens only when we use nuget generated in local. Unless we have to debug something, recommendation is to use published nuget package.
This is how my nuget.config looked like earlier.
After building the Dapr extension project, I modified the nuget.config
And build succeeds after that, I hope this helps.
Cheers @ASHIQUEMD I'll give that a go. I agree my PR is a hack and a temporary work around.
I really appreciate you taking the time to prove your method works, I'll give it a go next week. Thank you!
@ASHIQUEMD @rabollin thanks - I also got my .NET Functions working with this workaround - I assume this is not the permantent solution, right?
Hey @KaiWalter it's been fixed in the upstream package. I've linked the PR to their PR with the fix, it's just awaiting release.
I've asked when it's planned :)
That is correct, it is fixed in upstream and the final DAPR extension bits are getting deployed to production.
@ASHIQUEMD @rabollin thanks - I also got my .NET Functions working with this workaround - I assume this is not the permanent solution, right?
Cheers @ASHIQUEMD thanks for the tip it worked!
If anyone stumbles across this before the patch, bear in mind you need to change your profile nuget.config, not your project level config :)
facing same error with version 0.17
@MarekLani Can you please share the error details?
getting very same error as in the title of the issue: Unable to find package Microsoft.Azure.WebJobs.Extensions.Dapr with version (>= 99.99.99), when I build the package myself and instruct nuget to check for local packages, it of course works.
Hi Team,
I'm just doing an experiment with getting Dapr running with a function app Pub/Sub. I don't think Tye supports function apps + Dapr yet, but that's for another day!
When I use version
"0.16.0-preview01"
my build fails with the below output.If you want to have a look at what I'm experimenting with the source code is here:
https://github.com/Phiph/dapr-azure-functions
I am building on MacOs 13.6 M2 arm64
Here is the build output for my project: