Heatwave 1.0.8 broken in VS2022

[ptc-cjm]

After installing HeatWave 1.0.8 update in VS2022 (17.14.31).; The extension no longer shows in Installed(enabled) extensions. Further, loading any project with either WixV3 or newer projects results in an error mesage: "The 'HeatWavePackage' package did not load correctly. Inspecting the ActivityLog.xml shows the following error:
SetSite failed for package [HeatWavePackage]Source: 'Microsoft.VisualStudio.Composition' Description: Expected 1 export(s) with contract name "FireGiant.HeatWave.Services.IEditorClassificationBrushBridge" but found 0 after applying applicable constraints.
Microsoft.VisualStudio.Composition.CompositionFailedException: Expected 1 export(s) with contract name "FireGiant.HeatWave.Services.IEditorClassificationBrushBridge" but found 0 after applying applicable constraints.
at Microsoft.VisualStudio.Composition.ExportProvider.GetExports(ImportDefinition importDefinition)
at Microsoft.VisualStudio.Composition.ExportProvider.GetExports[T,TMetadataView](String contractName, ImportCardinality cardinality)
at Microsoft.VisualStudio.Composition.ExportProvider.GetExport[T,TMetadataView](String contractName)
at Microsoft.VisualStudio.Composition.ExportProvider.GetExportedValueT
at Microsoft.VisualStudio.ComponentModelHost.ComponentModel.GetServiceT
at FireGiant.HeatWave.HeatWavePackage.d__2.MoveNext() in D:\a\1\s\src\FireGiant.HeatWave\HeatWavePackage.cs:line 123
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Shell.AsyncPackage.<>c__DisplayClass17_0.<b__1>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.VisualStudio.Services.VsTask.RethrowException(AggregateException e)
at Microsoft.VisualStudio.Services.VsTask.InternalGetResult(Boolean ignoreUIThreadCheck)

************* END OF ERROR ******************

I've now seen this on 2 different Visual Studio 2022 instances (same version) and have gotten the same results. Also, can you please leave the older versions of this extension on the marketplace? The only way I could rollback to 1.0.6 was pulling it off of my virtual machine.

Thanks!

[FireGiantHelp]

You'll need to explicitly re-enable the extension or uninstall and re-install and ensure it's enabled before trying again, but this very much feels like a corrupt MEF cache. That can happen with failed installs/uninstalls, especially if it is repeated. I wish we controlled the VSIX installer, but we don't...

Before installing/uninstalling, delete your MEF cache here:
C:\Users\<user>\AppData\Local\Microsoft\VisualStudio\<instance ID>\ComponentModelCache

Then try again please. If it fails, please attach the MEF cache error file Microsoft.VisualStudio.Default.err located in that same folder.

[GreaterDane42]

The Heatwave extension is not showing in the list of installed extensions at all:

Instead the VS2022 Extension Manager shows that Heatwave can be installed when searching for it under the Browse tab. However, attempting to install the extension results in an error declaring that it's already installed:

The original poster described the issue a bit confusingly because the extension is not listed under Enabled, true, but they didn't mention that it's also absent from any Disabled category too.

Attaching the Microsoft.VisualStudio.Default.err:
Microsoft.VisualStudio.Default.err.zip

[ptc-cjm]

Yes, I had cleared my MEF cache. It was not in the disabled section either. It did not show as installed except when attempting to install again from browse which, I also got that dialog. I had to do a full repair of visual studio and remove the HeatWave package from the Common7\IDE\Extensions folder and kill the .mpack/.sqllite files just to roll back to 1.0.6. I get that we're at the mercy of the VSIX installer but this behavior does not occur with 1.0.6 in the same environment. My guess is that this might install/upgrade fine in a pristine VS2022 environment else they wouldn't have released it so I'm wondering if this is from a conflict with some other extension

[MaurizioFocareta]

Same issue here, tried to delete MEF cache but the issue remains.
Is there any workaound on this ? It's a big issue for our deployment processes.

[marcelooagosti]

I have probably the same scenario: VS2022 with WIXv3 installed in Windows 11. Exactly the same symptoms. Could not find a way to get Heatwave 1.06.
As an alternative, I installed VS2026. Started with the Tutorial and had no problems at all. The installation of 2026 got the Heatwave previously downloaded and installed that does not work with 2022,
Hope this helps.

