@connormahern-MW I don't think this plugin is maintained anymore - and I don't think @madskristensen looks at the issues - or is simply too busy.

I ended up moving to Rider, because web development using modern techniques, that is not Blazor, is sub-par in Visual Studio (non code) - so I have not used this plugin since.

I think the better solutions is, for someone to fork it, and make an updated plugin - or just give up and use something better for web development, than Visual Studio - as I think that web developers using modern frontend toolchains, is not really the priority group for the full Visual Studio - as most of them is using Visual Studio Code.
The Visual Studio team is doing a great job - but they just have to prioritize - and MS already makes the most popular editor for web development. (vscode)

@madskristensen Is it an idea to make a note on the repository that this plugin has reached end-of-life? Maybe that will spark a main fork, that can add support for 2022 and beyond? If you have the time, then if you can give someone some notes about what have to be done to the plugin, to make it compatible with 2022 - then that would properly make it way easier for someone to take over.

Add support for Visual Studio 2022:( #36

Description

Description

Current behavior

Expected behavior

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions