-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Nuget package is tied to AutoFac 4.0.0 #2
Comments
Hi richardacre, actually, the definition in .nuget should lead to let you use any version above or equal to 4.0. Have a look onto the nuget spec.
Can you add some more detail about your exceptions/ loading issues you get? I can add a new functions project, reference autofac 4.6.1 and add the nuget package without any issues. |
I've got a solution with multiple projects in, all referencing AutoFac 4.6.1 which builds fine. If I add a reference to AutofacOnFunctions to one of them (my Functions project) and try to build it I get a build error like "AutoFac , Version=4.0.0, or one of its dependencies. The system cannot find the file specified." . I'll continue to investigate, it may be VS2017 being a pain. Edit: Fixed it I had to upgrade Microsoft.NET.Sdk.Functions to v1.0.14 This is what my project.assets.json has come out like, note AutofacOnFunctions is still saying it wants 1.0.13 and 4.0.0
|
AutofacOnFunctions uses Azure Functions v2 based on .net standard. V1 can be used with .net framework. Which one do you use? |
We're using .Net Core so it'll be V2 |
I double checked your project.assets.json with mine and cannot see any difference. Can you put a screenshot or a sample project anywhere that I can reproduce this with your code? |
I have the same issue (see below). The code is quite sensitive to share, but let me know what info can help and I'll try to provide it. Thanks in advance!
File name: 'Autofac, Version=4.0.0.0, Culture=neutral, PublicKeyToken=17863af14b0044da' WRN: Assembly binding logging is turned OFF. Error generating functions metadata |
FYI: When I add your v2 project directly into my solution and link it up that way it works. |
Sorry for late answer, had been on vacation last two weeks. Thanks for letting me know. Do you have this issue locally as well as when being deployed to azure? |
Can you try with latest version and check if it works? |
Closed due to no interaction anymore on this. |
Hello I have come across the same issue. It works when I have Autofac 4.0.0, but as soon as I update to 4.8.1 I get a build error. I assume it must be something related to binding redirects, but don't think you can do that on azure functions. I am attaching a small project where you can see this happening. |
thanks @magoicochea will have a look onto your sample 👍 |
Finally this issue described in Azure Functions had been solved in Azure Functions v2 GA. redirects in Azure Functions |
It needs to target >=4.0.0 as the reset of my project is on 4.6.1
The text was updated successfully, but these errors were encountered: