Opening Visual Studio 2019 solution issue

[paladin]

Connecting to a vs 2019 solution project I'm getting 'Cannot find Visual Studio install path for version: 17'.
Removing the se generated artifacts recreating the workspace files from scratch does not help.  No issue building the solution in VS

[Clark]

It sounds like SlickEdit is trying to configure your build environment for Visual Studio 2022 and it's failing. Is this what you want or do you want SlickEdit to use Visual Studio 2019?

[paladin]

2022 is not installed and the solution space is built with 2019. I must be missing something fundamental in the setup. I need it build using VS2019

[Clark]

Something is definitely a little off.

Try to execute this command:

Code: [Select]

"c:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe"  -utf8 -all -prerelease -requires Microsoft.Component.MSBuild -format xml

If it works, redirect the output to a file and post the file here.

[paladin]

Results Attached

[Clark]

This output is definitely good. Something else must be going wrong. At the moment, I'm thinking it might be your configuration.

Try a default config:

Code: [Select]

vs +new -sc c:\temp\new-config-dir

There is a sample Visual Studio 2019 project you can test with.

Project>All Workspaces...>Sample Workspaces>VS2019.sln

If you are able to open this sample Visual Studio 2019 solution, then try yours. Depending on what happens here hopefully I'll have a good idea of what the problem is.

[paladin]

Opened the sample -- no issues. 
Open my my solution -- no issues.
I updated to beta 3 the other day and just double checked -- I'm still seeing the issue when use the default desktop link on my original solution but not on the Slickedit sample workspaces/vs2019.sln

[Clark]

Please post your user.cfg.xml for your problematic config. I need to look at some settings.

[paladin]

attached

[Clark]

I'm not seeing any configuration items that might effect opening a Visual Studio solution. At this point, I suspect it's something in the .sln file that is confusing SlickEdit.

Try setting the macro variable def_use_visual_studio_version to 16. This will tell SlickEdit to use Visual Studio 2019 when opening Visual Studio Solutions. Macro>Set Macro Variable...

[paladin]

setting the macro eliminates the warning during startup.

[Clark]

Great. Glad that works.