This extension allows to create a .NET Core 3.1 REST API ready to use solution taking into account:
- DI according to .NET Core 3.1 practices (without external dependencies)
- exception handling settings according to .NET Core 3.1 practices
- mapping settings (based on Automapper)
- OpenAPI basic configuration (can be enabled/disabled by configuration)
- API Versioning (based on URL routes)
- automatic OpenAPI versioning according to code
- XML Comments included in Swagger
The created solution is layered according to business practices in order to make it ready to be used in "real life".
You will find here the .NET Core 2.x version.
Besides the .NET Core 3.x upgrade, this version includes many improvements.
A new .NET 5 version has been released here (preview).
You will find more information about how to install and use the extension following the link below:
(sorry for omitting the hyperlink to the post. Recent updates in the marketplace do not allow certain types of external references. Blog posts are being migrated to avoid the issue.).
In addition to this Visual Studio version, you can find here the .NET CLI version.
- code comments (XML Comments type) at DataContract level are included in the Swagger/OpenAPI generation.
- fix related to AppSettings not being loaded properly by DI (thanks Devwulf for having reported the issue).
- default file opened at the editor level
- default Unit Tests samples included at controllers level.
- bug fix on XML comments file
- End of preview after the last "rc" dependency upgrade (Swashbuckle).
- Small fixes on tags and project metadata.
- .NET Core 3.1 upgrade.
- all dependencies upgrade (last available version).
Microsoft.AspNetCore.Mvc.Versioning and Microsoft.AspNetCore.Mvc.Versioning.ApiExplorer have been upgraded from preview to 4.0.0 release version. Swashbuckle.AspNetCore packages remain in "rc".
- Versioning has been aligned with .NET Core version
- API returns JSON-based exceptions
- XML comments have been improved to go deeper in specifications (return types descriptions, etc)
- the API produces JSON by default
- global error management and logging based on two alternatives (documented in the code)
- small fixes