Visual Studio 2019 solution support

[rjpontefract]

Hi

I've had to upgrade to MS VS2019 and SE pops up a dialog for each project in the solution saying it can't determine the version number.

Is support for opening VS2019 solutions on the roadmap?

[Lee]

Yes, support will continue for Visual Studio.  Several changes are required for Visual Studio 2019, they are moving away from the old way of how we detected older versions and product paths.  They have tools and API's for the new way going forward, but the changes are far too much for a hotfix or even a point release.  SlickEdit version 24 will have this included later this year, and will go through the usual beta test cycle.

We may need to issue a v23 hotfix to mute the warning specifically for Visual Studio 2019 for the early adopters, but would still require manual setup of environment settings for builds and manual tagging of the 2019 standard libraries.

[rjpontefract]

Thanks.  A hot fix that mutes the warning would be very much appreciated so that I can load import the workspace and navigate the code.  I have no problem doing manual configuration and tagging.

[rjpontefract]

Is there any chance of a hot fix for this?  Having to hit enter or click OK for 50 plus projects in a workspace is making SE less joyful to use.

[bengle]

I would like to add my vote for a v23 hotfix for this.

[Graeme]

If the following is the message you get then you can comment it out and reload the macro file with the load module command on the macro menu.  It's in wkspace.e

      _message_box('Unable to determine Visual Studio year from version='Version);

By the way, I found this by searching for "determine" with plus or minus two before/after lines, then searched the results for "version" - just in case the word "version" was on a different line to/from the word determine.

[Lee]

Changing this for next hotfix to a one-time prompt followed by passive warnings about unsupported new Visual Studio solutions.

[rjpontefract]

That's great to hear, thanks.