[PaulGlynn588]

Same issue and error message for our 4 developers in VS2022 (17.14.33).
Spent a day using ChatGPT to get to the bottom of the issue. Tried many things. It finally settled on there is an issue with the package.
Package does not show as installed in "Extensions Manager".
Works fine on the same box in VS2026 (although that is not an option for us at the moment).

[MSingh-13]

I faced the same issue described by @GreaterDane42 on VS2022 17.14.33. I got around this by uninstalling Heatwave 1.0.8 from the VS 2022 developer command prompt using the below command.
vsixinstaller.exe /uninstall:FireGiant.HeatWave.Dev17

I was able to download older versions of the Heatwave extension using the below marketplace URL.
https://marketplace.visualstudio.com/_apis/public/gallery/publishers/firegiant/vsextensions/FireGiantHeatWaveDev17/1.0.6/vspackage

I faced the same issue with Heatwave 1.0.7.

I was able to install Heatwave 1.0.6 and it was listed under installed extensions in VS 2022 as expected. When I tried to create an MSI Package or WiX library project, I got the below error.

When I disconnected from the internet and tried again, I got the below error.

I then downloaded the nuget package for WixToolset.Sdk 6.0.0 to my global nuget cache (C:\Users<username>.nuget\packages\wixtoolset.sdk) and tried to create the projects again while I was online but I got the same initial error. I then tried again while offline. This time the projects got created.

I had used the Heatwave extension for VS2019 a couple of years ago and I did not face these issues. This was a very frustrating and time consuming experience on VS2022. @FireGiantHelp could you please look into resolving these issues.

[Japollack]

With the help of Copilot I'm seeing what appears to be a package initialization failure with HeatWave 1.0.8 on Visual Studio 2022 Community 17.14.40.

Environment

• Visual Studio 2022 Community 17.14.40
• HeatWave for Visual Studio 1.0.8
• Installed from Visual Studio Marketplace
• Windows x64

Symptoms

The extension installs and the WiX project templates are available:

• WiX Setup Project
• Other WiX project templates

This suggests that the VSIX is installed correctly and at least part of the extension is functioning.

However:

• HeatWave does not consistently expose its Project menu commands.
• I can see "Upgrade to latest WiX version..." and"Upgrade to WiX SDK" in Tools → Customize → Commands → Project.
• Sometimes the commands appear in Visual Studio.
• Most of the time they do not appear.
• When they do appear, clicking them produces no UI, dialog, or error.

ActivityLog findings

I found the following package load failure:

Begin package load [HeatWavePackage]

SetSite failed for package [HeatWavePackage]

Source: Microsoft.VisualStudio.Composition

Description:
Expected 1 export(s) with contract name
"FireGiant.HeatWave.Services.IEditorClassificationBrushBridge"
but found 0 after applying applicable constraints.

Microsoft.VisualStudio.Composition.CompositionFailedException:
Expected 1 export(s) with contract name
"FireGiant.HeatWave.Services.IEditorClassificationBrushBridge"
but found 0 after applying applicable constraints.

at Microsoft.VisualStudio.Composition.ExportProvider.GetExports(...)
...
at FireGiant.HeatWave.HeatWavePackage.InitializeAsync()

The failure occurs during:
HeatWavePackage.InitializeAsync()
which appears to prevent the package from fully loading.

Additional observations

The ActivityLog also contains:

Successfully loaded extension 'HeatWave for Visual Studio' (FireGiant.HeatWave.Dev17)

So the VSIX itself is discovered and loaded, but the package initialization subsequently fails due to the missing MEF export.

VSIX manifest

<Identity Id="FireGiant.HeatWave.Dev17" Version="1.0.8" Publisher="FireGiant" />
and targets:

<InstallationTarget Id="Microsoft.VisualStudio.Community" Version="[17.14,19.0)" />

Visual Studio 17.14.40 should therefore be within the supported range.

So, should an implementation/export of:
FireGiant.HeatWave.Services.IEditorClassificationBrushBridge
be provided by a separate assembly?

The symptoms seem consistent with the package loading partially (templates available) while package-driven functionality such as the Upgrade commands becomes unavailable because HeatWavePackage.InitializeAsync() fails.

Any guidance or workaround would be appreciated.