Wix on windows 10 with mvs2013 or mvs2014 is not working (making php executable)
wix toolset visual studio 2019
wix toolset linux
wix toolset visual studio 2017
wix setup editor
wix toolset offline installer
wix toolset 3.7 download
Wix on windows 10 with mvs2013 or mvs2014 is not working.
I am getting the error:
The "GenerateCompileWithObjectPath" task could not be loaded from the assembly \WixTasks.dll. Could not load file or assembly 'file:///c:\WixTasks.dll' or one of its dependencies. The system cannot find the file specified. Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask. SetupProject5 C:\Program Files (x86)\MSBuild\Microsoft\WiX\v3.x\wix2010.targets
If i try to include
WixTasks.dll to the project, when mvs2013 or mvs2014 crashes during the build. I include
\WixTasks.dll to the
C:\SourceControl\vs2015\SetupProject1\SetupProject1\SetupProject1.wixproj from the unpacked wix binaries folder:
<?xml version="1.0" encoding="utf-8"?> <!-- Copyright (c) .NET Foundation and contributors. All rights reserved. Licensed under the Microsoft Reciprocal License. See LICENSE.TXT file in the project root for full license information. --> <Project ToolsVersion="4.0" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"> <PropertyGroup> <Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration> <Platform Condition=" '$(Platform)' == '' ">x86</Platform> <ProductVersion>3.10</ProductVersion> <ProjectGuid>0adbe89f-e1ce-4345-90e6-64b8304fa42f</ProjectGuid> <SchemaVersion>2.0</SchemaVersion> <OutputName>SetupProject1</OutputName> <OutputType>Package</OutputType> <WixToolPath>C:\SourceControl</WixToolPath> <WixTargetsPath>$(WixToolPath)\wix.targets</WixTargetsPath> <WixTasksPath>$(WixToolPath)\WixTasks.dll</WixTasksPath> <WixTargetsPath Condition=" '$(WixTargetsPath)' == '' AND '$(MSBuildExtensionsPath32)' != '' ">$(MSBuildExtensionsPath32)\Microsoft\WiX\v3.x\Wix.targets</WixTargetsPath> <WixTargetsPath Condition=" '$(WixTargetsPath)' == '' ">$(MSBuildExtensionsPath)\Microsoft\WiX\v3.x\Wix.targets</WixTargetsPath> </PropertyGroup> <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|x86' "> <OutputPath>bin\$(Configuration)\</OutputPath> <IntermediateOutputPath>obj\$(Configuration)\</IntermediateOutputPath> <DefineConstants>Debug</DefineConstants> </PropertyGroup> <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|x86' "> <OutputPath>bin\$(Configuration)\</OutputPath> <IntermediateOutputPath>obj\$(Configuration)\</IntermediateOutputPath> </PropertyGroup> <ItemGroup> <Compile Include="Product.wxs" /> </ItemGroup> <Import Project="$(WixTargetsPath)" /> <!-- To modify your build process, add your task inside one of the targets below and uncomment it. Other similar extension points exist, see Wix.targets. <Target Name="BeforeBuild"> </Target> <Target Name="AfterBuild"> </Target> -->
I was reading different online forums and examples the last two days. Also Pact books on wix by Nick Ramirez. Nothing is working.
Define the following MSBuild variables and everything should work.
<WixRootPath Condition=" '$(WixRootPath)' == '' ">$(MSBuildThisFileDirectory)Tools\wix\$(WixTargetVersion)\</WixRootPath> <WixToolPath Condition=" '$(WixToolPath)' == '' ">$(WixRootPath)</WixToolPath> <WixTargetsPath Condition=" '$(WixTargetsPath)' == '' ">$(WixRootPath)Wix.targets</WixTargetsPath> <WixCATargetsPath Condition=" '$(WixCATargetsPath)' == '' ">$(WixRootPath)sdk\Wix.CA.targets</WixCATargetsPath> <WixTasksPath Condition=" '$(WixTasksPath)' == '' ">$(WixToolPath)WixTasks.dll</WixTasksPath> <WixSdkPath Condition=" '$(WixSdkPath)' == '' ">$(WixRootPath)sdk\</WixSdkPath>
Just make sure the paths are right. These paths are for the wix 3.10.2 binaries which I checkout for my builds on the build machine.
I think the build tasks should be looking in the path defined by the WIX environment variable but I'm not 100% sure about that.
I think defining all the variables with the path you set should fix everything since the error mentions looking in C:\WixTasks.dll normally the path it looks for is something like $(WixInstallPath)WixTasks.dll but if $(WixInstallPath) isn't properly defined it will just be empty and default to C:\WixTasks.dll. You do define $(WixTasksPath) but I think it's getting overwritten for somereason...
Regardless, there's something wrong on your system right now but you can work around it this way probably.
EDIT: If the above doesn't work, download the wix binaries from here and extract them into a folder called "Wix" or whatever you want to call it. Then set your WixRootPath to be equal to that location.
msbuild, wix on windows 10 mvs2013 or mvs2014 not working. i getting project, when mvs2013 or mvs2014 crashes during build. include \wixtasks.dll Wix on windows 10 with mvs2013 or mvs2014 is not working (making php executable) Wix on windows 10 with mvs2013 or mvs2014 is not working. Recently active msbuild
I encountered this when using VS2015 and working on git branches that use different versions of Wix. (I'm upgrading to the latest Wix version but not all branches are there yet.)
You must terminate and restart VS if you switch between git branches that use different versions if Wix. VS holds some Wix files open, files that won't work under any other version of Wix. If you forget to do this your VS build will fail with the (quite cryptic) message of "The "GenerateCompileWithObjectPath" task could not be loaded from the assembly C:\Program Files (x86)\WiX Toolset v3.10\bin\WixTasks.dll"
WiX Toolset, The most powerful set of tools available to create your Windows installation experience. into build processes to create Windows installation packages. as the rest of your product: source code is compiled and then linked to create executables; The WiX command-line build tools work with any automated build system. 1 Wix on windows 10 with mvs2013 or mvs2014 is not working (making php executable) Jun 7 '16
The working solution from WiX Cookbook by Nick Ramirez, 2015, Chapter1 "Building a WiX installer from the command line", Example 4 "BuildMachineInstaller"
Download and unzip wix binaries file, for example from here.
1. Create some folder for your project, for example
C:\SourceControl\own\box1 with file
2. Extract binaries to some folder, for example to
3. start windows command line tool
cmd and change to your project folder. Execute
light commands as folows:
C:\SourceControl\own\box1\tools\wix\candle *.wxs -o obj\
C:\SourceControl\own\box1\tools\wix\light obj\*.wixobj -o bin\CommandLineInstaller.msi
Anyway, if somebody could give some working example files and description how to make *.exe or *.msi with MSBuild or Visual Studio Build and wix, i would appreciate a lot. The other examples in Pact books are not working by pure copying, although are very useful for general understanding.
Windows Installer XML (WiX), WiX is a set of tools that allows you to create Windows Installer-based The WiX toolset is based on a declarative XML authoring model. How does WiX work? the traditional compile and link model used to create executables from source NET 3.5, which is not installed by default on Windows 8 and Windows Server Service dependencies are causing my wix msi to force a reboot on uninstall Tag: wix , windows-installer I have spent the past 3 days running in-place while tracking down the cause of forced reboots on my system, but have finally narrowed it down to a very specific cause.
I've just come across this issue and found that at the top of the wix2010.targets file was the following property group.
<PropertyGroup> <WixInstallPath Condition=" '$(WixInstallPath)' == ''">$(Registry:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Installer XML\3.11@InstallRoot)</WixInstallPath> <WixInstallPath Condition=" '$(WixInstallPath)' == ''">$(Registry:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows Installer XML\3.11@InstallRoot)</WixInstallPath>
When checking the referenced registry path there was no entry for 3.11 but there was one there for 3.10. and the installed version was reported as 3.10. So updating the property group to the following corrected the issue for me.
<PropertyGroup> <WixInstallPath Condition=" '$(WixInstallPath)' == ''">$(Registry:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Installer XML\3.10@InstallRoot)</WixInstallPath> <WixInstallPath Condition=" '$(WixInstallPath)' == ''">$(Registry:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows Installer XML\3.10@InstallRoot)</WixInstallPath>
Hope this helps.
msbuild, Wix на окнах 10 с mvs2013 или mvs2014 не работает (что делает PHP Эти пути для WIX 3.10.2 двоичных файлов, которые я Checkout для моей сборки на :HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows из сборки C: \ Program Files (x86) \ WiX Toolset v3.10 \ Bin \ WixTasks .dll». Wix on Windows 10 with mvs2013 or mvs2014 does not work (making the php executable) Wix on windows 10 with mvs2013 or mvs2014 is not working. I am getting
I solved the problem by following these instructions:
Download WIX311.exe from https://github.com/wixtoolset/wix3/releases/tag/wix3111rtm Download Votive2017.vsix from https://marketplace.visualstudio.com/items?itemName=RobMensching.WixToolsetVisualStudio2017Extension
Remove any old WiX nuget packets from your solution/project
Follow these instructions (you can omit /quiet).
http://packagingstuffs.blogspot.com/2017/11/wix-toolset-311-silent-install-method.html Content from the website above;
To Install: Step1: Download the source from web and get the installer wix311.exe. Step2: Run following command:wix311.exe /install /quiet /norestart Step 3: Copy the Votive2017.vsix file (provided by vendor) to the local machine (e.g. %TEMP%) Step 4: Run VSIXinstaller from its stored location "%ProgramFiles(x86)%\Microsoft Visual Studio\2017\Professional\Common7\IDE\VSIXInstaller.exe" /quiet
Good luck and best regards
WiX, Windows Installer XML Toolset (WiX, pronounced "wicks"), is a free software toolset that builds Windows Installer packages from XML. It consists of a command-line environment that developers may integrate into their build processes to build of WiX on April 5, 2004, he commented, "I did not feel that many people inside Teams. Q&A for Work. Stack Overflow for Teams is a private, secure spot for you and your coworkers to find and share information.
Wix Toolset Visual Studio 2017 Extension, Visual Studio integration for the WiX Toolset - the most powerful set of tools To report bugs or feature requests please go to http://wixtoolset.org/issues/. The core of WiX is a set of build tools that build Windows Installer packages and then linked to create executables; in this case .exe setup bundles, PHP If something else with isset: else part does not work PHP Part is here So when I post it, else part does not work at all (meaning: the text I set just disappear), while the other half works (meaning: I can assign variables, but can't leave it blank).
4 Great Tools to Create Windows Installer Packages, Ability to create Windows installers that can install, uninstall, set One installer that is compatible with all major version of Windows from Windows 95 to Windows 10. It's not going to be able to do what InstallShield or even Advanced If you don't have Visual Studio, you can use the Wix tools or MSBuild. Wix on Windows 10 with mvs2013 or mvs2014 does not work (making the php executable)
Creating two start menu shortcuts for the same executable, Creating two start menu shortcuts for the same executable. Hi! I'm trying Rapidly troubleshoot problems before they affect your business. Java,.NET, & PHP application. http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Incomprehensible-warning-td2234181.html Dec 13, 2013; 4:10pm The reason for VC++ redistributable taking 6 minutes is probably caused by issues with Windows Update on the computer you are running the installer on. The VC++ redistributable uses the WIX burn engine (part of the WIX Toolset). During the installation process the WIX Burn engine will try to pause automatic updates.
- Please use proper names when possible, it makes it easier to understand what you are talking about - I assume you mean VS2013 and VS2015, not 'mvs2013' and 'mvs2014'?
- I did as you said. Visual studio crashes. I am also getting more than 100 warnings of type: "The global element 'schemas.microsoft.com/wix/2006*' has already been declared".
- I have tried on vs2013 and vs2015. Which vs do you use? Which wix do you install? How do you build? Do you use visual studio?
- I am sorry, i am new to exetutables, etc.. . Seems the error is that i should uninstall wix, and use binaries with MSBuild Tools instead.
- MSBuild give a lot of errors, ot type "Undefined if not building from within Visual Studio", for example: C:\SourceControl\own\box1\Tools\wix\candle.exe -dDebug -d"DevEnvDir=*Undefined if not building from within Visual Studio" . Could you please give me a full eample of *.wixproj file
- Dear Brian, if you could give me any full (the more complicated, the better. I am trying to make executable for phpbrowserbox website: github.com/dhtml/phpbrowserbox ) *.wixproj example i would appreciate a lot. Seems i use some variables, which MSBuild does not understand.
- Exactly what I ran into today, but with VS 2017.
- other working ways to make windows *.msi or *.exe files include: InnoSetup and IExpress link link link