Visual Studio 2026 Support

[MichaelKoster70]

Add support to install this plugin in Visual Studio 2026

• Migrate the Plugin Options to the new VS 2026 editor experience
• Upgrade CPS to v18

[softworkz]

Not needed. VS 2026 takes plugins targeting 2022 without needing any change (for the first time i VS history).

[MichaelKoster70]

While technically not needed, the underlying VS project system might have additional capabilities available that the plug in could use.

[softworkz]

the underlying VS project system might have additional capabilities available that the plug in could use.

Ah right, yes of course.

Not a 17 vs 18 matter, but in this context, I've been wondering whether it might be possible to use the connection definitions from Visual Studio's ConnectionManager (Settings >> Cross Platform >> Connection Manager).
This would unify connection definitions and you could also make the "Remote File Explorer" part of the extension features.

Have you ever looked into that?

There's a cli interface for management (C:\Program Files\Microsoft Visual Studio\18\Enterprise\Common7\IDE\VC\Linux\bin\ConnectionManagerExe\ConnectionManager.exe) - but using the connections is probably a different story.

[MichaelKoster70]

Using the vs connection manager was one of the first things I tried to use.

In order to use it, I would need a officially documented API for the connection manager.
Looks like as this is internal to VS.

I am not a fan of using undocumented features. That why I abandoned that idea for now

[softworkz]

I am not a fan of using undocumented features. That why I abandoned that idea for now

One could argue that in the area of VS Extensibility and the CPS, it can get pretty hard to get along when waiting for a documentation for everything. From my experience, there was always some part of reverse engineering involved - not necessarily for doing "forbidden" (unintended) things - in most cases just in order to find out how things are supposed to be done... :-)

But of course I get what you mean. Though....

....an API might not really be needed (other than the CLI tool for management), because - you can just read the configuration file:

C:\Users\admin\AppData\Local\Microsoft\Linux\User Data\3.0\store.xml 😛

(it's just some idea, though, not really important)