[WiX-users] Problem under Vista with ExecCommand
Hello, i made an simple installer for distributed installation of our software. It's necessary to write die IP of our application server in an txt-file, where the application reads it on first start. The "SERVERIP" ist passed to msiexec as an commandline-argument. The following CustomAction does an great job on Windows-XP, but on Vista the File "adr.txt" is not generated: REMOVE~=ALL The linebreaks in CustomAction are only in this mail, in the xml-file where is no linebreak. In the verbose-log i see that "RunCmd" is executed - on XP and Vista with RC 1 - and no error message. On XP we have the "adr.txt" after that, on vista we don't have. Does someone have an idea why that happens? regards, Albert Scholl -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference ___________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Un-installing Merge Module breaks upgraded component dependent on versioned dlls
Hi Wix-users, Another chestnut to do with shared MSM, here's the scenario: PRODUCT 1 contains: - MSM_A with contains version 1 of a backward compatible, A.dll, in component A, this depends on - MSM_B1 which contains version 1 of a non-backwards compatible, B1.dll, in component B1 PRODUCT 2 contains: - MSM_A with contains version 2 of a backward compatible, A.dll, in component A, this depends on - MSM_B2 which contains version 2 of a non-backwards compatible, B2.dll, in component B2 SCENARIO 1. Install Product 1, this installs A and B1 on the machine 2. No install Product 2, this upgrades A to version 2, and installs B2 on the machine (side by side with B1) 3. Now un-install Product 2, this removed B2 but leaves A with the upgraded version. Using A.dll now FAILS as it required B2, but only has B1 installed. Note that, to complicate matters, the dlls A, B1 and B2 are all COM (which is why Product 1 and Product 2 don't simply contain their own separate versions of A). But I think that this is a slight red-herring, though I may be wrong on this. Suggestions so far have been 1. Make B2 permanent - though this seems ugly, and results in files left on the machine after un-installing all products 2. Remove product 1 when product 2 is installed, which isn't really an option 3. Effectively changing the setup so that B1 and B2 are replaced with an upgrade component B which is upgraded in the same way as A is (though as these are shared, not backwards compatible and COM his make this option none trivial) Any help on this much appreciated. Yours, David - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MedHelp 6722
Canadian Doctor Dawn Howe Best Price On Net March 80% OFF! http://www.google.jp/pagead/iclk?sa=l&ai=xlyax&num=513195&adurl=http://www.addbase.com - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ _______ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Migrating merge modules to Wix
Hi wix-users, I've been looking into migrating as set of Visual Studio MSIs and MSMs to WiX (v2). On the whole things are are going swimmingly! One issue I haven't quite worked out is about migrating shared merge modules to wix. I've been using the same component guids as the previous VS2005 used (i.e. so that the componentIds match), but the shared COM components are now registered differently (using the recommended TypeLib, Class and ProgId WiX elements, as opposed to the (advertised?) way that VS registers COM). These all install correctly, and co-exist with legacy VS installers at the file level. But there is an issue with the COM registration. The issue is as follows: 1. Install a WiX MSI (containing a WiX MSM, which contains a shared COM component going to common files), *Result:* Works, shared com registered 2. Then install an older VS MSI (containing a VS MSM, which containing the same shared COM file), *Result:* Both apps work, shared com registered 3. Then uninstall the VS MSI. *Result:* WiX install is BROKEN, shared com is unregistered. My guess is that this is to do with the resources (i.e. registry keys) changing for the same component. Does anyone have any suggestions about this issue. With thanks, David - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] More PI}}LS IN$$IDE
{BODY}-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/_______
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] READY FOR C00L %N_IG_Ht?
Welcome my friend, We have a great offer in our shop Go here, for more... http://zlseyja.heartspeak.hk/?715170993051- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] More PI}}LS IN$$IDE
{BODY}-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] error 2103
[EMAIL PROTECTED] wrote: > Hello. > > We get some troubles running setup on a tailored version of Windows > Embedded. > > Everything seems fine until phase InstallFinalize, which gives error 2103; > "Could not resolve path for shell folder 26". > > 26 - is a kind of an id number for some system folder? http://msdn.microsoft.com/library/default.asp?url=/library/en-us/shellcc/platform/shell/reference/enums/csidl.asp lists the CSIDL numbers for special folders. I'm assuming that it's 26 decimal, which is 0x1A hex, which is CSIDL_APPDATA. You've probably used [AppDataFolder] somewhere in your setup. If you're using Windows XP Embedded I would have expected this to be present. Perhaps you've omitted some component that implements SHGetSpecialFolderPath/SHGetFolderPath? -- Mike Dimmick - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error code lookup
[EMAIL PROTECTED] wrote: > Is there a way to lookup Wix error codes? I'm getting CNDL0124, and I'd li > ke to find out more about the error, so I can start debugging it. As Rob says, look in messages.xml. IIRC in v3 all the Message elements carry a Number attribute so you can simply search for Number="124". I've looked into this problem before and I think that you've actually got malformed XML, or after performing the include step the XML is malformed. I noted last time that the element is not valid under in the WiX v2 schema. The catch block in Preprocessor.cs reports SP1ProbablyNotInstalled if *any* XmlException occurs, which seems too aggressive to me. No doubt some exception is erroneously thrown if SP1 isn't installed and you try to load an XmlDocument from a StringReader, but can we not tell the difference between this and an actual malformed document? -- Mike Dimmick - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
