-
Notifications
You must be signed in to change notification settings - Fork 572
Description
The Cosmos DevKit installer fails to detect installed Visual Studio workloads, even though Visual Studio 2022 Community Edition is installed with the required workloads (.NET Desktop Development and Desktop Development with C++). As a result, the installer reports:
Visual Studio Workloads not found
This prevents the installer from building Builder.sln and launching Cosmos Builder.
Steps of installation up to now
Installed Visual Studio 2022 Community Edition with the required workloads.
Installed .NET 6 Runtime (x64).
Downloaded the latest Cosmos DevKit installer (install-VS2022.bat).
Ran the installer from Command Prompt as Administrator.
Attempted to bypass detection by manually setting InstallDir in the batch file.
Despite these steps, the installer still fails to detect the workloads.
Expected behavior
The installer should detect the installed Visual Studio workloads, build Builder.sln, and launch Cosmos Builder without errors.
Logs
Build status: Error
Error: Visual Studio Workloads not found.
Checking Dependencies...
Repos: IL2CPU, XSharp and Common is installed.
Proper Cosmos folder name is installed.
Visual Studio 15.9+ is installed.
Visual Studio Workloads was not found. Install install .Net Core 6.0 Runtime.
Setup (please complete the following information):
Cosmos Version: DevKit (latest release)
Installer run as administrator: Yes
Visual Studio Version: 2022 Community Edition, 17.x
Workloads installed: .NET Desktop Development, Desktop Development with C++
Operating System: Windows 11
Additional context
Running the installer in PowerShell causes / arguments to be misinterpreted; CMD must be used.
Manually setting InstallDir does not resolve the detection issue.
Directly building Builder.sln via MSBuild works, which suggests the problem is with the installer’s detection logic, likely related to vswhere.exe or the MSBuild path.