Conversation
Note: VSIXManifest needs manual change depending on Version.
UnityMixedCallstack.csproj
Outdated
| <VSToolsPath Condition="'$(VSToolsPath)' == ''">$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v$(VisualStudioVersion)</VSToolsPath> | ||
| <!-- <VSSDK140Install Condition="'$(VSSDK140Install)' == ''">$(MSBuildProgramFiles32)\Microsoft Visual Studio 14.0\VSSDK\</VSSDK140Install> --> | ||
| <VSSDK170Install Condition="'$(VSSDK170Install)' == ''">$(MSBuildProgramFiles32)\Microsoft Visual Studio\2019\Professional\VSSDK\</VSSDK170Install> | ||
| <VSSdkPath Condition="'$(VisualStudioVersion.Contains(`17`))'">$(ProgramFiles)\Microsoft Visual Studio\2022\VSSDK\</VSSdkPath> |
There was a problem hiding this comment.
For me this is in: C:\Program Files\Microsoft Visual Studio\2022\Professional\VSSDK -- what version of VS are using?
There was a problem hiding this comment.
I installed 2022 Professional to a custom location. (just removed "Professional" from the default path). We can set it back to default path. Couldn't find a registry or other way to get this info (now that vswhere is needed to locate VS installations.)
There was a problem hiding this comment.
Yeah I also briefly ran down the rabbit hole of attempting to automagically determine install location without much success. If you could change this to the default path that would be great! Once this lands I'll upload a visix installer for VS2022 as a release here.
|
Thanks for doing this I haven't found time to do this myself! I'll be happy to upload a visix installer for 2022 once we get this working. |
Added initial support for Visual Studio 2022.
Tested with recent trunk with both 2019 and 2022.
2 things that may need cleanup :