SlnGen fails under VsDevCmd environment.

[jogietze]

The "%PROGRAMFILES%\Microsoft Visual Studio\2022\Enterprise\Common7\Tools\VsDevCmd.bat" batch file sets up the PATH environment variable to include, for example:

C:\Program Files\Microsoft Visual Studio\2022\Enterprise\\MSBuild\Current\Bin\amd64

Your detection logic here...

https://github.com/microsoft/slngen/blob/main/src/Shared/DevelopmentEnvironment.cs#L182

...appends an extra amd64 without checking if the path exists, and fails:

D:\src>slngen
Unhandled exception: System.IO.FileNotFoundException: C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Current\Bin\amd64\amd64\MSBuild.exe
  at System.Diagnostics.FileVersionInfo.GetVersionInfo(String fileName)
  at Microsoft.VisualStudio.SlnGen.Program.Main(String[] args) in D:\a\_work\1\s\src\Microsoft.VisualStudio.SlnGen.Tool\Program.cs:line 81

[jeffkl]

That logic is in an if statement for only when the current runtime is 64-bit but the MSBuild.exe found is not 64-bit. Is this from a 32-bit development environment? I'm curious how its finding the 64-bit MSBuild.exe but doesn't think the current process is already 64-bit.

[jeffkl]

@jogietze Have you tried the latest version and still hit this? I think I saw it happen yesterday but when I updated SlnGen to the latest version it started working.

[jogietze]

The issue comes and goes. It's reasonably easy to work around by updating %PATH%.