Re: [WiX-users] Registering a Windows Service that is a C OM executable
Thanks for all your help, Bob and Phil. -Matt - 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] stop service before installvalidate
Also, I'm pretty sure that InstallValidate takes account of the ServiceControl table when it's deciding whether to show a FilesInUse dialog, if that's the issue. Phil Wilson From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson Sent: Wednesday, March 28, 2007 9:01 PM To: Bei Liu (Volt) Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] stop service before installvalidate Bei Liu (Volt) wrote: I'm trying to stop the services before installvalidate when uninstall. However, I got the following error. Per the doc, the services actions must come during the transaction because they modify system state. Actions that modify the system can't be immediate. -- sig://boB http://bobs.org - 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] User specific permissions
I'm trying to create a folder that's either writable by the installing user, or by all users, depending on ALLUSERS. What would I need to do to set permissions specific to the installing user? I attempted to use the USERSID property, and got no error, but the resulting older had an odd BUILTIN\BUILTIN user entry with a question mark, instead of one for the user who performed the install. Ive basically done the following: Component Id=workfolder.all ... Location=either ConditionALLUSERS/Condition CreateFolder Permission User=Everyone GenericAll=yes / /CreateFolder /Component Component Id=workfolder.single ... Location=either ConditionNOT ALLUSERS/Condition CreateFolder Permission User=[USERSID] GenericAll=yes / /CreateFolder /Component - 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] Problems with MFC and CRT 8 Merge Modules
I added this to my project file: Merge Id='CRT80' Language='1033' SourceFile='c:\program files\common files\merge modules\Microsoft_VC80_CRT_x86.msm' DiskId='1' / Merge Id='MFC80' Language='1033' SourceFile='c:\program files\common files\merge modules\Microsoft_VC80_MFC_x86.msm' DiskId='1' / and then added this to my main feature: MergeRef Id=CRT80 / MergeRef Id=MFC80 / When I built with WiX, I got tons of ICE warnings as shown below. Is this expected? Microsoft claim in msdn that you should do this: From the Project menu, point to Add and click Merge Module. Select Microsoft_VC80_CRT_x86.msm and Microsoft_VC80_MFC_x86.msm, and click OK. Anthony Wieser Wieser Software Ltd I:\2005\CPP\NDS\HexagonWx\HexagonWx.wxs(55,0): Warning LGHT1055: The InstallExecuteSequence table contains an action 'SxsInstallCA' which cannot be merged from the merge module 'c:\program files\common files\merge modules\Microsoft_VC80_MFC_x86.msm'. This action is likely colliding with an action in the database that is being created. The colliding action may have been authored in the database or merged in from another merge module. If this is a standard action, it is likely colliding due to a difference in the condition for the action in the database and merge module. If this is a custom action, it should only be declared in the database or one merge module. I:\2005\CPP\NDS\HexagonWx\HexagonWx.wxs(55,0): Warning LGHT1055: The InstallExecuteSequence table contains an action 'SxsUninstallCA' which cannot be merged from the merge module 'c:\program files\common files\merge modules\Microsoft_VC80_MFC_x86.msm'. This action is likely colliding with an action in the database that is being created. The colliding action may have been authored in the database or merged in from another merge module. If this is a standard action, it is likely colliding due to a difference in the condition for the action in the database and merge module. If this is a custom action, it should only be declared in the database or one merge module. light.exe(0,0): Warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.762.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): Warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.100.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): Warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.101.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): Warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.103.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): Warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.104.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): Warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.193.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): Warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.762.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E light.exe(0,0): Warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.100.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E light.exe(0,0): Warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.101.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E light.exe(0,0): Warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.103.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E light.exe(0,0): Warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.104.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E light.exe(0,0): Warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.193.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E light.exe(0,0): Warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Registry, Column: Registry, Key(s): reg_downlevel_manifest.8.0.50727.100.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): Warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Registry, Column:
Re: [WiX-users] Problems with MFC and CRT 8 Merge Modules
The Warnings are okay - it's errors you want to worry about. I get the same verification reports and a big fat Vista verification logo to go with them :-) -- View this message in context: http://www.nabble.com/Problems-with-MFC-and-CRT-8-Merge-Modules-tf3487580.html#a9738055 Sent from the wix-users mailing list archive at Nabble.com. - 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] Conditional RemoveFiles on Uninstall
You can probably declare your 'RemoveFile' ines in a component that has a component condition triggered by a property that your user can configure via a checkbox in your UI. I believe that 'RemoveFile' lines work on install and all files will be removed on uninstall so probably won't be the solution for your described needs. Best of luck. -- View this message in context: http://www.nabble.com/Conditional-RemoveFiles-on-Uninstall-tf3480347.html#a9738169 Sent from the wix-users mailing list archive at Nabble.com. - 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 do i embedd and install a 3rd party msi (eg directx or wse runtime) if not already installed
I regularly install DirectX as part of my WiX packages, here's the code for a file I just include for the functionality to 'appear': ?xml version='1.0' encoding=utf-8? Include xmlns='http://schemas.microsoft.com/wix/2003/01/wi' Feature Id=DirectX9 Title=DirectX9 Level=100 Description=DirectX9 AllowAdvertise=no Display=hidden ComponentRef Id=DirectX9 / /Feature Property Id=DirectXDllDirectX9\dsetup.dll/Property Property Id=InstallDXNo/Property CustomAction Id=SetInstallDX Property=InstallDX Value=Yes / CustomAction Id=MsiInstDX BinaryKey=MsiCustomActions DllEntry=MsiInstDX Impersonate=yes / CustomAction Id=MsiInstDXProp Property=MsiInstDXDeferred Value=[UILevel];[SourceDir][DirectXDll] Impersonate=yes / CustomAction Id=MsiInstDXDeferred BinaryKey=MsiCustomActions DllEntry=MsiInstDX Execute=deferred Impersonate=yes / InstallExecuteSequence Custom Action=SetInstallDX After=LaunchConditions(NOT Installed) AND ((DXMajorVersion lt; 4) OR (DXMajorVersion = 4 AND DXMinorVersion lt; 9))/Custom Custom Action=MsiInstDX After=InstallInitialize(NOT Installed) AND (InstallDX = Yes)/Custom Custom Action=MsiInstDXProp After=MsiInstDX(NOT Installed) AND (InstallDX = Yes)/Custom Custom Action=MsiInstDXDeferred After=MsiInstDXProp(NOT Installed) AND (InstallDX = Yes)/Custom /InstallExecuteSequence InstallUISequence Custom Action=SetInstallDX After=LaunchConditions(NOT Installed) AND ((DXMajorVersion lt; 4) OR (DXMajorVersion = 4 AND DXMinorVersion lt; 9))/Custom Custom Action='SetRebootRequired' After='SetInstallDX'(NOT Installed) AND (InstallDX = Yes)/Custom /InstallUISequence DirectoryRef Id=TARGETDIR Directory Id=DirectX9 Name=DirectX9 src=Installs\Common\DirectX9c Component Id=DirectX9 Guid=80A814B2-E059-4A83-9533-C9A9A694C869 DiskId=1 File Id=DX9BDA.cab Name=BDA.cab Compressed=no / File Id=DX9BDANT.cab Name=BDANT.cab Compressed=no / File Id=DX9BDAXP.cab Name=BDAXP.cab Compressed=no / File Id=DX9DirectX.cab Name=DirectX.cab Compressed=no / File Id=DX9dsetup32.dll Name=dsetup32.dll Compressed=no / File Id=DX9DSETUP.dll Name=DSETUP.dll Compressed=no / File Id=DX9dxnt.cab Name=dxnt.cab Compressed=no / File Id=DX9DXSETUP.exe Name=DXSETUP.exe Compressed=no / File Id=DX9ManagedDX.CAB Name=ManagdDX.CAB LongName=ManagedDX.CAB Compressed=no / /Component /Directory /DirectoryRef /Include AS for other MSIs (Adobe Reader, for example) so long as there's only one to install, you can call the MSI in a deferred custom action that'll launch after your own installation had finished - I've done that a few times with great success too. Good luck, Gareth -- View this message in context: http://www.nabble.com/How-do-i-embedd-and-install-a-3rd-party-msi-%28eg-directx-or-wse-runtime%29-if-not-already-installed-tf3469351.html#a9738492 Sent from the wix-users mailing list archive at Nabble.com. - 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 do i embedd and install a 3rd party msi (eg directx or wse runtime) if not already installed
Create a bootstrapper. Check out msdn documentation on the msbuild GenerateBootstrapper task. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gareth at Serif Sent: Thursday, March 29, 2007 10:23 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How do i embedd and install a 3rd party msi (eg directx or wse runtime) if not already installed I regularly install DirectX as part of my WiX packages, here's the code for a file I just include for the functionality to 'appear': ?xml version='1.0' encoding=utf-8? Include xmlns='http://schemas.microsoft.com/wix/2003/01/wi' Feature Id=DirectX9 Title=DirectX9 Level=100 Description=DirectX9 AllowAdvertise=no Display=hidden ComponentRef Id=DirectX9 / /Feature Property Id=DirectXDllDirectX9\dsetup.dll/Property Property Id=InstallDXNo/Property CustomAction Id=SetInstallDX Property=InstallDX Value=Yes / CustomAction Id=MsiInstDX BinaryKey=MsiCustomActions DllEntry=MsiInstDX Impersonate=yes / CustomAction Id=MsiInstDXProp Property=MsiInstDXDeferred Value=[UILevel];[SourceDir][DirectXDll] Impersonate=yes / CustomAction Id=MsiInstDXDeferred BinaryKey=MsiCustomActions DllEntry=MsiInstDX Execute=deferred Impersonate=yes / InstallExecuteSequence Custom Action=SetInstallDX After=LaunchConditions(NOT Installed) AND ((DXMajorVersion lt; 4) OR (DXMajorVersion = 4 AND DXMinorVersion lt; 9))/Custom Custom Action=MsiInstDX After=InstallInitialize(NOT Installed) AND (InstallDX = Yes)/Custom Custom Action=MsiInstDXProp After=MsiInstDX(NOT Installed) AND (InstallDX = Yes)/Custom Custom Action=MsiInstDXDeferred After=MsiInstDXProp(NOT Installed) AND (InstallDX = Yes)/Custom /InstallExecuteSequence InstallUISequence Custom Action=SetInstallDX After=LaunchConditions(NOT Installed) AND ((DXMajorVersion lt; 4) OR (DXMajorVersion = 4 AND DXMinorVersion lt; 9))/Custom Custom Action='SetRebootRequired' After='SetInstallDX'(NOT Installed) AND (InstallDX = Yes)/Custom /InstallUISequence DirectoryRef Id=TARGETDIR Directory Id=DirectX9 Name=DirectX9 src=Installs\Common\DirectX9c Component Id=DirectX9 Guid=80A814B2-E059-4A83-9533-C9A9A694C869 DiskId=1 File Id=DX9BDA.cab Name=BDA.cab Compressed=no / File Id=DX9BDANT.cab Name=BDANT.cab Compressed=no / File Id=DX9BDAXP.cab Name=BDAXP.cab Compressed=no / File Id=DX9DirectX.cab Name=DirectX.cab Compressed=no / File Id=DX9dsetup32.dll Name=dsetup32.dll Compressed=no / File Id=DX9DSETUP.dll Name=DSETUP.dll Compressed=no / File Id=DX9dxnt.cab Name=dxnt.cab Compressed=no / File Id=DX9DXSETUP.exe Name=DXSETUP.exe Compressed=no / File Id=DX9ManagedDX.CAB Name=ManagdDX.CAB LongName=ManagedDX.CAB Compressed=no / /Component /Directory /DirectoryRef /Include AS for other MSIs (Adobe Reader, for example) so long as there's only one to install, you can call the MSI in a deferred custom action that'll launch after your own installation had finished - I've done that a few times with great success too. Good luck, Gareth -- View this message in context: http://www.nabble.com/How-do-i-embedd-and-install-a-3rd-party-msi-%28eg-directx-or-wse-runtime%29-if-not-already-installed-tf3469351.html#a9738492 Sent from the wix-users mailing list archive at Nabble.com. - 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 - 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] Conditional Install of the Office 2003 PIAs
I have an installer for a product with an optional Office 2003 Addin that requires the Office 2003 PIAs, and I'm trying to figure out how I can install the assemblies only if the component is selected in the feature tree. A bootstrapper will launch the PIA MSI beforehand, wouldn't it? I'm currently taking a look at the CC addin that Rob blogged about here http://blogs.msdn.com/robmen/archive/2006/06/20/641202.aspx , but I have a feeling that this is going to install the PIAs, then run the addin setup. Is there an MSM for the PIAs that I could use instead? That way, the module could be a component of the optional feature. As an alternative, I'm thinking about checking the registry to see which Office applications are installed. Another possibility would be to run a custom action to actually shell out and run msiexec on the included package, but that seems a little messy for the end user (although I suppose it could run silently). Any suggestions on how to do this? Thanks, Chris - 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] Problems with MFC and CRT 8 Merge Modules
Yes, it sounds like those warnings are normal for the merge modules and Wix. The modules seem to work though, so I've just ignored the warning for now. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anthony Wieser Sent: Thursday, March 29, 2007 12:51 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Problems with MFC and CRT 8 Merge Modules I added this to my project file: Merge Id='CRT80' Language='1033' SourceFile='c:\program files\common files\merge modules\Microsoft_VC80_CRT_x86.msm' DiskId='1' / Merge Id='MFC80' Language='1033' SourceFile='c:\program files\common files\merge modules\Microsoft_VC80_MFC_x86.msm' DiskId='1' / and then added this to my main feature: MergeRef Id=CRT80 / MergeRef Id=MFC80 / When I built with WiX, I got tons of ICE warnings as shown below. Is this expected? Microsoft claim in msdn that you should do this: From the Project menu, point to Add and click Merge Module. Select Microsoft_VC80_CRT_x86.msm and Microsoft_VC80_MFC_x86.msm, and click OK. Anthony Wieser Wieser Software Ltd I:\2005\CPP\NDS\HexagonWx\HexagonWx.wxs(55,0): Warning LGHT1055: The InstallExecuteSequence table contains an action 'SxsInstallCA' which cannot be merged from the merge module 'c:\program files\common files\merge modules\Microsoft_VC80_MFC_x86.msm'. This action is likely colliding with an action in the database that is being created. The colliding action may have been authored in the database or merged in from another merge module. If this is a standard action, it is likely colliding due to a difference in the condition for the action in the database and merge module. If this is a custom action, it should only be declared in the database or one merge module. I:\2005\CPP\NDS\HexagonWx\HexagonWx.wxs(55,0): Warning LGHT1055: The InstallExecuteSequence table contains an action 'SxsUninstallCA' which cannot be merged from the merge module 'c:\program files\common files\merge modules\Microsoft_VC80_MFC_x86.msm'. This action is likely colliding with an action in the database that is being created. The colliding action may have been authored in the database or merged in from another merge module. If this is a standard action, it is likely colliding due to a difference in the condition for the action in the database and merge module. If this is a custom action, it should only be declared in the database or one merge module. light.exe(0,0): Warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.762.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): Warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.100.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): Warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.101.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): Warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.103.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): Warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.104.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): Warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.193.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E light.exe(0,0): Warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.762.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E light.exe(0,0): Warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.100.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E light.exe(0,0): Warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.101.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E light.exe(0,0): Warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.103.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E light.exe(0,0): Warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.104.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E light.exe(0,0): Warning LGHT1076: ICE03: String overflow (greater than length permitted in column); Table: Component, Column: KeyPath, Key(s):
[WiX-users] How to install a windows service with account.
Hi, I have an urgent problem about wix version 2. It is needed to allow user to assign the startname/account and password of a windows service instead of using LocalSystem. I want to assign it through two ways: 1. Commandline at time of installation. 2. UI dialog ask for account/password. I used public Property to assign account/password through command line. But the service cannot get started. Does anybody know what I need to do this job with the build in functions of wix? Or I have to write my own custom action? Time is urgent, please help. Thanks a lot. Shi- 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] Conditional Install of the Office 2003 PIAs
I don't think it's worth the added complication. Just install the PIAs in the bootstrapper. Phil Wilson From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Bardon Sent: Thursday, March 29, 2007 10:48 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Conditional Install of the Office 2003 PIAs I have an installer for a product with an optional Office 2003 Addin that requires the Office 2003 PIAs, and I'm trying to figure out how I can install the assemblies only if the component is selected in the feature tree. A bootstrapper will launch the PIA MSI beforehand, wouldn't it? I'm currently taking a look at the CC addin that Rob blogged about here http://blogs.msdn.com/robmen/archive/2006/06/20/641202.aspx , but I have a feeling that this is going to install the PIAs, then run the addin setup. Is there an MSM for the PIAs that I could use instead? That way, the module could be a component of the optional feature. As an alternative, I'm thinking about checking the registry to see which Office applications are installed. Another possibility would be to run a custom action to actually shell out and run msiexec on the included package, but that seems a little messy for the end user (although I suppose it could run silently). Any suggestions on how to do this? Thanks, Chris - 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] Windows Installer and multiple languages - wrong language on error dialog buttons
Hello, I'm building installation with multiple language support and encountered a problem. I'm following WiX tutorial: 1. Build istallation for each language separately 2. Take first language as a base ant create tranforms for all other languages: msitran.exe -g install_de-de.msi install_en-us.msi en-us.mst 3. Put all transforms together: msidb.exe -d install_de_de.msi -r en-us.mst Then I'm starting installation from bootstap program : msiexec.exe /i install_de_de.msi TRANSFORMS=:en-us.mst It works fine for the most part, but when error dialog pops up, it has text in correct language, but buttons (like Yes,No, Cancel) are displayed in the base language, not in the transform language. For example above, where I used German as base language and English was added as transform, error dialogs display English messages, but buttons are in German. My computer localle is set to English, so it can't be explained by localle setting. Anybody has any ideas? Thank you, Igor -- View this message in context: http://www.nabble.com/Windows-Installer-and-multiple-languages---wrong-language-on-error-dialog-buttons-tf3488097.html#a9739779 Sent from the wix-users mailing list archive at Nabble.com. - 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] Fwd: RE : acl a directory
-- Forwarded message -- From: Justin Dearing [EMAIL PROTECTED] Date: Mar 29, 2007 2:33 PM Subject: Re: [WiX-users] RE : acl a directory To: Jacquet Fabian [EMAIL PROTECTED] If this is WiX version 2 then adding the permission element by default will remove the inherit parent ACLs from the folder. You have to add the extended attribute. You also have to link wixca.lib into your MSI. Example: Directory Id=DB_FOLDER Name=database: CreateFolder !-- In order to inherit permissions you must link wixca.lib into the msi and specify the attribute Extended=yes -- Permission User=Users Extended=yes GenericRead=yes GenericWrite=yes / File Id=Database Name=example.mdb Source=..\database\example.mdb / /CreateFolder /Directory For WiX version 3 the rules are different. If you are using WiX version 3 I would like to know how exactly you get this to work. On 3/29/07, Jacquet Fabian [EMAIL PROTECTED] wrote: The tag Permission let you put ACL on a directory. You only can put this as child as CreateFolder tag. -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Lindsay Harris Envoyé : jeudi 29 mars 2007 8:01 À : DevDiv WiX; wix-users@lists.sourceforge.net Cc : David Voskuil Objet : [WiX-users] acl a directory Does anyone know if there is a simple way to acl a directory in WIX? Or would this be a custom action call? Thanks! Lindsay Harris - 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 - 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] problem when run custom action before costinitialize
Can I schedule a custom action that using the directory manager before costinitialize? If not, is there a way to run an application that installed by the msi before costinitialize? Thanks, - 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] problem when run custom action before costinitialize
1. Not as far as I know. 2. That doesn't make any sense to me. CostInitialize happens long before the transaction that installs things happens. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bei Liu (Volt) Sent: Thursday, March 29, 2007 1:12 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] problem when run custom action before costinitialize Can I schedule a custom action that using the directory manager before costinitialize? If not, is there a way to run an application that installed by the msi before costinitialize? Thanks, - 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] problem when run custom action before costinitialize
2. I just want to run it when uninstall. Is that possible? Thanks, From: Rob Mensching Sent: Thursday, March 29, 2007 1:25 PM To: Bei Liu (Volt); wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize 1. Not as far as I know. 2. That doesn't make any sense to me. CostInitialize happens long before the transaction that installs things happens. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bei Liu (Volt) Sent: Thursday, March 29, 2007 1:12 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] problem when run custom action before costinitialize Can I schedule a custom action that using the directory manager before costinitialize? If not, is there a way to run an application that installed by the msi before costinitialize? Thanks, - 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] failed to initialize xml utilities
I'm having problems with my install, on just one machine. It goes along fine, then just starts rolling back. It doesn't give an error message or anything. I logged the install, and found the following error in the log, just before it starts rolling back. MSI (s) (D4:B8) [13:09:25:454]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI1D6.tmp, Entrypoint: ExecXmlFile ExecXmlFile: Error 0x800401f3: failed to initialize xml utilities Anyone seen this before. The same msi works without any problems on other machines. It seems to be just this one, that has a problem. What could be causing this? - 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] failed to initialize xml utilities
MSXML busted? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam Sent: Thursday, March 29, 2007 1:37 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] failed to initialize xml utilities I'm having problems with my install, on just one machine. It goes along fine, then just starts rolling back. It doesn't give an error message or anything. I logged the install, and found the following error in the log, just before it starts rolling back. MSI (s) (D4:B8) [13:09:25:454]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI1D6.tmp, Entrypoint: ExecXmlFile ExecXmlFile: Error 0x800401f3: failed to initialize xml utilities Anyone seen this before. The same msi works without any problems on other machines. It seems to be just this one, that has a problem. What could be causing this? - 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 - 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] problem when run custom action before costinitialize
Why? What are you trying to do? From: Bei Liu (Volt) Sent: Thursday, March 29, 2007 1:30 PM To: Rob Mensching; wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize 2. I just want to run it when uninstall. Is that possible? Thanks, From: Rob Mensching Sent: Thursday, March 29, 2007 1:25 PM To: Bei Liu (Volt); wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize 1. Not as far as I know. 2. That doesn't make any sense to me. CostInitialize happens long before the transaction that installs things happens. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bei Liu (Volt) Sent: Thursday, March 29, 2007 1:12 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] problem when run custom action before costinitialize Can I schedule a custom action that using the directory manager before costinitialize? If not, is there a way to run an application that installed by the msi before costinitialize? Thanks, - 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] problem when run custom action before costinitialize
I have a service installed by my installer. I'll run after install. I want to remove it before uninstall. Also don't want to get the file in use popup. From: Rob Mensching Sent: Thursday, March 29, 2007 2:09 PM To: Bei Liu (Volt); wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize Why? What are you trying to do? From: Bei Liu (Volt) Sent: Thursday, March 29, 2007 1:30 PM To: Rob Mensching; wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize 2. I just want to run it when uninstall. Is that possible? Thanks, From: Rob Mensching Sent: Thursday, March 29, 2007 1:25 PM To: Bei Liu (Volt); wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize 1. Not as far as I know. 2. That doesn't make any sense to me. CostInitialize happens long before the transaction that installs things happens. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bei Liu (Volt) Sent: Thursday, March 29, 2007 1:12 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] problem when run custom action before costinitialize Can I schedule a custom action that using the directory manager before costinitialize? If not, is there a way to run an application that installed by the msi before costinitialize? Thanks, - 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] problem when run custom action before costinitialize
You should be able to just schedule the service to be stopped and no file-in-use error should occur. From: Bei Liu (Volt) Sent: Thursday, March 29, 2007 2:11 PM To: Rob Mensching; wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize I have a service installed by my installer. I'll run after install. I want to remove it before uninstall. Also don't want to get the file in use popup. From: Rob Mensching Sent: Thursday, March 29, 2007 2:09 PM To: Bei Liu (Volt); wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize Why? What are you trying to do? From: Bei Liu (Volt) Sent: Thursday, March 29, 2007 1:30 PM To: Rob Mensching; wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize 2. I just want to run it when uninstall. Is that possible? Thanks, From: Rob Mensching Sent: Thursday, March 29, 2007 1:25 PM To: Bei Liu (Volt); wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize 1. Not as far as I know. 2. That doesn't make any sense to me. CostInitialize happens long before the transaction that installs things happens. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bei Liu (Volt) Sent: Thursday, March 29, 2007 1:12 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] problem when run custom action before costinitialize Can I schedule a custom action that using the directory manager before costinitialize? If not, is there a way to run an application that installed by the msi before costinitialize? Thanks, - 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] problem when run custom action before costinitialize
I did that, Component... File ... Name=MyService.exe /File ServiceControl Id=MyService Name=MyService.exe Stop=uninstall Remove=uninstall Wait=yes ServiceArgument /d [INSTALLDIR]EF.G/ServiceArgument /ServiceControl /Component I still get file-in-use popup when uninstall.(Stop service is happened after CostFinilize, InstallValidate) From: Rob Mensching Sent: Thursday, March 29, 2007 2:41 PM To: Bei Liu (Volt); wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize You should be able to just schedule the service to be stopped and no file-in-use error should occur. From: Bei Liu (Volt) Sent: Thursday, March 29, 2007 2:11 PM To: Rob Mensching; wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize I have a service installed by my installer. I'll run after install. I want to remove it before uninstall. Also don't want to get the file in use popup. From: Rob Mensching Sent: Thursday, March 29, 2007 2:09 PM To: Bei Liu (Volt); wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize Why? What are you trying to do? From: Bei Liu (Volt) Sent: Thursday, March 29, 2007 1:30 PM To: Rob Mensching; wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize 2. I just want to run it when uninstall. Is that possible? Thanks, From: Rob Mensching Sent: Thursday, March 29, 2007 1:25 PM To: Bei Liu (Volt); wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize 1. Not as far as I know. 2. That doesn't make any sense to me. CostInitialize happens long before the transaction that installs things happens. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bei Liu (Volt) Sent: Thursday, March 29, 2007 1:12 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] problem when run custom action before costinitialize Can I schedule a custom action that using the directory manager before costinitialize? If not, is there a way to run an application that installed by the msi before costinitialize? Thanks, - 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] RE : acl a directory
I am using version 2. This is great information, thanks! =) Lindsay -Original Message- From: Justin Dearing [mailto:[EMAIL PROTECTED] Sent: Thursday, March 29, 2007 11:37 AM To: Lindsay Harris; DevDiv WiX; wix-users@lists.sourceforge.net; David Voskuil Subject: Fwd: [WiX-users] RE : acl a directory -- Forwarded message -- From: Justin Dearing [EMAIL PROTECTED] Date: Mar 29, 2007 2:33 PM Subject: Re: [WiX-users] RE : acl a directory To: Jacquet Fabian [EMAIL PROTECTED] If this is WiX version 2 then adding the permission element by default will remove the inherit parent ACLs from the folder. You have to add the extended attribute. You also have to link wixca.lib into your MSI. Example: Directory Id=DB_FOLDER Name=database: CreateFolder !-- In order to inherit permissions you must link wixca.lib into the msi and specify the attribute Extended=yes -- Permission User=Users Extended=yes GenericRead=yes GenericWrite=yes / File Id=Database Name=example.mdb Source=..\database\example.mdb / /CreateFolder /Directory For WiX version 3 the rules are different. If you are using WiX version 3 I would like to know how exactly you get this to work. On 3/29/07, Jacquet Fabian [EMAIL PROTECTED] wrote: The tag Permission let you put ACL on a directory. You only can put this as child as CreateFolder tag. -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Lindsay Harris Envoyé : jeudi 29 mars 2007 8:01 À : DevDiv WiX; wix-users@lists.sourceforge.net Cc : David Voskuil Objet : [WiX-users] acl a directory Does anyone know if there is a simple way to acl a directory in WIX? Or would this be a custom action call? Thanks! Lindsay Harris - 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 - 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] Service and virtual directories.
I tried to use WebVirtualDir Id='TestWebVirtualDir' Alias='Test' Directory='InstallDir' WebSite='DefaultWebSite' WebApplication Id='TestWebApplication' Name='Test' / /WebVirtualDir And WebSite Id='DefaultWebSite' Description='Default Web Site' WebAddress Id='AllUnassigned' Port='80' / /WebSite But I get an error indicating the the IIS tables could not be accessed. Any ideas on what I could change so that I can create a virtual directory. Next I would like to install a .NET Windows Service. If I do this manually I use installutil. Does the following also use the equivalent? ServiceInstall Id='MyServiceInstall' DisplayName='My Test Service' Name='MyServiceExeName' ErrorControl='normal' Start='auto' Type='ownProcess' Vital='yes' / ServiceControl Id='MyServiceControl' Name='MyServiceExeName' Start='install' Stop='uninstall' Remove='uninstall' / Is there an explanation somewhere about these tasks and what the options available are? Thank you. Kevin - 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] problem when run custom action before costinitialize
You could have a race condition (we did). I don't know if it's Windows Installer or a WiX Custom Action that stops services but, it appears that it continues when the service controller reports that the service is stopped. The service controller reports a service as stopped when the service successfully responds to a stop request (i.e. a ServiceBase based class' OnStop method completes successfully). But, the files are in-use until the process exits. If your OnStop method just starts the shutdown and then returns, you have a problem. Your OnStop method should start the shutdown of the service threads and then wait for them to complete before it exits. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bei Liu (Volt) Sent: Thursday, March 29, 2007 5:54 PM To: Rob Mensching; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] problem when run custom action before costinitialize I did that, Component... File ... Name=MyService.exe /File ServiceControl Id=MyService Name=MyService.exe Stop=uninstall Remove=uninstall Wait=yes ServiceArgument /d [INSTALLDIR]EF.G/ServiceArgument /ServiceControl /Component I still get file-in-use popup when uninstall.(Stop service is happened after CostFinilize, InstallValidate) From: Rob Mensching Sent: Thursday, March 29, 2007 2:41 PM To: Bei Liu (Volt); wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize You should be able to just schedule the service to be stopped and no file-in-use error should occur. From: Bei Liu (Volt) Sent: Thursday, March 29, 2007 2:11 PM To: Rob Mensching; wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize I have a service installed by my installer. I'll run after install. I want to remove it before uninstall. Also don't want to get the file in use popup. From: Rob Mensching Sent: Thursday, March 29, 2007 2:09 PM To: Bei Liu (Volt); wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize Why? What are you trying to do? From: Bei Liu (Volt) Sent: Thursday, March 29, 2007 1:30 PM To: Rob Mensching; wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize 2. I just want to run it when uninstall. Is that possible? Thanks, From: Rob Mensching Sent: Thursday, March 29, 2007 1:25 PM To: Bei Liu (Volt); wix-users@lists.sourceforge.net Subject: RE: problem when run custom action before costinitialize 1. Not as far as I know. 2. That doesn't make any sense to me. CostInitialize happens long before the transaction that installs things happens. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bei Liu (Volt) Sent: Thursday, March 29, 2007 1:12 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] problem when run custom action before costinitialize Can I schedule a custom action that using the directory manager before costinitialize? If not, is there a way to run an application that installed by the msi before costinitialize? Thanks, - 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] file association issue
Hi, During the installation of our product (our product is a multimedia player), we are doing some file association with our product. Our requirement is; Allow multiple versioins of player to coexist. Issue: When newer version(V2) is installed over the earlier version( V1), all the files are getting associated with V2 as expected. when we un-install V2, we want file association reverted to V1, but this is not happening. Below given is the WiX code I am using for file assoication: ProgId Id='Test.abcdfile' Description='Test Presentation File' Extension Id='abcd' ContentType='application/abcd' Verb Id='open' Sequence='10' Command='Open' Target='[!playbackexe]' Argument='%1' / /Extension /ProgId am I doing something wrong? Any help will be highly appreciated!. thanks Vij - It's here! Your new message! Get new email alerts with the free Yahoo! Toolbar.- 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] install uninstall run conditions
I have an MSI where I need to run some programs after the installation. I have put in some custom actions to run the items and they seem to work fine. however I don't want to run these files when it is uninstalled, because obviously the files won't be there anymore and it will give an error message. so I put a condition InstallMode Remove into the action. to remove button in the uninstall dialogue has a published event which sets the InstallMode to Remove. however I am finding that the actions are still executing causing a fatal error in the uninstaller -- View this message in context: http://www.nabble.com/install-uninstall-run-conditions-tf3490210.html#a9747189 Sent from the wix-users mailing list archive at Nabble.com. - 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] Upgrade problem
How does a major upgrade differ from small one? Tamas Tiboldi wrote: Yes, i know thanks. We are planning to have major upgrades too. -- View this message in context: http://www.nabble.com/Upgrade-problem-tf1755143.html#a9747529 Sent from the wix-users mailing list archive at Nabble.com. - 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] upgrade nightmare
the problem is that requiring commandline parameters or bootstrapper is unacceptable for us, we have seen that our users are too stupid to type a commandline (!?) so I have been told toto make a thing that can do installs and updates on the same package without requiring any commandline parameters or bootstrapper.the only way I have worked out so far is to have a fixed package ID. The problem is that whenever I update installer nothing will be updated, as it will run the MSI from the cached version! -- View this message in context: http://www.nabble.com/upgrade-nightmare-tf2271831.html#a9747562 Sent from the wix-users mailing list archive at Nabble.com. - 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 install a windows service with account.
Hi, You didn't wrote anything aobut used OS. I am not suer whteher it will help you but you may need to secure the public properties that should be used during Execute Sequence. You Should read the pint 1 of following page: (I know that it is about vista but the rule is valid also for XP but it is not enforced enough in XP): http://www.macrovision.com/company/news/newsletter/tips/is_vista.shtml regards Stefan SHI CHEN wrote: Hi, I have an urgent problem about wix version 2. It is needed to allow user to assign the startname/account and password of a windows service instead of using LocalSystem. I want to assign it through two ways: 1. Commandline at time of installation. 2. UI dialog ask for account/password. I used public Property to assign account/password through command line. But the service cannot get started. Does anybody know what I need to do this job with the build in functions of wix? Or I have to write my own custom action? Time is urgent, please help. Thanks a lot. Shi - 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 -- Stefan Pavlik | [EMAIL PROTECTED] Whitestein Technologies s.r.o. | www.whitestein.com Panenska 28 | 811 03 Bratislava | Slovak Republic Main +421 2 5443-5502 | Direct +421 2 5930-0735 - 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] FW: Metabase transactions not committed consistently
Forwarding per Rob's mail. I'd love to see details on the bug mentioned below. Thanks Thomas From: Rob Mensching Sent: Thursday, March 29, 2007 11:08 PM To: Thomas Jeyaseelan Subject: RE: Metabase transactions not committed consistently 1. See http://sharepoint/sites/wix about the wix alias. 2. This sounds like an existing bug (maybe recently fixed bug). From: Thomas Jeyaseelan Sent: Thursday, March 29, 2007 10:33 PM To: Rob Mensching Subject: RE: Metabase transactions not committed consistently Rob, I can't seem to e-mail the WiX alias (I get a not-authorized reply from Exchange), so I'm e-mailing you directly with this matter. Thomas From: Thomas Jeyaseelan Sent: Thursday, March 29, 2007 10:32 PM To: Windows Installer XML Subject: Metabase transactions not committed consistently I've noticed that certain metabase transactions such as ISAPI Filter installs and WebApplication extension registrations are not being registered in the metabase all the time. The syntax for the registration of the extensions is demonstrated in the examples below. Does the code below in a WXS file guarantee that the metabase is updated and committed with the registration transaction, or is there something additional needed? Also, does IIS need to be stopped before the install and re-started? Thomas In the example below, the FPP extension doesn't always get registered. Component Id='ContactCardWebVDirComponent' Guid='171ED91C-1683-4226-A547-70F81C1A9E0D' WebVirtualDir Id='ContactCardWebVDir' WebSite='WebServicesWebSite' Alias='ContactCard' Directory='ContactCardWebServiceFolder' DirProperties='ReadAndExecute' WebApplication Id='ContactCardWebApp' Name='ContactCard Web App' Isolation='medium' WebAppPool='SpacesAppPool' WebApplicationExtension Extension='aspx' CheckPath='no' Executable='[FRAMEWORKDIR]aspnet_isapi.dll' Script='yes' Verbs='GET,HEAD,POST,DEBUG' / WebApplicationExtension Extension='asmx' CheckPath='no' Executable='[FRAMEWORKDIR]aspnet_isapi.dll' Script='yes' Verbs='GET,HEAD,POST,DEBUG' / WebApplicationExtension Extension='fpp' CheckPath='no' Executable='[FRAMEWORKDIR]aspnet_isapi.dll' Script='yes' Verbs='GET,HEAD,POST,DEBUG' / /WebApplication /WebVirtualDir /Component ... Feature Id='WebServicesFeature' Title='Web Services' Level='1' InstallDefault='local' TypicalDefault='install' AllowAdvertise='no' ConfigurableDirectory='INSTALLDIR' ComponentRef Id='WebRootComponent' / ComponentRef Id='ProbeComponent' / ComponentRef Id='SpacesAppPoolComponent' / ComponentRef Id='WebServicesWebSiteComponent' / ComponentRef Id='ContactCardWebVDirComponent' / Thomas Jeyaseelan Developer, Windows Live Spaces 425-705-4554 [EMAIL PROTECTED] http://t.spaces.msn.com/ - 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] upgrade nightmare
You should change the ProductCode as well. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Some user Sent: 30 March 2007 07:40 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] upgrade nightmare the problem is that requiring commandline parameters or bootstrapper is unacceptable for us, we have seen that our users are too stupid to type a commandline (!?) so I have been told toto make a thing that can do installs and updates on the same package without requiring any commandline parameters or bootstrapper.the only way I have worked out so far is to have a fixed package ID. The problem is that whenever I update installer nothing will be updated, as it will run the MSI from the cached version! -- View this message in context: http://www.nabble.com/upgrade-nightmare-tf2271831.html#a9747562 Sent from the wix-users mailing list archive at Nabble.com. -- --- 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=sourceforge CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - 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
