Re: [WiX-users] VS11 and WixProj
Latest WiX release is not Beta. It's 2719. On Thu, Mar 22, 2012 at 11:23 AM, ShitalKumar Mehta (Synergy Technologies LLC) v-shm...@microsoft.com wrote: I suppose as per March 10 post from Rob, latest WIX Release [3.6 beta] has support for VS11. VS11, however wouldn't show templates for Windows Installer XML, so maybe it's related to how I have setup VS11. WIX 3.6 Beta was installed before VS11 was installed. In VS2010: I see that I have WIX folder under C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\ItemTemplates. In VS11: C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\ItemTemplates doesn't have the templates. I am reinstalling WIX 3.6 Beta to see if it detects VS11 and populates templates correctly. In Repair mode, it just reconfirms that its installed correctly for VS2010 and before. It does nothing for VS11. Thanks, Shital -Original Message- From: ShitalKumar Mehta (Synergy Technologies LLC) Sent: Thursday, March 22, 2012 10:38 AM To: wix-users@lists.sourceforge.net Subject: VS11 and WixProj I have side by side installation of VS2010 and VS11. When I open my WIX Setup Project I get error while loading WIX Projects. What's the story of VS11 support for .WIXProj? My Setup Project has following. 1. Setup [WIXProj] 2. Couple of other .MSM [WIXProj] 3. One Custom Action DLL. 4. A DBProj Thanks, Shital Mehta IT Developer -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn: cache only Burn engine?
If the user renames the executable, then the default prompt for the executable will be incorrect but he or she can still browse to it with the old name. On Wed, Mar 21, 2012 at 9:43 AM, Vadym Verba vve...@sdl.com wrote: Hello. Recently we have some problem with bundle maintaining. Here is use case: 1. Customer gets cd-layout and renames bundle from OldName to NewName. 2. Then he installs some 2 products from bundle. 3. Then he deletes one and tries to install it again. Boom! Bundle failed with Failed to find payload error, where it refers to original bundle location with OldName. It uses to cache entire bundle and uses it for source prompts, but then I found this in wix history: WixBuild: Version 3.6.2109.0 - RobMen: SFBUG:3197472 - cache only Burn engine, fix up signatures when using attached containers. So I wonder what should my bundle do now, if some mad customer decides to rename or even delete original bundle (to free some disk space for instance)? I see wix installer itself solved this problem by downloading cab from internet, but I don't think this is the option in my case, because we have packages attached to bundle default container (inside bundle in other words). As usual, you are the best and I will appreciate any help here). Maybe make some feature request to allow entire bundle to be cached by setting some attribute? Or it is just by design and we have to tell customer to do not remove or rename cd-layout? BR, Vadym. /pre font face=arial size=1 color=#736F6E bSDL PLC confidential, all rights reserved./b If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us.BR SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207.BR Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. /font -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn: uninstalling an MSI
Which BootstrapperApplication are you using? If you're using wixstdba, I expect it does not handle this scenario well. You'd want to create a BA that is designed to show the MSI UI instead of it's own UI. On Thu, Mar 22, 2012 at 9:17 AM, robert_y...@non.agilent.com wrote: Some further research after looking at some logs : when I install the .msi via msiexec /I msiFileName.msi, CLIENTUILEVEL=0, which I guess is full UI. When uninstalling via the command line below, CLIENTUILEVEL=2 and UILevel=3 (INSTALLUILEVEL_BASIC). So I guess my question is how to get burn to use a different CLIENTUILEVEL for installation vs. uninstallation ? From: YANG,ROBERT Sent: Thursday, March 22, 2012 8:51 AM To: 'wix-users@lists.sourceforge.net' Subject: Burn: uninstalling an MSI Hi all -- I've been tinkering with Wix 3.6 (build 2719), and set up a test bundle which installs a .msi package. I wanted the msi's user interface to be displayed, so I specified DisplayInternalUI=yes in MsiPackage. This all seems to work fine for installation. On uninstallation I wanted to disable change/modify, so I specified DisableModify=yes in the bundle. When I go to uninstall the bundle, rather unexpectedly I see the Resume dialog. The .msi uses the stock version found in Mondo, which apparently is shown on condition Installed AND (RESUME OR Preselected). The Resume dialog is not shown if I simply run msiexec /x msiFileName.msi or do an uninstall of the MSI from Add/Remove Programs. Is there something else I should be doing ? It would be fine to run the uninstall silently, but we need to have the UI shown on installation. Thanks for any advice or pointers ! -Rob -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Repairing ice64
Hi Folks: I'm currently writing the first of what could be many installers for a company. I have the following inside the TARGETDIR directory: Directory Id=ProgramMenuFolder Directory Id=COMPANYSTARTMENUFOLDER Name=Raised Bar Directory Id=ApplicationProgramsFolder Name=Surface Reader/ /Directory /Directory I then have a component that installs a shortcut: DirectoryRef Id=ApplicationProgramsFolder Component Id=ApplicationShortcut Shortcut Id=ApplicationStartMenuShortcut Name=Surface Reader Description=Allow access to MIDI control surfaces Target=[APPLICATIONROOTDIRECTORY]Surface Reader.exe.exe WorkingDirectory=APPLICATIONROOTDIRECTORY/ RemoveFolder Id=ApplicationProgramsFolder On=uninstall/ RegistryValue Root=HKLM Key=Software\Raised Bar\Surface Reader Name=installed Type=integer Value=1 KeyPath=yes/ /Component /DirectoryRef I am successfully removing the ApplicationProgramsFolder, as can be seen above. But I'm getting an ice64 telling me that the COMPANYSTARTMENUFOLDER is not removed. Given that there could be other products in the future, what is the best way of getting around this issue? Any help accepted. Regards Sean. -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn: cache only Burn engine? Source prompt in BA
If the user renames the executable, then the default prompt for the executable will be incorrect but he or she can still browse to it with the old name. Thanks for pointing me to the right direction). For those who might have problems with source prompt in BA here is solution: 1) Subscribe on BootstrapperApplication.ResolveSource event 2) In event handle execute Engine.SetLocalSource(e.PackageOrContainerId, e.PayloadId, new_file_location) (harvest new_file_location data somehow). 3) Before handler return, execute e.Result = Result.Retry Note that after that engine will try to resolve source with provided data only once, so it is up to BA to validate if new_file_location is a valid source and ask user to reenter path if it is needed. But it is still unclear how patch bundle should handle source missing, if it is launched in Patch relation. There is no way to detect main bundle was launched in silence mode and if patch bundle decides to show dialog for source prompt it may hang some installation script (on PowerShell for instance) rather than just fails. /pre font face=arial size=1 color=#736F6E bSDL PLC confidential, all rights reserved./b If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us.BR SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207.BR Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. /font -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Repairing ice64
Add a RemoveFolder to your start menu. RemoveFolder will only remove empty folders. Description Remove an empty folder if the parent component is selected for installation or removal. By default, the folder is the directory of the parent component. This can be overridden by specifying the Directory attribute with a value corresponding to the Id of the directory, or by specifying the Property attribute with a value corresponding to a property that will have a value that resolves to the full path of the folder. -Original Message- From: Sean Farrow [mailto:sean.far...@seanfarrow.co.uk] Sent: Friday, March 23, 2012 2:38 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Repairing ice64 Importance: High Hi Folks: I'm currently writing the first of what could be many installers for a company. I have the following inside the TARGETDIR directory: Directory Id=ProgramMenuFolder Directory Id=COMPANYSTARTMENUFOLDER Name=Raised Bar Directory Id=ApplicationProgramsFolder Name=Surface Reader/ /Directory /Directory I then have a component that installs a shortcut: DirectoryRef Id=ApplicationProgramsFolder Component Id=ApplicationShortcut Shortcut Id=ApplicationStartMenuShortcut Name=Surface Reader Description=Allow access to MIDI control surfaces Target=[APPLICATIONROOTDIRECTORY]Surface Reader.exe.exe WorkingDirectory=APPLICATIONROOTDIRECTORY/ RemoveFolder Id=ApplicationProgramsFolder On=uninstall/ RegistryValue Root=HKLM Key=Software\Raised Bar\Surface Reader Name=installed Type=integer Value=1 KeyPath=yes/ /Component /DirectoryRef I am successfully removing the ApplicationProgramsFolder, as can be seen above. But I'm getting an ice64 telling me that the COMPANYSTARTMENUFOLDER is not removed. Given that there could be other products in the future, what is the best way of getting around this issue? Any help accepted. Regards Sean. -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Burn: uninstalling an MSI
Thanks ! Yes, it's using the standard bootstrapper. In the meantime I hunted through the source and found MsiEngineCalculateInstallLevel, MsiEnginePlanAddPackage and WiuInitializeExternalUI.. wondering if there is a good way to intercept the UI level in a custom BA. Maybe using IBootstrapperEngine somehow ? I think we would only need to do this for the uninstall case. Which BootstrapperApplication are you using? If you're using wixstdba, I expect it does not handle this scenario well. You'd want to create a BA that is designed to show the MSI UI instead of it's own UI. On Thu, Mar 22, 2012 at 9:17 AM, lt;robert_yang@.agilentgt; wrote: Some further research after looking at some logs : when I install the .msi via msiexec /I msiFileName.msi, CLIENTUILEVEL=0, which I guess is full UI. When uninstalling via the command line below, CLIENTUILEVEL=2 and UILevel=3 (INSTALLUILEVEL_BASIC). So I guess my question is how to get burn to use a different CLIENTUILEVEL for installation vs. uninstallation ? From: YANG,ROBERT Sent: Thursday, March 22, 2012 8:51 AM To: 'wix-users@.sourceforge' Subject: Burn: uninstalling an MSI Hi all -- I've been tinkering with Wix 3.6 (build 2719), and set up a test bundle which installs a .msi package. I wanted the msi's user interface to be displayed, so I specified DisplayInternalUI=yes in MsiPackage. This all seems to work fine for installation. On uninstallation I wanted to disable change/modify, so I specified DisableModify=yes in the bundle. When I go to uninstall the bundle, rather unexpectedly I see the Resume dialog. The .msi uses the stock version found in Mondo, which apparently is shown on condition Installed AND (RESUME OR Preselected). The Resume dialog is not shown if I simply run msiexec /x msiFileName.msi or do an uninstall of the MSI from Add/Remove Programs. Is there something else I should be doing ? It would be fine to run the uninstall silently, but we need to have the UI shown on installation. Thanks for any advice or pointers ! -Rob [...] -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-uninstalling-an-MSI-tp7396006p7399203.html Sent from the wix-users mailing list archive at Nabble.com. -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] DTF question
Hi everyone, I'm wanting to write a little utility to help our deployments server monitor installations. I can use the Database class on an MSI and get its productcode with an appropriate query and hence then verify that it is installed. However, MSPs don't seem so straightforward. What's a good way to, given a path to an MSP file, determine if it has been installed (i.e., the equivalent of seeing if it is visible in Programs and Features)? Assume no obvious connection between its filename and that of what it patches. Keith Douglas Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6 keith.doug...@statcan.gc.ca Telephone | Téléphone 613-951-4405 Facsimile | Télécopieur 613-951-1966 Government of Canada | Gouvernement du Canada -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] DTF question
1) Enumerate the installed Product Codes; 2) Select the one of interest; 3) Enumerate the patches installed to that ProductCode; 4) Check if the patch of interest is one of the installed patches to that ProductCode. Fast and dirty. I'm sure there are more elegant ways to get it. -- John Merryweather Cooper Build Install Engineer - ESA Jack Henry Associates, Inc.® Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: keith.doug...@statcan.gc.ca [mailto:keith.doug...@statcan.gc.ca] Sent: Friday, March 23, 2012 3:28 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] DTF question Hi everyone, I'm wanting to write a little utility to help our deployments server monitor installations. I can use the Database class on an MSI and get its productcode with an appropriate query and hence then verify that it is installed. However, MSPs don't seem so straightforward. What's a good way to, given a path to an MSP file, determine if it has been installed (i.e., the equivalent of seeing if it is visible in Programs and Features)? Assume no obvious connection between its filename and that of what it patches. Keith Douglas Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6 Statistique Canada | 170, promenade Tunney's Pasture, Ottawa ON K1A 0T6 keith.doug...@statcan.gc.ca Telephone | Téléphone 613-951-4405 Facsimile | Télécopieur 613-951-1966 Government of Canada | Gouvernement du Canada -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ 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. -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] harvesting an out of process com server
Hi: I'm adding an out of process com server to my installation that I'd normally register with /regserver on the command line. How would I go about adding the necessary entries to a wix installer-I know I can use heat to register an inproc com server. Any help appreciated. Regards Sean. -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] using a 32-bit project in a 64-bit installer
Hi: I'm writing an installer in visual studio. I have a 32-bit com server that is written in atl. This com server does not have a 64-build configuration and therefore doesn't build when I build the 64-bit configurations. If I add the Project.TargetPath to my installer, what path will this resolve to. Given that the target path on a 32-bit build is $(SolutionDir)\$(Configuration). Any help appreciated. Regards Sean. -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
