[WiX-users] Files in MSI not dropped onto system during install
I have an install that contains 14647 files. When the MSI is installed it is only installing 13895 files (any file higher than this number is not making it on the system)...is there some sort of limitation? I have used orca to examine the MSI and everything looks correct...I can see the files...they are assigned to the correct components...the components are assigned to the correct directories...but still they are not getting on the system. Anyone else have this issue? Nick H. NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. 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] Patching, patching, and more patching.....
Hello, From research I have done, it appears that this type of question has been asked a few times before (so please hang in there)...but I am still a little sketchy on the details of how to accomplish it or maybe if I am understanding the process correctly. Here is what I would like to do: * Create the RTM version of my installer * Be able to patch the RTM version with any patch that I create for it * Also be able to patch the RTM version that has already been patched with a previous (earlier) patch In other words, if I release version 2008.0.14.0 I would like to be able to patch it (and all the RTM's with previously distributed patches applied) with the latest a greatest patch (let's say 2008.0.14.30) * I would be able to patch 2008.0.14.0 to 2008.0.14.30 * I would be able to patch 2008.0.14.15 to 2008.0.14.30 * Etc, etc, etc Now, it appears that this can be accomplished by adding ReplacePatch and additional TargetImage tags in the patch file. I have attempted to create this patch and it seems to work (although some things concerned me when looking at the patch.log, but side point anyways). My real concern is if I want to accomplish this it appears that I would have to have an administrative image of every single patch and then reference it in my PCP file with a TargetImage tagemy administrative images are over 250MB in size and we could easily have over 50-80 patches created during the time this software would be in use by our customers.we are talking 12 - 20 GB of hard drive space (I know, I know...hard drive space is cheap) and it seems like the patch creation process would take for ever!!! I tried this with just a few administrative images and it seems to really take a lot longer than when I only had 2 administrative images to deal with so I can only image how long it would take with 50 admin images to deal with. Hopefully, I am misunderstanding how to create patches that will accomplish my goals above and there is a cleaner way. Anyone else out there trying to accomplish the same thing or have already done so successfully? I would love to have your input. Thanks, Nick H. NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. - 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.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Patching, patching, and more patching.....
And it appears that the minor upgrades (service packs) would be approximately the same size as the original install? My orginal install is about 110MB and the updates are about 15MB. Thanks again Bob, I really appreciate you input/help. From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Friday, April 13, 2007 12:38 PM To: Nick Hennemann Cc: [EMAIL PROTECTED] Subject: Re: [WiX-users] Patching, patching, and more patching. Nick Hennemann wrote: * Create the RTM version of my installer * Be able to patch the RTM version with any patch that I create for it * Also be able to patch the RTM version that has already been patched with a previous (earlier) patch The MSI patching model supports that but as you found, it quickly turns into a exponential nightmare both for building the patches and applying them. The general approach is to support multiple QFE patches but cumulative minor upgrade patches (aka service packs). The service packs supercede the QFEs and eventually become the required target images. It keeps the matrix down to a manageable level. -- sig://boB http://bobs.org NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. - 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.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Patch trying to uninstall RTM (original) version
Ok, thanks Bob! I appreciate your time to help out a newbie. From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Thursday, April 12, 2007 9:45 AM To: Nick Hennemann Cc: [EMAIL PROTECTED] Subject: Re: [WiX-users] Patch trying to uninstall RTM (original) version Nick Hennemann wrote: No matter how I run the patch I get taken to the repair or remove dialog. However the msiexec log show that it being recognized as a patch and if I select the repair option it does indeed apply the changed (updated) files to the target system. It's expected if the patch has UI (which it would if your original packages have UI). These patches are something that will most likely be downloaded by our customer base and applied by our customers. Can these patches be installed in a quiet mode? Possibly using a bootstrapper to help determine if the patch has completed? Absolutely. Generally, patches aren't downloaded/installed as naked .msp files. Instead, there's an .exe wrapper that uses the /qb or /qn switches to suppress the .msp UI. Take a look at the MsiApplyPatch function. -- sig://boB http://bobs.org NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. - 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.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Overwrite existing files during install
I have created several WiX installs and normally I do not have to worry about any of the files I am putting on the system already being there...however with my latest install the files I am dumping on the system could possible be on the system already. Is there a way that I can ensure that they files get overwritten (even if the existing files are possibly in use during the install). I have attempted to reboot after applying the install, thinking that they would then get moved into place, but they have not. Anyone have some ideas on how to accomplish this? Thanks for you time, Nick NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. - 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.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Overwrite existing files during install
Searched MS for this SDK, found one date 1/11/2001 http://www.microsoft.com/downloads/details.aspx?FamilyID=e96f8abc-62c3-4 cc3-93ad-bfc98e3ae4a3DisplayLang=en Is this the newest one? Thanks for the quick response. Nick From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 06, 2007 5:29 PM To: Nick Hennemann; wix-users@lists.sourceforge.net Subject: RE: Overwrite existing files during install I suggest reading through the File Versioning stuff in the MSI SDK. It talks in depth about when files are replace during the install. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nick Hennemann Sent: Tuesday, March 06, 2007 3:29 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Overwrite existing files during install I have created several WiX installs and normally I do not have to worry about any of the files I am putting on the system already being there...however with my latest install the files I am dumping on the system could possible be on the system already. Is there a way that I can ensure that they files get overwritten (even if the existing files are possibly in use during the install). I have attempted to reboot after applying the install, thinking that they would then get moved into place, but they have not. Anyone have some ideas on how to accomplish this? Thanks for you time, Nick NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. - 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.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Calling MSI from within MSI
Is there a way to call an MSI from within an MSI (to install a missing component that is needed by the main MSI to install successfully). I have it setup as a custom action to check for this component and if it is not already installed then it kicks of the secondary MSI to install the missing component. I should mention that the second MSI is not one that I have written. The custom action works fine and launches the second MSI; however I get an error message stating, Another installation is in progress. You must complete that installation before continuing this one. Is this possible or is there a cleaner way? Thanks for your time. Nick NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. - 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.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to use a Property Value to create another Property
Thanks for the quick response.I just tried your suggestion and unfortunately I got the same result. From: Levi Wilson [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 14, 2007 2:11 PM To: Nick Hennemann Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How to use a Property Value to create another Property Have you tried: Property Id='VDDIR' Value=[MAINDIR]webmain / I think that should resolve to what you want. On 2/14/07, Nick Hennemann [EMAIL PROTECTED] wrote: I have the following Property MAINDIR and it is populated correctly from the registry Property Id='MAINDIR' RegistrySearch Id='AppInstallRegistrySearch' Type='raw' Root='HKLM' Key='Software\OurSoftwareCompany\SoftwareName' Name='Install Directory' / /Property And then I have another property call VDDIR and I use the MAINDIR property to help build the path for my virtual directoryhowever I can see that instead of the path being built by replacing the MAINDIR property with it's value it simply is leaving the path with [MAINDIR] . Here are the properties as reported in the MSI log: Property(S): MAINDIR = C:\PROGRA~1\SoftwareDir\ Property(S): VDDIR = [MAINDIR]webmain Property Id='VDDIR'[MAINDIR]webmain/Property How do I use the value from one Property in another one? Any help would be greatly appreciated. It appears that maybe it is defining the property of VDDIR before it is getting the value of MAINDIR...if so how can I ensure that MAINDIR is populated first. TIA. Here is an excerpt from the WiX tutorial that shows how to do it, but I can't seem to make it work. Anyone able to get this to work? Property Id= INSTALLDIR IniFileSearch Id='AcmeFoobarIniFile' Type='directory' Name='SampleRegistry.ini' Section='Sample' Key='InstallDir' / / Property There might be cases when simply knowing the directory is not enough: you have to look into the directory and make sure a given file exists there. Depth = n can be used to instruct the installer to look n levels deeper than the specified Path. Zero or a missing Depth attribute means only to look in the specified folder, not below it. We use square brackets in Path to tell the installer to use the value of the INSTALLDIR property-bracketed names will be looked up and if found, replaced with their actual value. If not found, the string will remain unchanged. Property Id=FILEEXISTS DirectorySearch Id=CheckFileDir Path=[INSTALLDIR] Depth=0 FileSearch Id=CheckFile Name=Lookfor.txt / /DirectorySearch /Property NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. - 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.phpp=sourceforgeCID=DEVDE V ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. - 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.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to use a Property Value to create anotherProperty
Ok, I will go that route. THANK YOU for your quick responses! From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of K-ballo Sent: Wednesday, February 14, 2007 2:42 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How to use a Property Value to create anotherProperty You cannot set a property to the value of another property in that way. That is necessary to prevent creating circular references. What you should do is call a CustomAction that will set the value of VDDIR property after MAINDIR has been set. You would have to do something like this: CustomAction Id=SetVDDIR Property=VDDIR Value=[MAINDIR]webmain/ Custom Action=SetVDDIR After=AppSearch/ K-ballo.- Nick Hennemann escribió: I have the following Property MAINDIR and it is populated correctly from the registry Property Id='MAINDIR' RegistrySearch Id='AppInstallRegistrySearch' Type='raw' Root='HKLM' Key='Software\OurSoftwareCompany\SoftwareName' Name='Install Directory' / /Property And then I have another property call VDDIR and I use the MAINDIR property to help build the path for my virtual directoryhowever I can see that instead of the path being built by replacing the MAINDIR property with it's value it simply is leaving the path with [MAINDIR] . Here are the properties as reported in the MSI log: Property(S): MAINDIR = C:\PROGRA~1\SoftwareDir\ Property(S): VDDIR = [MAINDIR]webmain Property Id='VDDIR'[MAINDIR]webmain/Property How do I use the value from one Property in another one? Any help would be greatly appreciated. It appears that maybe it is defining the property of VDDIR before it is getting the value of MAINDIR...if so how can I ensure that MAINDIR is populated first. TIA. Here is an excerpt from the WiX tutorial that shows how to do it, but I can't seem to make it work. Anyone able to get this to work? Property Id=INSTALLDIR IniFileSearch Id='AcmeFoobarIniFile' Type='directory' Name='SampleRegistry.ini' Section='Sample' Key='InstallDir' / /Property There might be cases when simply knowing the directory is not enough: you have to look into the directory and make sure a given file exists there. Depth = n can be used to instruct the installer to look n levels deeper than the specified Path. Zero or a missing Depth attribute means only to look in the specified folder, not below it. We use square brackets in Path to tell the installer to use the value of the INSTALLDIR property-bracketed names will be looked up and if found, replaced with their actual value. If not found, the string will remain unchanged. Property Id=FILEEXISTS DirectorySearch Id=CheckFileDir Path=[INSTALLDIR] Depth=0 FileSearch Id=CheckFile Name=Lookfor.txt / /DirectorySearch /Property NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. - 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.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. - 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.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https
Re: [WiX-users] Adding tons of files to an MSI
take a look at the tallow.exe command...very helpful for this type of situation. From: [EMAIL PROTECTED] on behalf of Very Secret Sent: Tue 2/6/2007 4:31 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Adding tons of files to an MSI Can anyone help me to automatically add a directory and all its contents to an MSI? The problem: I have a directory whose contents is auto generated and therefore can be considered fairly random. The directory may contain thousands of files so adding them manually with the File ... tag is not an option. My question: How can I add the directory, say myDir, and all the files in myDir to the MSI automatically? Are there some File Source=myDir\* ... / option? (I am using the latest version of Wix 3) - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Determine selected features from tree
New to Wix I see how to set the 'level' attribute to determine whether the item is to be enabled or disabled by default in the feature tree. I have two features in my feature tree and I want to be able to kick of different custom actions based on what features the end user selects during the install. I'm sure there is an easy way to determine what items the user selected, but have failed to locate it thus far. Any help would be appreciated. Thanks. NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
