Why not have the NSwag studio as an extension to VS

RicoSuter / NSwag

The Swagger/OpenAPI toolchain for .NET, ASP.NET Core and TypeScript.

http://NSwag.org

MIT License

6.77k stars 1.29k forks source link

Why not have the NSwag studio as an extension to VS #548

Open weitzhandler opened 7 years ago

weitzhandler commented 7 years ago

It should be a lot easier if it's part of Visual Studio as a VSIX. The entire generation process could be automated easily. It could be integrated with the project/solution settings in Visual Studio. Defaults configuration can be set right from VS' options.

RicoSuter commented 7 years ago

There are currently no plans for a Visual Studio extension. First it is a big pain to build VS extensions (compared to a simple WPF UI) and second I just don't have the time to also support a VS extension without being paid for it... :-)

weitzhandler commented 7 years ago

An extension is plain WPF... But I feel you! And thanks for your time and effort for everything you achieved so far it's great!

RicoSuter commented 7 years ago

True, but if we build a VS extension then it should bring more feature than just the standalone NSwagStudio application. For example it should integrate in the project system, so that you can add NSwag to an existing Web API project, or provide context menu on the client project to regenerate the code... maybe we also need project templates for better and simpler integration.

RicoSuter commented 7 years ago

Maybe an extension with the binary and context menu to create and run an nswag.json file in a project?

Bundle binaries or install NPM module (npm install -g nswag)
Context menu for
- Add nswag.json to project
- Run nswag.json of a project
- Open nswag.json with JSON Schema editing (how?)

weitzhandler commented 7 years ago

Yes. That would be a great starting point indeed.