Actually it works with my static Web API, as I wrote before. With dynamically created Web API, Swagger only generate following docs:
GET - /api/AbpServiceProxies
POST - /api/AbpServiceProxies
GET - /api/ServiceProxies
POST - /api/ServiceProxies
I spent many time with configuration of Swagger, but I was unsuccessful with dynamic Web API. Maybe someone will figure it out with help of tutorials I posted before.
Hi, maybe this will help you:
<a class="postlink" href="http://bitoftech.net/2014/08/25/asp-net-web-api-documentation-using-swagger/">http://bitoftech.net/2014/08/25/asp-net ... g-swagger/</a> <a class="postlink" href="http://www.strathweb.com/2014/04/opt-opt-asp-net-web-api-help-page/">http://www.strathweb.com/2014/04/opt-op ... help-page/</a>
I followed these manuals and the Swagger is fully functional for my Web API. It should work for you too.
Hi, I changed this method to "normal" sync method and I tested it again. But, the error is the same. I think this is not only problem of an async implementation, there may be a global problem (somewhere deeper in the ABP framework code) to catch exceptions right way.
I'm using Multi Page Application, not Angular, Durandal, etc. Please test this example and you should get the same result.
Thank you.
By the way, this framework is great, it saved me a lot of time, I appreciate all of your work, keep going...
Yes, customErrors is set On. It was a first thing I changed.
It works in PostInitialize section. Thank you.
I solved it. It was really simple, just one line of code to add a new menu
context.Manager.Menus.Add("TopMenu", new MenuDefinition("TopMenu", new FixedLocalizableString("Top menu")));
In your code is it exactly same as my solution, thank you for help.