-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All in a sudden Functions compilation in Visual Studio fails with exception #139
Comments
From @tohling on November 13, 2017 19:0 Could you add an explicit reference for Newtonsoft version 9.0.1 and see if the error goes away? |
From @ChristianWeyer on November 13, 2017 20:32 Thanks for this idea. Yep, tried that. Same result. After further investigating, I found my issue is similar to this one: |
@ahmelsayed did you ever resolve this? I just ran in to this too but haven't been able to identify the right fix to resolve it. |
Hello, I have exactly this same error in my .NET 4.6.1 Azure function project, but it's really not clear how I should fix it.
Can anybody provide a simple explanation how to fix this? |
@Yvand I tried the binding redirect too but it didn't help as I believe the error is happening at runtime for the function generator and not in your components. If you see my referenced comment above I basically had to go through the changes line by line to find the offending code (in my case it was refactoring some azure auth code to a shared method) and remove that code. There may be other methods but that painstaking one was the only one I found which resolved this in my instance. |
HI @scottcha, aahh ok, thank you. |
@Yvand I had a similar issue. I moved all "my" code (not the functions) into a separate project. What also worked was changing the access modifier of "my" classes (not the functions) to internal. Both approaches solved the problem for me. |
@cschwendtner Moving my code to a separate class library project mitigated the problem for me. Thanks! |
fixed by @cschwendtner in #151 Please update to |
I'm still getting this issue with 1.0.8 on .NET Standard 2.0. (Functions V2). Severity Code Description Project File Line Suppression State WRN: Assembly binding logging is turned OFF. Error generating functions metadata I will try the work around now. I'm a bit confused how my function can call my code in other project if I mark it all as internal? Thanks. EDIT: Even an empty .net standard 1.08 project will not compile. Downgrading to 1.07 is the only option right now. |
@Moffmo - The fix in #151 / Compiling an empty Azure Functions V2 (netstandard2.0) project (with The workaround (that was described in this comment) is changing the access modifier of "your" classes (not the functions) to |
I'm getting the same issue. Created a StackOverflow for it. StackOverflow link |
From @ChristianWeyer on November 12, 2017 20:57
Hi all,
Did anybody ever see this?
I have a .NET 4.6.1 project. Everything worked fine - util a certain point.
From one moment to the other I get this exception:
I restarted VS, no help.
Any idea?
Thanks!
Copied from original issue: Azure/Azure-Functions#586
The text was updated successfully, but these errors were encountered: