Attempting to Create a HeatWave (WiX) MSI Project Causes VS Error

Question

I'm new to HeatWave / WiX and wanted to get started with it, but am running into a strange issue that I haven't been able to find a resolution to.

In short, when I select Add > New Project from the solution context menu, then choose the MSI Package project and click Create, the project creation wizard fails with the error message The SDK 'WixToolset.Sdk/6.0.0' specified could not be found. I haven't been able to find anywhere online that I can download this SDK except from NuGet, but I can't install a NuGet package to the solution itself, so there doesn't seem to be any way to make it available to this project creation wizard.

What am I missing here? The HeatWave documentation implies all I need to do is install the extension and create a project, and then add extra NuGet packages to the project after it has been created. No other steps for installation are mentioned.

For what it's worth, I downloaded the VS extension from here and made sure I updated to the latest version of VS 2022 (17.13.6). If there's any other details relevant to debugging this, let me know.

To be clear, I haven't had any issues installing the extension itself (as far as I know anyway), it's just that I can't create a new project using the extension.

Thanks!

EDIT: It seems Nuget sources could be a cause of this issue, but in my case I already have nuget.org enabled:

Double-check Visual Studio's view of your NuGet feeds. There are many different ways to override which feeds are enabled/disabled/available, and maybe the VS set is different from what you got on the command-line? — Rob Mensching
– Rob Mensching, Commented May 10 at 20:56
It's the same from the VS UI sadly. I added a screenshot in case that helps. — Caleb Keller
– Caleb Keller, Commented May 13 at 19:27

Rob Mensching · Accepted Answer · 2025-05-08 15:06:34Z

0

You have installed HeatWave correctly. The issue sounds like Visual Studio cannot restore from nuget.org. Almost always the issue is misconfigured NuGet sources.

In Visual Studio, go to Tools -> Options then search for nuget. In the "Package Sources" make sure the first entry is to nuget.org like the following:

You will likely have additional sources in the list

If you prefer the command-line, try the following command:

dotnet nuget list source

You should see https://api.nuget.org/v3/index.json in the list somewhere and it needs to be marked [Enabled]. Mine is first:

Registered Sources:
  1.  nuget.org [Enabled]
      https://api.nuget.org/v3/index.json
  ...

If not, then you need to add that source doing:

dotnet nuget add source --name nuget.org https://api.nuget.org/v3/index.json

If the source is present but disabled, then you need to enable it:

dotnet nuget enable source nuget.org

(Replace nuget.org in that command-line with the name displayed in your first list source command, usually nuget.org).

answered May 8 at 15:06

Rob Mensching

36.3k5 gold badges94 silver badges134 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

Caleb Keller May 9 at 21:01

Thanks for the suggestion! Unfortunately, I already have nuget.org in my sources and enabled. I updated the question to include this additional debug information. Is there anything else that could be causing this issue?

Rob Mensching May 10 at 18:09

Maybe try creating a project by hand following the Quick Start (docs.firegiant.com/quick-start) and seeing if that works.

Caleb Keller May 13 at 19:25

I created the project using the quick start guide, but when I try to add it to VS using add > existing project, I get the same "Wixtoolset.Sdk/6.0.0 could not be found" error. Is it possible for me to install the toolset separately, or is that what the extension is required for?

Rob Mensching May 14 at 14:00

You can definitely use the WiX Toolset from the command-line, without HeatWave. That's what the Quick Start documentation is doing. However, HeatWave does all the work to integrate the .wixproj into Visual Studio (and it's a lot of work). I've never heard of anyone having this problem after verifying the nuget.config is correct. You might try the HeatWave forum where it is easier to go back and forth: docs.firegiant.com/heatwave/reporting-bugs

Collectives™ on Stack Overflow

Attempting to Create a HeatWave (WiX) MSI Project Causes VS Error

1 Answer 1

4 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

4 Comments

Your Answer

Sign up or log in

Post as a guest

Related