[WiX-users] Data Center Management
Maintec's Data Center Management services empowers companies to securely and remotely http://www.maintec.com/data-center-management.html -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] 32- and 64-bit installers: which GUIDs should be unique?
It sounds like you are almost there, the trick is to use * as your component guids then wix will get it right for you (shared components will use the same guid as determined by the keypath). http://wyrdfish.wordpress.com/2011/01/05/32-and-64-bit-msis-from-a-single-sou rce-file/ I also use a launch condition to stop the 32bit MSI being installed on a 64 bit OS then you don't have to worry about shortcuts. But if you do want to allow them to be installed side by side you would have to create a 32 and a 64 bit shortcut folder to stop them clashing. -Original Message- From: Dave Mateer [mailto:dave_mat...@ntm.org] Sent: 12 March 2012 18:36 To: wix-users@lists.sourceforge.net Subject: [WiX-users] 32- and 64-bit installers: which GUIDs should be unique? I have a working installer and have been using this installer for both 32-bit and 64-bit, simply switching the Program files location, i.e.: ?if $(var.Platform) = x64 ? ?define Win64 = yes ? ?define PlatformProgramFilesFolder = ProgramFiles64Folder ? ?else ? ?define Win64 = no ? ?define PlatformProgramFilesFolder = ProgramFilesFolder ? ?endif ? We just discovered that Weird Things Happen when both the 32-bit and 64-bit are installed, then uninstalled in various orders, etc. The files in Program files are obviously installed in separate locations, but some of the content is installed in the same location, i.e. CommonAppDataFolder. My question is, to save myself the most amount of pain in the future, which Guids should be the same between the 32-bit and 64-bit versions, and which should be different? For those that are different, how can you code this in WiX without maintaining two completely separate installers? We would like to support both major and minor upgrades, and although we don't want people to install both the 32-bit version and 64-bit version and run them side-by-side, it is really outside of our control and ideally that shouldn't break anything, nor should uninstalling one version break the other. Here are my guesses so far, but I really don't have much confidence in my understanding: +-+---+-- ---+ | Value | x86/x64 same? | How | +-+---+-- ---+ | ProductCode No Use * as ProductCode | | UpgradeCode No Define different static Guids in config file| | Files in Program files No ??? Would I have to define every single file twice? | | Files in CommonAppDataFolder Yes Hard-coded Guid | | Shortcuts (shared)Yes Hard-coded Guid | + ---+ Please enlighten me! Thanks! Dave - - Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. 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. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] .NET Custom Action fails intermittently on some machines
I have the same problem for our installer as well. I have now seen a custom action reporting success in out own logging and then the see in the MSI log that the CA fails. A part of the log where it fails: MSI (s) (A8:38) [13:37:49:868]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI3620.tmp, Entrypoint: ProcessRawDwordRegistryValue SFXCA: Extracting custom action to temporary directory: C:\Windows\Installer\MSI3620.tmp-\ SFXCA: Binding to CLR version v2.0.50727 Calling custom action CyberTech.Wix.CA!CyberTech.Wix.CA.CustomActions.ProcessRawDwordRegistryValue MSI (s) (A8!0C) [13:37:49:978]: PROPERTY CHANGE: Modifying PROCESSED_DWORD property. Its current value is '0'. Its new value: '14'. CustomAction ProcessRegistryValueLogtime returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) Action ended 13:37:49: ProcessRegistryValueLogtime. Return value 3. The custom action is used multiple times. It fails the third time. The log of the three custom actions: MSI (s) (A8:7C) [13:37:49:634]: Doing action: ProcessEnableRealtimePlay Action 13:37:49: ProcessEnableRealtimePlay. Action start 13:37:49: ProcessEnableRealtimePlay. MSI (s) (A8:5C) [13:37:49:634]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI3535.tmp, Entrypoint: ProcessRawDwordRegistryValue MSI (s) (A8:28) [13:37:49:650]: Generating random cookie. MSI (s) (A8:28) [13:37:49:650]: Created Custom Action Server with PID 3140 (0xC44). MSI (s) (A8:08) [13:37:49:666]: Running as a service. MSI (s) (A8:08) [13:37:49:666]: Hello, I'm your 32bit Impersonated custom action server. SFXCA: Extracting custom action to temporary directory: C:\Windows\Installer\MSI3535.tmp-\ SFXCA: Binding to CLR version v2.0.50727 Calling custom action CyberTech.Wix.CA!CyberTech.Wix.CA.CustomActions.ProcessRawDwordRegistryValue MSI (s) (A8!70) [13:37:49:853]: PROPERTY CHANGE: Modifying PROCESSED_DWORD property. Its current value is '1'. Its new value: '0'. Action ended 13:37:49: ProcessEnableRealtimePlay. Return value 1. MSI (s) (A8:7C) [13:37:49:853]: Doing action: ProcessEnableRealtimePlay.GetValue Action 13:37:49: ProcessEnableRealtimePlay.GetValue. Action start 13:37:49: ProcessEnableRealtimePlay.GetValue. MSI (s) (A8:7C) [13:37:49:853]: PROPERTY CHANGE: Modifying ENABLEREALTIMEPLAY property. Its current value is '#0'. Its new value: '0'. Action ended 13:37:49: ProcessEnableRealtimePlay.GetValue. Return value 1. MSI (s) (A8:7C) [13:37:49:853]: Doing action: ProcessRegistryValueLogtime.SetValue Action 13:37:49: ProcessRegistryValueLogtime.SetValue. Action start 13:37:49: ProcessRegistryValueLogtime.SetValue. MSI (s) (A8:7C) [13:37:49:868]: PROPERTY CHANGE: Modifying RAW_DWORD property. Its current value is '#0'. Its new value: '#14'. Action ended 13:37:49: ProcessRegistryValueLogtime.SetValue. Return value 1. MSI (s) (A8:7C) [13:37:49:868]: Doing action: ProcessRegistryValueLogtime Action 13:37:49: ProcessRegistryValueLogtime. Action start 13:37:49: ProcessRegistryValueLogtime. MSI (s) (A8:38) [13:37:49:868]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI3620.tmp, Entrypoint: ProcessRawDwordRegistryValue SFXCA: Extracting custom action to temporary directory: C:\Windows\Installer\MSI3620.tmp-\ SFXCA: Binding to CLR version v2.0.50727 Calling custom action CyberTech.Wix.CA!CyberTech.Wix.CA.CustomActions.ProcessRawDwordRegistryValue MSI (s) (A8!0C) [13:37:49:978]: PROPERTY CHANGE: Modifying PROCESSED_DWORD property. Its current value is '0'. Its new value: '14'. CustomAction ProcessRegistryValueLogtime returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) Action ended 13:37:49: ProcessRegistryValueLogtime. Return value 3. Action ended 13:37:49: INSTALL. Return value 3. I ran this installer 2 times, then it failed. I ran it a third time, that was successful. The logging is only different from the line CustomAction ProcessRegistryValueLogtime returned actual error code 1603 I'm using a virtual machine, win2k8. It has 4gb of memory. During install the machine was idle. What can I do to trace and fix this issue? Kind regards, Hans de Groot -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/NET-Custom-Action-fails-intermittently-on-some-machines-tp4659699p7368559.html Sent from the wix-users mailing list archive at Nabble.com. -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Burn: shedule reboot from Managed BA
Hello.
I spend a lot of time in attempt to make my C# BA to restart computer after
installation, but without any success. Native
'WixStandardBootstrapperApplication.RtfLicense' seems to work fine, and I
didn't find in Wix sources any reasons why it doesn't work with my BA. I'm
sure I missed something and here I need your help, please )
Here is what my BA does:
MainWindow.Model.Bootstrapper.Shutdown += OnShutDownHandler; ...
private void OnShutDownHandler(object sender, ShutdownEventArgs e)
{ ... e.Result = Result.Restart; ... }
Here is what 'WixStandardBootstrapperApplication.RtfLicense' does:
virtual STDMETHODIMP_(int) OnShutdown() {
int nResult = IDNOACTION; ...
if (m_fRestartRequired) {
if (m_fAllowRestart) { nResult = IDRESTART; }
} ...
return nResult;
}
Here is code in engine which calls OnShutdown:
int nResult = pEngineState-userExperience.pUserExperience-OnShutdown();
if (IDRESTART == nResult) {
LogId(REPORT_STANDARD, MSG_BA_REQUESTED_RESTART,
LoggingBoolToString(pEngineState-fRestart));
pEngineState-fRestart = TRUE;
}
Couldn't be more simple. But still I don't see 'MSG_BA_REQUESTED_RESTART'
message in logs (which is 'Bootstrapper application requested restart at
shutdown. Planned to restart already: '), and thus reboot is not performed at
all. Result.Restart is of int 102 in Result enum, which is the same value as
IDRESTART. I'm currently using Wix 3.6.2712.
As usual I will be very very grateful for any hints here).
Thx in advance. 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
--
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Multi-language installer
Having already done some research, it appears that single-MSI multi-language installers are not supported by Windows Installer, and thus, not by WiX. However, the latest information I could find that actually looked definitive was from 2007, and I'm wondering if there has been any progress since that time, or if perhaps there is a solution for my very simple case. 99.9% of the payload in my installer is the same between the various languages. In fact, it is being called silently from a bootstrapper so I don't even care about UI transformation. The ONLY thing that needs to be translated is the product name as it appears in Add/Remove Programs and the shortcut (including the folder), i.e.: Product Name=!(loc.ProductName)/ Package Description=!(loc.ProductName)/ Directory Id=ProgramMenuFolder Directory Id=ApplicationProgramsFolder Name=!(loc.ProductName)/ /Directory DirectoryRef Id=ApplicationProgramsFolder Component Shortcut Name=!(loc.ProductName) /Component /DirectoryRef Is there any way to officially do this without duplicating the content? I have four languages to support, and the content is over 400 MB, so it would be a real waste to create four separate installers. The language of the application itself can be switched at runtime (using localization resource files), so we really want to create one DVD with our single installer. The most helpful workarounds I found (from 2007) are: http://jpassing.com/2007/06/14/authoring-multi-language-msi-packages/ http://wix.tramontana.co.hu/tutorial/transforms/morphing-installers Is this still the state of things? Would those transforms even work with non-UI transforms? Any better ideas? Thanks, Dave -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] .NET Custom Action fails intermittently on some machines
You might be encountering this: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Two-Wierd-Inst aller-Problems-DTF-and-QuietExec-td7220939.html From: hansdegroot hans.degr...@nice.com Sent: Tuesday, March 13, 2012 9:07 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] .NET Custom Action fails intermittently on some machines I have the same problem for our installer as well. I have now seen a custom action reporting success in out own logging and then the see in the MSI log that the CA fails. A part of the log where it fails: MSI (s) (A8:38) [13:37:49:868]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI3620.tmp, Entrypoint: ProcessRawDwordRegistryValue SFXCA: Extracting custom action to temporary directory: C:\Windows\Installer\MSI3620.tmp-\ SFXCA: Binding to CLR version v2.0.50727 Calling custom action CyberTech.Wix.CA!CyberTech.Wix.CA.CustomActions.ProcessRawDwordRegistryValue MSI (s) (A8!0C) [13:37:49:978]: PROPERTY CHANGE: Modifying PROCESSED_DWORD property. Its current value is '0'. Its new value: '14'. CustomAction ProcessRegistryValueLogtime returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) Action ended 13:37:49: ProcessRegistryValueLogtime. Return value 3. The custom action is used multiple times. It fails the third time. The log of the three custom actions: MSI (s) (A8:7C) [13:37:49:634]: Doing action: ProcessEnableRealtimePlay Action 13:37:49: ProcessEnableRealtimePlay. Action start 13:37:49: ProcessEnableRealtimePlay. MSI (s) (A8:5C) [13:37:49:634]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI3535.tmp, Entrypoint: ProcessRawDwordRegistryValue MSI (s) (A8:28) [13:37:49:650]: Generating random cookie. MSI (s) (A8:28) [13:37:49:650]: Created Custom Action Server with PID 3140 (0xC44). MSI (s) (A8:08) [13:37:49:666]: Running as a service. MSI (s) (A8:08) [13:37:49:666]: Hello, I'm your 32bit Impersonated custom action server. SFXCA: Extracting custom action to temporary directory: C:\Windows\Installer\MSI3535.tmp-\ SFXCA: Binding to CLR version v2.0.50727 Calling custom action CyberTech.Wix.CA!CyberTech.Wix.CA.CustomActions.ProcessRawDwordRegistryValue MSI (s) (A8!70) [13:37:49:853]: PROPERTY CHANGE: Modifying PROCESSED_DWORD property. Its current value is '1'. Its new value: '0'. Action ended 13:37:49: ProcessEnableRealtimePlay. Return value 1. MSI (s) (A8:7C) [13:37:49:853]: Doing action: ProcessEnableRealtimePlay.GetValue Action 13:37:49: ProcessEnableRealtimePlay.GetValue. Action start 13:37:49: ProcessEnableRealtimePlay.GetValue. MSI (s) (A8:7C) [13:37:49:853]: PROPERTY CHANGE: Modifying ENABLEREALTIMEPLAY property. Its current value is '#0'. Its new value: '0'. Action ended 13:37:49: ProcessEnableRealtimePlay.GetValue. Return value 1. MSI (s) (A8:7C) [13:37:49:853]: Doing action: ProcessRegistryValueLogtime.SetValue Action 13:37:49: ProcessRegistryValueLogtime.SetValue. Action start 13:37:49: ProcessRegistryValueLogtime.SetValue. MSI (s) (A8:7C) [13:37:49:868]: PROPERTY CHANGE: Modifying RAW_DWORD property. Its current value is '#0'. Its new value: '#14'. Action ended 13:37:49: ProcessRegistryValueLogtime.SetValue. Return value 1. MSI (s) (A8:7C) [13:37:49:868]: Doing action: ProcessRegistryValueLogtime Action 13:37:49: ProcessRegistryValueLogtime. Action start 13:37:49: ProcessRegistryValueLogtime. MSI (s) (A8:38) [13:37:49:868]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI3620.tmp, Entrypoint: ProcessRawDwordRegistryValue SFXCA: Extracting custom action to temporary directory: C:\Windows\Installer\MSI3620.tmp-\ SFXCA: Binding to CLR version v2.0.50727 Calling custom action CyberTech.Wix.CA!CyberTech.Wix.CA.CustomActions.ProcessRawDwordRegistryValue MSI (s) (A8!0C) [13:37:49:978]: PROPERTY CHANGE: Modifying PROCESSED_DWORD property. Its current value is '0'. Its new value: '14'. CustomAction ProcessRegistryValueLogtime returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) Action ended 13:37:49: ProcessRegistryValueLogtime. Return value 3. Action ended 13:37:49: INSTALL. Return value 3. I ran this installer 2 times, then it failed. I ran it a third time, that was successful. The logging is only different from the line CustomAction ProcessRegistryValueLogtime returned actual error code 1603 I'm using a virtual machine, win2k8. It has 4gb of memory. During install the machine was idle. What can I do to trace and fix this issue? Kind regards, Hans de Groot -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/NET-Custom-Act ion-fails-intermittently-on-some-machines-tp4659699p7368559.html Sent from the wix-users mailing list archive at Nabble.com.
Re: [WiX-users] Multiple Instances / Instance Transforms
Hi Martin, I too stumbled upon that sln, but was so green with WiX that I was unable to follow the example. Did you get anywhere with you solution? Regards Anthony -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Multiple-Instances-Instance-Transforms-tp5419660p7368675.html Sent from the wix-users mailing list archive at Nabble.com. -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Multi-language installer
The Windows Installer behavior has not changed. :( On Tue, Mar 13, 2012 at 7:26 AM, Dave Mateer dave_mat...@ntm.org wrote: Having already done some research, it appears that single-MSI multi-language installers are not supported by Windows Installer, and thus, not by WiX. However, the latest information I could find that actually looked definitive was from 2007, and I'm wondering if there has been any progress since that time, or if perhaps there is a solution for my very simple case. 99.9% of the payload in my installer is the same between the various languages. In fact, it is being called silently from a bootstrapper so I don't even care about UI transformation. The ONLY thing that needs to be translated is the product name as it appears in Add/Remove Programs and the shortcut (including the folder), i.e.: Product Name=!(loc.ProductName)/ Package Description=!(loc.ProductName)/ Directory Id=ProgramMenuFolder Directory Id=ApplicationProgramsFolder Name=!(loc.ProductName)/ /Directory DirectoryRef Id=ApplicationProgramsFolder Component Shortcut Name=!(loc.ProductName) /Component /DirectoryRef Is there any way to officially do this without duplicating the content? I have four languages to support, and the content is over 400 MB, so it would be a real waste to create four separate installers. The language of the application itself can be switched at runtime (using localization resource files), so we really want to create one DVD with our single installer. The most helpful workarounds I found (from 2007) are: http://jpassing.com/2007/06/14/authoring-multi-language-msi-packages/ http://wix.tramontana.co.hu/tutorial/transforms/morphing-installers Is this still the state of things? Would those transforms even work with non-UI transforms? Any better ideas? Thanks, Dave -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Multi-language installer
They may not be supported but I've done it in InstallShield with and without a Setup.EXE. http://www.installsite.org/pages/en/msi/articles/embeddedlang/ The setup.exe with lanuage selection and command line passing to specify the embedded language transform to use is the officially supported technique. The only thing that really sucks IMO is that you better not modify the UI from one build to another if you are doing Minor Upgrades as you can get into some nasty cached transform problem areas. Major Upgrades work fine though. From: Rob Mensching r...@robmensching.com Sent: Tuesday, March 13, 2012 10:20 AM To: General discussion for Windows Installer XML toolset. wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Multi-language installer The Windows Installer behavior has not changed. :( On Tue, Mar 13, 2012 at 7:26 AM, Dave Mateer dave_mat...@ntm.org wrote: Having already done some research, it appears that single-MSI multi-language installers are not supported by Windows Installer, and thus, not by WiX. However, the latest information I could find that actually looked definitive was from 2007, and I'm wondering if there has been any progress since that time, or if perhaps there is a solution for my very simple case. 99.9% of the payload in my installer is the same between the various languages. In fact, it is being called silently from a bootstrapper so I don't even care about UI transformation. The ONLY thing that needs to be translated is the product name as it appears in Add/Remove Programs and the shortcut (including the folder), i.e.: Product Name=!(loc.ProductName)/ Package Description=!(loc.ProductName)/ Directory Id=ProgramMenuFolder Directory Id=ApplicationProgramsFolder Name=!(loc.ProductName)/ /Directory DirectoryRef Id=ApplicationProgramsFolder Component Shortcut Name=!(loc.ProductName) /Component /DirectoryRef Is there any way to officially do this without duplicating the content? I have four languages to support, and the content is over 400 MB, so it would be a real waste to create four separate installers. The language of the application itself can be switched at runtime (using localization resource files), so we really want to create one DVD with our single installer. The most helpful workarounds I found (from 2007) are: http://jpassing.com/2007/06/14/authoring-multi-language-msi-packages/ http://wix.tramontana.co.hu/tutorial/transforms/morphing-installers Is this still the state of things? Would those transforms even work with non-UI transforms? Any better ideas? Thanks, Dave -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Multi-language installer
If you really only want package name and shortcut localization, it may be possible to do with a few conditions in an English MSI and some property settings. See ARPCOMMENTS ProductName etc. How will you determine what language to use, will it be passed in from your bootstrapper or based on OS settings? -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: 13 March 2012 15:13 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Multi-language installer The Windows Installer behavior has not changed. :( On Tue, Mar 13, 2012 at 7:26 AM, Dave Mateer dave_mat...@ntm.org wrote: Having already done some research, it appears that single-MSI multi-language installers are not supported by Windows Installer, and thus, not by WiX. However, the latest information I could find that actually looked definitive was from 2007, and I'm wondering if there has been any progress since that time, or if perhaps there is a solution for my very simple case. 99.9% of the payload in my installer is the same between the various languages. In fact, it is being called silently from a bootstrapper so I don't even care about UI transformation. The ONLY thing that needs to be translated is the product name as it appears in Add/Remove Programs and the shortcut (including the folder), i.e.: Product Name=!(loc.ProductName)/ Package Description=!(loc.ProductName)/ Directory Id=ProgramMenuFolder Directory Id=ApplicationProgramsFolder Name=!(loc.ProductName)/ /Directory DirectoryRef Id=ApplicationProgramsFolder Component Shortcut Name=!(loc.ProductName) /Component /DirectoryRef Is there any way to officially do this without duplicating the content? I have four languages to support, and the content is over 400 MB, so it would be a real waste to create four separate installers. The language of the application itself can be switched at runtime (using localization resource files), so we really want to create one DVD with our single installer. The most helpful workarounds I found (from 2007) are: http://jpassing.com/2007/06/14/authoring-multi-language-msi-packages/ http://wix.tramontana.co.hu/tutorial/transforms/morphing-installers Is this still the state of things? Would those transforms even work with non-UI transforms? Any better ideas? Thanks, Dave -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- virtually, Rob Mensching - http://RobMensching.com LLC - - Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. 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. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Multi-language installer
Transforms are transforms - they apply to the MSI file, not just the UI. I've changed Shortcut names, custom action conditions and (I'm pretty sure) ProductName using transforms. Phil W -Original Message- From: Dave Mateer [mailto:dave_mat...@ntm.org] Sent: Tuesday, March 13, 2012 7:26 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Multi-language installer Having already done some research, it appears that single-MSI multi-language installers are not supported by Windows Installer, and thus, not by WiX. However, the latest information I could find that actually looked definitive was from 2007, and I'm wondering if there has been any progress since that time, or if perhaps there is a solution for my very simple case. 99.9% of the payload in my installer is the same between the various languages. In fact, it is being called silently from a bootstrapper so I don't even care about UI transformation. The ONLY thing that needs to be translated is the product name as it appears in Add/Remove Programs and the shortcut (including the folder), i.e.: Product Name=!(loc.ProductName)/ Package Description=!(loc.ProductName)/ Directory Id=ProgramMenuFolder Directory Id=ApplicationProgramsFolder Name=!(loc.ProductName)/ /Directory DirectoryRef Id=ApplicationProgramsFolder Component Shortcut Name=!(loc.ProductName) /Component /DirectoryRef Is there any way to officially do this without duplicating the content? I have four languages to support, and the content is over 400 MB, so it would be a real waste to create four separate installers. The language of the application itself can be switched at runtime (using localization resource files), so we really want to create one DVD with our single installer. The most helpful workarounds I found (from 2007) are: http://jpassing.com/2007/06/14/authoring-multi-language-msi-packages/ http://wix.tramontana.co.hu/tutorial/transforms/morphing-installers Is this still the state of things? Would those transforms even work with non-UI transforms? Any better ideas? Thanks, Dave -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/en/legal/default.aspx. You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail recept...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Multi-language installer
On 13-Mar-12 10:26, Dave Mateer wrote: 99.9% of the payload in my installer is the same between the various languages. The canonical way is to have one language-neutral installer and n language-specific installers. Is there any way to officially do this without duplicating the content? I have four languages to support, and the content is over 400 MB, so it would be a real waste to create four separate installers. Another approach is to isolate language-neutral content into a shared external .cab file, so you have n installers but no duplicated content. -- sig://boB http://joyofsetup.com/ -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
