519 or try a weekly build of 3.6.
(http://wix.sourceforge.net/releases/)
Once that is done open your solution in visual studio and it should run
the upgrade wizard automatically.
-Original Message-----
From: Skip Sailors [mailto:ssail...@wpc-edi.com]
Sent: 17 March 2011 19:27
To:
missing. What do I have to do so that my IDE can find the new WiX?
TIA
Skip Sailors, Consultant
Washington Publishing Company
ssail...@wpc-edi.com <mailto:ssail...@wpc-edi.com>
Cell: 425.753.4601
Fax: 425.562.2245
www.wpc-servi
blank. What am I
missing?
TIA
Skip Sailors, Consultant
Washington Publishing Company
ssail...@wpc-services.com <mailto:ssail...@wpc-edi.com>
Cell: 425.753.4601
Fax: 425.562.2245
www.wpc-services.com <http://www.wp
Pardon a lurker.
I only know enough to be dangerous on a *nix box. Seems to me, though,
that if you are shipping your product via what sounds like conventional
*nix ./make ./configure and you want to get the same sort of flavor on a
Windows box then WiX isn't what you want. MSBuild is closer to
iting trouble
Skip Sailors wrote:
>
>
> Root="HKLM" Key="Software\Classes\Wow6432Node\CLSID\{
> yada-yada-blah-blah-blah }" Action="createAndRemoveOnUninstall">
>
It's not normally necessary to specify that r
yada-yada-blah-blah-blah }" has been written, so that the account
running the install process is allowed to write some keys. Does anybody
know what is going on? Can someone cite chapter and verse of the manual
I should have read to understand this?
TIA
Skip Sailors
Washington Publishi
6 matches
Mail list logo
