Hello All,
Thanks for understanding my issue. I have found the solution to my problem.
It was all because of harvesting the solution. I was missing the step so was
not able to run the MSI on machine other then the development.
I have then perform the harvesting of the Installer and it worked.
It's not exactly clear what you're doing, but the way this works (to
state the obvious maybe) is that you build the MSI file on your dev
machine and then take that MSI file to other machines and run it to
install the product. If you have a problem installing the MSI file on
another machine, then
Hi Nick,
Thanks for looking into the issue. $(var.MyProject.TargetMachine) is used
in the solution to set the file path . It is not related to compling or
execution of the installer.
My concern is that if I am executing the installer from my development
machine where I have developed the
Dit mailadres is niet meer in gebruik. Mail kan je voortaan sturen naar
basti...@careercontrol.nl.
--
Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+
I want to develop a installer using WIX in which we want to run 3 set up
simultaneously: DB Script, Console application and Web service. I have
develop the WIX Installer solution using VS2012 and have insluded the
console application and webservice solutions too within the same solution.
So, when
I don't understand. The $(var.MyProject.TargetMachine) is only used while
compiling the installer and not while using the installer. After compiling
the solution you should get one MSI file. You only need to deploy the MSI
file to the machine where you want to install.
--
View this message in
6 matches
Mail list logo
