Swashbuckle.AspNetCore: AddSwaggerGen broken with the latest ASP.NET Core 1.1
ASP.NET Core 1.1 was released yesterday and it broke SwashBuckle. What are the chances of getting it fixed soon? Reverting back to an old ASP.NET Core is a discouraging concept.
)
In ConfigureServices I have
services.AddSwaggerGen
That line generates the following exception:
FatalExecutionEngineError occurred HResult=-2146233082 Message=Exception of type ‘System.ExecutionEngineException’ was thrown. InnerException:
Additional information: The runtime has encountered a fatal error. The address of the error was at 0xca2b3c23, on thread 0xcf8. The error code is 0xc0000005. This error may be a bug in the CLR or in the unsafe or non-verifiable portions of user code. Common sources of this bug include user marshaling errors for COM-interop or PInvoke, which may corrupt the stack.
I would be very grateful for any indication on what to do with this!
Thanks
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 18 (1 by maintainers)
Swashbuckle is component-based, consisting of 3 different packages (all described in the readme).
If you want the generation functionality, then you need to include the following package:
Swashbuckle.AspNetCore.SwaggerGen
@gcsuk I found that all I had to do was delete my bin and obj project folders, clean the solution and rebuild it and it seemed to pick those references up just fine!
Hi again,
Just wondering if anyone is going to address this? The solution offered (adding Microsoft.NETCore.App) does not work - I am targeting .NET Framework 4.6.1 and it says that Package Microsoft.NETCore.App 1.1.0 is not compatible with net461.
Is there anything I can do to resolve swashbuckle working wtih ASP.NET core 1.1.0 targeting framework 4.6.1?
Thanks,
Ian
I am using it in a couple projects with VS2017 and the latest .NET core with no issues. If you wish, you can put a project on GH and I’ll take a quick look and see if I can spot the problem…