-
Notifications
You must be signed in to change notification settings - Fork 158
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
Reference documentation generation with CSharp Extension methods fails #201
Comments
Interesting, I don't even get an exception, but extension methods don't appear on the docs: #156 |
I'm still seeing this btw on various occasions maybe I take a closer look in the future... |
I noticed that this only happens when the project with the extension methods (the code from the initial post) is build against net45 (and not when build against net40). Another note: You can workaround this with |
Ok after countless hours of testing and debugging I think I figured this one out. Strictly speaking this is no bug in FCS, as it happens if we use the net40 reference assemblies in combination with an assembly compiled against net45 in the Now to the FSF issue: Ideally we would look at the assembly we currently want to analyze and use the matching reference assemblies, however I didn't found an ideal way to do this:
Currently I just updated the reference assemblies to use the 4.5 ones, this seems to fix the problem temporarily (but this or other problems may come back sooner or later considering 4.0, 4.6, 4.5.1, 4.5.2 and so on). (However, I could not reproduce this exact problem with later versions and 4.0 assemblies work as well). /cc @tpetricek Do you think just updating to 4.5 is fine for now? Should we go into any of the solutions mentioned above? Is there someone who could help me with the FCS API (I don't think this is a use case the API was designed for, but we wouldn't need another dependency)? |
… Fixes crash with C# extension methods when the assembly containing them was build against net45. Fixes #201. (Might fix) Reference
When a function and a module is marked with the System.Runtime.CompilerServices.Extension attribute, for example
exceptions like the following appear while generating the API reference documentation:
The text was updated successfully, but these errors were encountered: