Surround the command line argument with " to produce
double quotes in the compiled MSI. " is an XML standard and is replaced
by the parser with double quotes. For example:
-u "[USERNAME]" -k "[SERIAL]"
will show up as this in the MSI:
-u "[USERNAME]" -k "[SERIAL]"
Also, whe
to have the " Wix.targets" anywhere.
Installer.wxs is the main Wix file with the product, errormessages, actions
etc. Files.wxs is project spesific files (the components, linked mergefiles
etc). Don't quite see where i should add your XML nor how that would function?
Sincerely
Th
I use the MSBuild GenerateBootstrapper task to create a
bootstrapper to install .NET 2.0, 3.0, and other dependencies. It's fairly
easy to add to your build process if you're running MSBuild.
If you're using Votive, edit your .wixproj project file and add the following
code to
I had these issues with earlier versions of WiX, but they seem to have gone away with the latest releases. Try upgradin WiX to the latest release and you should see the issues disappear.Michael
From: "Jyothi Gummadi(Corpus, Inc)" <[EMAIL PROTECTED]>Sent: Wednesday, September 13,
Whenever I sit at my desk, I have the potential to introduce bugs. :)Do C++ custom actions introduce less defects? Absolutely not. If you or I write a bad custom action, it's not going to work or it's going to be very buggy.The issue is really the dependency. A non-CLR-based C++ custom actio
5 matches
Mail list logo