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
heat.exe : error HEAT0001 : Exception has been thrown by the target of an invocation. #4853
Comments
The only way I could reproduce this was to not have the specified version of MSBuild installed on my machine. I only had MSBuild 14.0 on my machine, but set the ToolsVersion in the csproj file to 12.0. For now, Heat requires that the version of MSBuild specified in the ToolsVersion attribute is installed. Pull request to log the real error message: 289.
|
Thanks for the update. Is there some .wixproj upgrading required when going from VS2013 to VS2015?
|
The ToolsVersion of the wixproj isn't relevant to Heat. Heat reads in the ToolsVersion of the target project (in your case D:\XXXX\Service.Windows.ApplicationServer\Service.Windows.ApplicationServer.csproj) and loads that version of MSBuild to process it.
|
Ah... that's good to know. Should I just update the ToolsVersion of the projects to 14 then? Is that a workaround?
|
I wouldn't call it a workaround, that's how it works. The ToolsVersion attribute is for specifying which version of MSBuild to use to build the project - Visual Studio, msbuild, and heat all behave differently depending on the value. If you want to build the project with MSBuild 12, then set the ToolsVersion to 12.0 and make sure MSBuild 12 is installed. If you want to build the project with MSBuild 14, then set the ToolsVersion to 14.0 and make sure MSBuild 14 installed.
|
|
The latest 3.10 beta (June) resolved issue #4597 but when I retargeted .NET 4.6, (HEAT) stopped working again, and I'm now getting the below error results and cannot build the WiX project:.
heat.exe : error HEAT0001 : Exception has been thrown by the target of an invocation.
The text was updated successfully, but these errors were encountered: