Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to build project with latest Visual Studio #2523

Open
RaymondEllis opened this issue Nov 14, 2024 · 1 comment
Open

Unable to build project with latest Visual Studio #2523

RaymondEllis opened this issue Nov 14, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@RaymondEllis
Copy link

RaymondEllis commented Nov 14, 2024

Release Type: Official Release
Version: 4.2.0.2232
Platform(s): Windows/Linux, likely all others but untested.
Describe the bug
Unable to build project with Stride packages on latest Visual Studio.

To Reproduce

  1. Update Visual Studio to latest version 17.12.0+
  2. Clean
  3. Attempt to build

Expected behavior
Should build regardless of new VS versions, unless VS explicitly broke something.

Log and callstacks
Error shows as:

[AssetCompiler] Could not find a compatible version of MSBuild.
The command "dotnet "C:\Users\<UserHere>\.nuget\packages\stride.core.assets.compilerapp\4.2.0.2232\buildTransitive\..\lib\net8.0-windows7.0\Stride.Core.Assets.CompilerApp.dll"  --disable-auto-compile --project-configuration "Debug" --platform=Windows --project-configuration=Debug --compile-property:StrideGraphicsApi=Direct3D11 --output-path="<ProjectPath>\Bin\Windows\Debug\win-x64\data" --build-path="<ProjectPath>\<ProjectName>.Windows\obj\stride\assetbuild\data" --package-file="<ProjectPath>\<ProjectName>.Windows\<ProjectName>.Windows.csproj" --msbuild-uptodatecheck-filebase="<ProjectPath>\<ProjectName>.Windows\obj\Debug\win-x64\stride\assetcompiler-uptodatecheck"" exited with code 1.
@RaymondEllis RaymondEllis added the bug Something isn't working label Nov 14, 2024
@RaymondEllis
Copy link
Author

Found a work around: Install net 8.0 sdk. I had 8.0 installed as part of VS, was likely removed with the VS update since 9.0 is now out.

Would this work if FindAndSetMSBuildVersion checked if x.Version.Major >= NetMajorVersion instead of ==?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant