I am trying to create an MSI file through WiX. To do that in VSCode, I need to install the "HeatWave" extension. But I can't find it in the extension marketplace.
It is, however, in the online web browser marketplace.
I downloaded the VSIX file and tried to install it through that - Didn't work either.
It just gave me this error.
"extension/package.json was not found in ZIP"
What is preventing me from installing the extension? Is there any other way to add WiX to Visual Studio Code?
HeatWave is an extension for Visual Studio; it doesn't support Visual Studio Code. We're not aware of any Visual Studio Code extensions for WiX today. But please file a feature idea at https://github.com/firegiant/HeatWaveSupport/issues/new/choose so the dev team can track interest in VSCode.
Related
How do you get msbuild.exe without installing those crazy Visual Studio programs?
I need it for an npm install to finish working. I'm on Windows 7 and can't get on older version of Visual Studio 2013 Express online.
The latest (as of Jan 2019) stand-alone MSBuild installers can be found here: https://www.visualstudio.com/downloads/
Scroll down to "Tools for Visual Studio 2019" and choose "Build Tools for Visual Studio 2019" (despite the name, it's for users who don't want the full IDE)
See this question for additional information.
It used to be installed with the .NET framework. MsBuild v12.0 (2013) is now bundled as a stand-alone utility and has it's own installer.
http://www.microsoft.com/en-us/download/confirmation.aspx?id=40760
To reference the location of MsBuild.exe from within an MsBuild script, use the default $(MsBuildToolsPath) property.
You can also get the MSBuild executable as a Nuget package https://www.nuget.org/packages/Microsoft.Build.Runtime/.
Download MSBuild with the link from #Nicodemeus answer was OK, yet the installation was broken until I've added these keys into a register:
[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\MSBuild\ToolsVersions\12.0]
"VCTargetsPath11"="$([MSBuild]::ValueOrDefault('$(VCTargetsPath11)','$(MSBuildExtensionsPath32)\\Microsoft.Cpp\\v4.0\\V110\\'))"
"VCTargetsPath"="$([MSBuild]::ValueOrDefault('$(VCTargetsPath)','$(MSBuildExtensionsPath32)\\Microsoft.Cpp\\v4.0\\V110\\'))"
When I try to publish a project, the error shows:
Error 2. SignTool.exe Missing.
I searched on my computer for SignTool.exe, the file doesn't exist.
I installed the Windows SDK, that didnt work, the file still doesn't exist. Then I installed the .Net framework, Silverlight, then reinstalled the whole Microsoft Visual Basic.
The file still doesn't exist.
Where can i download SignTool.exe?
signtool.exe is part of the .NET SDK. You'll need to download that, which will install it into the proper location.
You should be able to find the .NET SDK with a search on MSDN. There's no point in posting a link here, because they change over time or as new versions are released. (You can also find it by searching Google for "dot net sdk", which returns many different links to the Microsoft pages.)
I had the same issue but installing the Windows SDK did not work for me (signtool.exe was still missing from my machine).
I stumbled across this solution: http://www.benedykt.net/2015/08/12/missing-signtool-exe-w-visual-studio-2015/
Basically:
Open Programs and Features
Select 'Microsoft Visual Studio [version]' and click Change
And select 'ClickOnce Publishing Tools' for installation
I have been trying to get the MonoTools for Visual Studio from their web site (mono-tools.com). But with no luck. Where to get MonoTools for Visual Studio 2010/2012 plug-in?
Aditya.
You can easily modify the MonoTools installer to work with VS2012. .vsix files are ZIP files. In the root of the zip, you'll see a file named extension.vsixmanifest, which lists the versions of Visual Studio that are supported by the extension.
Basically,
Download the MonoTools package
Rename it to have a .zip extension
Right-click and select "open" - you don't want to extract the file, just open the archive using the built-in Windows mechanism
Copy extension.vsixmanifest anywhere - say, to your desktop.
Open it up in a text editor (I love Notepad++, EMACS is also pretty awesome under OSX.)
Change the SupportedProducts key to the following:
<SupportedProducts>
<VisualStudio Version="10.0">
<Edition>VSTS</Edition>
<Edition>VSTD</Edition>
<Edition>Pro</Edition>
</VisualStudio>
<VisualStudio Version="11.0">
<Edition>VSTS</Edition>
<Edition>VSTD</Edition>
<Edition>Pro</Edition>
</VisualStudio>
</SupportedProducts>
Copy the modified file back into the archive.
Rename it from .zip to .vsix
Run it. The Visual Studio Version Selector should appear and let you pick VS2012.
If the Mono menu item doesn't appear after restarting VS, you may need to run
devenv /setup
from a VS command prompt (or, from c:\program files (x86)\microsoft visual studio 11\common7\ide).
This works for just about any VS2010 extension.
That was a former product from Novell, and it is no longer offered or developed.
Xamarin doesn't offer it either.
can get it from here: http://mono-tools.com/
free if you do their survey
but i don't see a vs2012 version
It costs at minimum $999.00 - https://store.xamarin.com/ and is included as part of Mono for Android. Here's a screenshot of what it looks like after it's installed.
There is also a training course on this from PluralSight -- http://www.pluralsight-training.net/microsoft/Courses/TableOfContents/android-intro
We have created a simple wix project for a basic windows application. Everything builds fine and the MSI is produced.
However, switching to Release gives the following error message;
light.exe(0,0): error LGHT0222: The cube file'C:\Users\julius\AppData\Local\assembly\dl3\3V768E95.XWA\CYQG3JK6.XHT\2b4730b4\00186b06_b0b7cb01\darice.cub' cannot be found. This file is required for MSI validation.
If I run our build script which uses msbuild to build the solution everything works fine. So I am thinking it got something to do with the visual studio environment. I have tried making a simple solution with a wix installer and that solution works fine both in debug and release.
Im running this on Windows 7 64 bit box using VS 2010 SP1.
Any ideas what I should look for?
Same config here. I just copied it from C:\Program Files (x86)\Windows Installer XML v3.6\bin to that location and the error is gone. Weird...
I was able to fix this in VS2013 by simply restarting Visual Studio
Has anybody been using WiX with 2010? I'm not able to get my install projects to work in 2010 and I can't find any info on getting this to work/future plans for support.
Try installing the latest build of WiX 3.5. This is the version that supports VS2010. I don't know if it has been updated for the beta2 release, but there was a new one built 3 days ago.
EDIT: The link above will not work for Visual Studio 2010 post-Beta. For later releases of Visual Studio 2010, use the latest release:
http://wix.sourceforge.net/releases/
and select the latest version.
which version of Wix are you using? last I checked, there was some compatibility issues with wix >=3, votive, and visual studio.
you might have to get a custom build of votive that will load on 2010.
As of October 26, this is what I had to do to get it working:
Download latest of 3.5 http://wix.sourceforge.net/releases/3.5.1023.0/
I snagged Wix35_x64.msi, you grab the other if you run 32bit. I'm not sure what the other (less obvious) files are for (I'm looking at you, ProjectAggregator2).
After installation, Wix projects load (yay!) but don't build (boo) with an error about the path for Candle.EXE being invalid. Apparently, its still looking for "C:\Program Files (x86)\Windows Installer XML v3" on my system.
Created this directory and copied the contents of "C:\Program Files (x86)\Windows Installer XML v35" into it.
Now, apart from some build errors due to changes in some of the $vars, it works.
We added support for Visual Studio 2010 beta 2 in last Friday's build. See http://www.joyofsetup.com/2009/10/30/wix-v3-5-supports-visual-studio-2010-beta-2/.