search

holgerleichsenring / AutofacOnFunctions

Azure Function Autofac Integration
MIT License
11 stars 8 forks source link

Boostrapper Fails When Autofac is Upgraded #8

Closed oh-yeah closed 6 years ago

oh-yeah commented 6 years ago

Problem: Upgrading Autofac to any version greater >= 4.7 causes an error in the bootstraper.

Steps to Reproduce:

Error Message Method 'CreateModules' in type 'AutofacOnFunctions.Samples.Bootstrap.Bootstrapper' from assembly 'AutofacOnFunctions.Samples.NetStandard, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' does not have an implementation.

holgerleichsenring commented 6 years ago

thanks for adding, will have a look.

holgerleichsenring commented 6 years ago

Actually, I could reproduce this issue with azure functions sdk 1.0.21. This is a known issue in Azure Functions. redirects in Azure Functions. The article claims that with Azure Function GA it should be solved.

holgerleichsenring commented 6 years ago

Unluckily it looks like it is not sufficient to just reference GA version (1.0.23). nuget package must reference webjobs 3.0.0 instead of rc1 for some reason. I'll update it an add a new nuget package soon.

holgerleichsenring commented 6 years ago

nuget package 1.0.14 had been uploaded, sources adopted, please give it a try.

NinjaSciurus commented 5 years ago

The issue is again (or still) present in the current version 1.0.14 (using Autofac 4.8.1, functions SDK 1.0.24 and webjobs 3.0.0) on netstandard2.0. Do you have any information regarding breaking changes (either in AutofacOnFunctions or its dependencies)? I have searched around on this error but I only find old and obsolete articles.

UPDATE: my fault, I had the Autofac 4.8.1 nuget explicitely installed. Removing this results in AutofacOnFunctions using its default version (4.0.0) and it works. Thanks for your work! :)

holgerleichsenring commented 5 years ago

oh, thanks, @NinjaSciurus. I was just scared that MS did some "fancy" stuff to azure functions that let the issue come up again. :-)