Changing ProjectSDK to 7.0.0-rc1 crashes the project

[mikitheking3]

Question

I have installed WiX 7 with the CLI. However, attempting to use it in my VisualStudio project when starting a new Wix project I get this if i try to install it through NuGet (The Wix SDK) - Package 'WixToolset.Sdk 7.0.0-rc.1' has a package type 'MSBuildSdk' that is not supported by project 'Package5'. If i just attempt to change it in my .wixproj file I get "One or more projects have changes which cannot be automatically handled by the project system. Please save other changes, and releoad these projects to prevent data loss, then it says "C:\Users\xxx\Desktop\VS Projekti\Package5\Package5.wixproj : error : The project file cannot be opened by the project system, because it is missing some critical imports or the referenced SDK cannot be found." This only happens when i try to refrence the RC 7.0 version. I can downgrade to any other version in the .wixproj file and use it but I cannot load this version for the life of me.

Open Source Maintenance Fee

• I (or an organization I'm a member of) pay the Open Source Maintenance Fee by sponsoring the wixtoolset project because I support the maintainers.

[robmen]

Please share the Package5.wixproj. Sounds like it isn't configured correctly.

Note: the CLI isn't used at all by the .wixproj.

[mikitheking3]

Package5.zip

Here is the whole .wixproj file. It only has this one line! When i change the version number to 7.0.0-rc.1 I get all the errors above :/. I started a project with the HeatWave for VS 2022 addon found on firegiant.

[mikitheking3]

It gets even weirder. So I installed VS 2026 Enterprise Edition, to try and see if there would be any difference from VS 2022 and I get the same error. What is interesting is, while In 2022 I have to reload the project when I write the SDK version 7.0.0-rc.1 and can't continue using it, In 2026 when I change the SDK version to 7 and add the accept EULA line, I can continue working on the project and even build it until I exit VS. When I load VS again, the solution does not want to load until I lower the version number to 6.0.2.