[WiX-users] WIX
Hi I have problems with custom action and dll. My .wxs file has 2 custom actions which are calling a dll and its function and passing a PROPERTY's value as a parameter to the dll. Vc++ dll(win 32) .The dll is calling a function msigetproperty(,,Buffer,). This buffer should extract the value of the property and display. but it is not extracting the property. My custom action are CustomAction Id=MyAction Return=check Execute=deferred BinaryKey=dll DllEntry=Print HideTarget=yes / Binary Id=dll src=dll.dll / Property Id=SOME_PUBLICHello, from deferred CA/Property CustomAction Id=MyAction.SetProperty Return=check Property=MyAction Value=[SOME_PUBLIC] / InstallExecuteSequence Custom Action=MyAction.SetProperty Before=InstallFiles/ Custom Action=MyAction After=MyAction.SetProperty / /InstallExecuteSequence Am i missing something in this. DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persistent Systems Pvt. Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Pvt. Ltd. does not accept any liability for virus infected mails. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WIX
Your custom action is deferred, so you will have limited access to the database (the CustomActionData property only pretty much). Check the WiX sources for examples on how to work with it. K-ballo.- [EMAIL PROTECTED] escribió: Hi I have problems with custom action and dll. My .wxs file has 2 custom actions which are calling a dll and its function and passing a PROPERTY's value as a parameter to the dll. Vc++ dll(win 32) .The dll is calling a function msigetproperty(,,Buffer,). This buffer should extract the value of the property and display. but it is not extracting the property. My custom action are CustomAction Id=MyAction Return=check Execute=deferred BinaryKey=dll DllEntry=Print HideTarget=yes / Binary Id=dll src=dll.dll / Property Id=SOME_PUBLICHello, from deferred CA/Property CustomAction Id=MyAction.SetProperty Return=check Property=MyAction Value=[SOME_PUBLIC] / InstallExecuteSequence Custom Action=MyAction.SetProperty Before=InstallFiles/ Custom Action=MyAction After=MyAction.SetProperty / /InstallExecuteSequence Am i missing something in this. DISCLAIMER == This e-mail may contain privileged and confidential information which is the property of Persistent Systems Pvt. Ltd. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Persistent Systems Pvt. Ltd. does not accept any liability for virus infected mails. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Shortcuts and components
Ward, Mike (MED US) wrote: I think it pretty natural for someone to think the shortcuts would be associated with the files here, not the component. Generally, that's true, but not with advertised shortcuts. I think some of this is just result of laziness. I didn't see a reason to put the files in separate components because they always get installed together. Components are *the* atomic unit in MSI so generally they should be as small as possible. That helps not only in this case but when it comes to patching and upgrades. capitalized. Again, my understanding is limited but I think the compiler might be able to help here. It appears a public property is one that can be set at runtime. It's not apparent to me that a property used in a RadioButtonGroup can ever be useful unless it's public. Perhaps there is a use case I'm not thinking of here? It's perfectly legal to use a UI construct only in the UI sequence. Where something is outright illegal or almost certainly won't do what the user intended, the compiler often emits a warning or error. For example, a Feature element's ConfigurableDirectory attribute is only useful with public properties, so if you try to use a private property, the compiler gives an error. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] determine selected item in listbox
Stanislav Martinek wrote: Can anybody tell me how to determine which item is selected in listbox i fany? Check the property tied to the list box. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Extensions and Schemas
K-ballo wrote: I'm working on a very simple extension, and I have a question about the schema. My main element will have Product as parent, and I would like to limit the number of sibblings to just one, so only one instance of my element can be used in a project. How can I accomplish this kind of restrictions (min/maxOccurs) at the schema from an extension, where I can't modify the parent element? You probably can't do it via schema validation but need to code the check in the compiler extension. In general, WiX does explicit authoring checks because it can do so more flexibly than schema validation allows -- certainly it gives better errors then 'invalid content.'g -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Question about writing custom actions...
Mike Dimmick wrote: The WiX custom actions perform their install/uninstall actions on a per-component basis by calling MsiGetComponentState. If the resource is currently installed locally or to run from source, and the action is to make it absent or removed, the uninstall tasks are performed. It's probably a good idea to stick to this model. It also makes it easier to support patching, upgrade, and repair scenarios over all-or-nothing install/uninstall choices. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Best Way to Include MSVCRT 80 Dependencies
What's the best way to include the Microsoft Visual Studio 2005 CRT dependencies? I want to include the debug versions for my debug build. I've tried using the standard MSM files but I get a bunch of warnings. I have the following WXS code: ** !-- MSVCRT 80 libraries -- ?if $(env.BUILDTYPE) = debug? Merge Id=CRT Language=0 SourceFile=..\crt\Microsoft.VC80.DebugCRT\Microsoft_VC80_DebugCRT_x86.msm DiskId=1 / Merge Id=CRT Policy Language=0 SourceFile=..\crt\Microsoft.VC80.DebugCRT\policy_8_0_Microsoft_VC80_DebugCRT_x86.msm DiskId=1 / ?else? Merge Id=CRT Language=0 SourceFile=..\crt\Microsoft.VC80.CRT\microsoft_vc80_crt_x86.msm DiskId=1 / Merge Id=CRT Policy Language=0 SourceFile=..\crt\Microsoft.VC80.CRT\policy_8_0_Microsoft_VC80_CRT_x86.msm DiskId=1 / ?endif? InstallExecuteSequence FindRelatedProducts Before=LaunchConditions / RemoveExistingProducts After=InstallValidate / /InstallExecuteSequence InstallUISequence FindRelatedProducts Before=LaunchConditions / /InstallUISequence UI UIRef Id=WixUI_Minimal / UIRef Id=WixUI_ErrorProgressText / Publish Dialog=ExitDialog Control=Finish Event=DoAction Value=LaunchBrowser Order=1![CDATA[UILevel 2 AND NOT Installed]]/Publish /UI Feature Id=MyFeature Title=My Feature Level=1 MergeRef Id=CRT / MergeRef Id=CRT Policy / !-My Components -- /Feature /Feature * When I compile this I get a bunch of Warnings (see below). Any suggestions on how to fix? Thx. Steve Bush *** 1Compiling - Candle (v3.0.2512.0) .\MyfeatureSetup.wxs MyfeatureSetup.wixobj 1Building - Light (v3.0.2512.0) - objd\i386\MyfeatureSetup.msi ... 1warnings in directory d:\clues\private\setup\myfeaturesetup 1d:\clues\private\setup\myfeaturesetup\myfeaturesetup.wxs(49) : warning LGHT1055 : The InstallExecuteSequence ta le contains an action 'SxsInstallCA' which cannot be merged from the merge module '..\crt\Microsoft.VC80.Debu CRT\policy_8_0_Microsoft_VC80_DebugCRT_x86.msm'. This action is likely colliding with an action in the datab se that is being created. The colliding action may have been authored in the database or merged in from anot er merge module. If this is a standard action, it is likely colliding due to a difference in the condition f r 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. 1d:\clues\private\setup\myfeaturesetup\myfeaturesetup.wxs(49) : warning LGHT1055 : The InstallExecuteSequence ta le contains an action 'SxsUninstallCA' which cannot be merged from the merge module '..\crt\Microsoft.VC80.De ugCRT\policy_8_0_Microsoft_VC80_DebugCRT_x86.msm'. This action is likely colliding with an action in the dat base that is being created. The colliding action may have been authored in the database or merged in from an ther 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 t e database or one merge module. 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.762.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.100.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.101.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.103.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.104.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.193.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th
Re: [WiX-users] Best Way to Include MSVCRT 80 Dependencies
IMHO: statically link against libcmt so you don't have the dependency. smile/ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Bush Sent: Friday, June 29, 2007 9:04 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Best Way to Include MSVCRT 80 Dependencies What's the best way to include the Microsoft Visual Studio 2005 CRT dependencies? I want to include the debug versions for my debug build. I've tried using the standard MSM files but I get a bunch of warnings. I have the following WXS code: ** !-- MSVCRT 80 libraries -- ?if $(env.BUILDTYPE) = debug? Merge Id=CRT Language=0 SourceFile=..\crt\Microsoft.VC80.DebugCRT\Microsoft_VC80_DebugCRT_x86.msm DiskId=1 / Merge Id=CRT Policy Language=0 SourceFile=..\crt\Microsoft.VC80.DebugCRT\policy_8_0_Microsoft_VC80_DebugCRT_x86.msm DiskId=1 / ?else? Merge Id=CRT Language=0 SourceFile=..\crt\Microsoft.VC80.CRT\microsoft_vc80_crt_x86.msm DiskId=1 / Merge Id=CRT Policy Language=0 SourceFile=..\crt\Microsoft.VC80.CRT\policy_8_0_Microsoft_VC80_CRT_x86.msm DiskId=1 / ?endif? InstallExecuteSequence FindRelatedProducts Before=LaunchConditions / RemoveExistingProducts After=InstallValidate / /InstallExecuteSequence InstallUISequence FindRelatedProducts Before=LaunchConditions / /InstallUISequence UI UIRef Id=WixUI_Minimal / UIRef Id=WixUI_ErrorProgressText / Publish Dialog=ExitDialog Control=Finish Event=DoAction Value=LaunchBrowser Order=1![CDATA[UILevel 2 AND NOT Installed]]/Publish /UI Feature Id=MyFeature Title=My Feature Level=1 MergeRef Id=CRT / MergeRef Id=CRT Policy / !-My Components -- /Feature /Feature * When I compile this I get a bunch of Warnings (see below). Any suggestions on how to fix? Thx. Steve Bush *** 1Compiling - Candle (v3.0.2512.0) .\MyfeatureSetup.wxs MyfeatureSetup.wixobj 1Building - Light (v3.0.2512.0) - objd\i386\MyfeatureSetup.msi ... 1warnings in directory d:\clues\private\setup\myfeaturesetup 1d:\clues\private\setup\myfeaturesetup\myfeaturesetup.wxs(49) : warning LGHT1055 : The InstallExecuteSequence ta le contains an action 'SxsInstallCA' which cannot be merged from the merge module '..\crt\Microsoft.VC80.Debu CRT\policy_8_0_Microsoft_VC80_DebugCRT_x86.msm'. This action is likely colliding with an action in the datab se that is being created. The colliding action may have been authored in the database or merged in from anot er merge module. If this is a standard action, it is likely colliding due to a difference in the condition f r 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. 1d:\clues\private\setup\myfeaturesetup\myfeaturesetup.wxs(49) : warning LGHT1055 : The InstallExecuteSequence ta le contains an action 'SxsUninstallCA' which cannot be merged from the merge module '..\crt\Microsoft.VC80.De ugCRT\policy_8_0_Microsoft_VC80_DebugCRT_x86.msm'. This action is likely colliding with an action in the dat base that is being created. The colliding action may have been authored in the database or merged in from an ther 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 t e database or one merge module. 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.762.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.100.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.101.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.103.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.104.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 :
Re: [WiX-users] Extensions and Schemas
Bob is correct. I haven't found a way to get XSD to do the validation as you want. It's unfortunate because it'd be nice for intelli-sense but in the end you want to have the check in your extension anyway because you can provide a much better error message than what XSD would give by default. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson Sent: Friday, June 29, 2007 7:55 AM To: K-ballo Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Extensions and Schemas K-ballo wrote: I'm working on a very simple extension, and I have a question about the schema. My main element will have Product as parent, and I would like to limit the number of sibblings to just one, so only one instance of my element can be used in a project. How can I accomplish this kind of restrictions (min/maxOccurs) at the schema from an extension, where I can't modify the parent element? You probably can't do it via schema validation but need to code the check in the compiler extension. In general, WiX does explicit authoring checks because it can do so more flexibly than schema validation allows -- certainly it gives better errors then 'invalid content.'g -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Best Way to Include MSVCRT 80 Dependencies
Unfortunately, I'm not in a position to recompile all of the code to remove the CRT dependency. Sometimes you have to play the hand you're dealt. I've done the web searching route and find a lot of conflicting info. Any pointers would be appreciated. From: Rob Mensching Sent: Friday, June 29, 2007 9:27 AM To: Steve Bush; wix-users@lists.sourceforge.net Subject: RE: Best Way to Include MSVCRT 80 Dependencies IMHO: statically link against libcmt so you don't have the dependency. smile/ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Bush Sent: Friday, June 29, 2007 9:04 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Best Way to Include MSVCRT 80 Dependencies What's the best way to include the Microsoft Visual Studio 2005 CRT dependencies? I want to include the debug versions for my debug build. I've tried using the standard MSM files but I get a bunch of warnings. I have the following WXS code: ** !-- MSVCRT 80 libraries -- ?if $(env.BUILDTYPE) = debug? Merge Id=CRT Language=0 SourceFile=..\crt\Microsoft.VC80.DebugCRT\Microsoft_VC80_DebugCRT_x86.msm DiskId=1 / Merge Id=CRT Policy Language=0 SourceFile=..\crt\Microsoft.VC80.DebugCRT\policy_8_0_Microsoft_VC80_DebugCRT_x86.msm DiskId=1 / ?else? Merge Id=CRT Language=0 SourceFile=..\crt\Microsoft.VC80.CRT\microsoft_vc80_crt_x86.msm DiskId=1 / Merge Id=CRT Policy Language=0 SourceFile=..\crt\Microsoft.VC80.CRT\policy_8_0_Microsoft_VC80_CRT_x86.msm DiskId=1 / ?endif? InstallExecuteSequence FindRelatedProducts Before=LaunchConditions / RemoveExistingProducts After=InstallValidate / /InstallExecuteSequence InstallUISequence FindRelatedProducts Before=LaunchConditions / /InstallUISequence UI UIRef Id=WixUI_Minimal / UIRef Id=WixUI_ErrorProgressText / Publish Dialog=ExitDialog Control=Finish Event=DoAction Value=LaunchBrowser Order=1![CDATA[UILevel 2 AND NOT Installed]]/Publish /UI Feature Id=MyFeature Title=My Feature Level=1 MergeRef Id=CRT / MergeRef Id=CRT Policy / !-My Components -- /Feature /Feature * When I compile this I get a bunch of Warnings (see below). Any suggestions on how to fix? Thx. Steve Bush *** 1Compiling - Candle (v3.0.2512.0) .\MyfeatureSetup.wxs MyfeatureSetup.wixobj 1Building - Light (v3.0.2512.0) - objd\i386\MyfeatureSetup.msi ... 1warnings in directory d:\clues\private\setup\myfeaturesetup 1d:\clues\private\setup\myfeaturesetup\myfeaturesetup.wxs(49) : warning LGHT1055 : The InstallExecuteSequence ta le contains an action 'SxsInstallCA' which cannot be merged from the merge module '..\crt\Microsoft.VC80.Debu CRT\policy_8_0_Microsoft_VC80_DebugCRT_x86.msm'. This action is likely colliding with an action in the datab se that is being created. The colliding action may have been authored in the database or merged in from anot er merge module. If this is a standard action, it is likely colliding due to a difference in the condition f r 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. 1d:\clues\private\setup\myfeaturesetup\myfeaturesetup.wxs(49) : warning LGHT1055 : The InstallExecuteSequence ta le contains an action 'SxsUninstallCA' which cannot be merged from the merge module '..\crt\Microsoft.VC80.De ugCRT\policy_8_0_Microsoft_VC80_DebugCRT_x86.msm'. This action is likely colliding with an action in the dat base that is being created. The colliding action may have been authored in the database or merged in from an ther 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 t e database or one merge module. 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.762.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.100.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.101.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component,
Re: [WiX-users] votive project reference to wixlib
As usually happens to me... as soon as i posted this yesterday i found the problem. because i switched to referencing the wixlib file directly the project dependency order was lost and the votive project was building before the application. sorry about the dumb post. From: Steve Baker [EMAIL PROTECTED] Sent: Thursday, June 28, 2007 12:47 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] votive project reference to wixlib i tried running my solution from msbuild instead of from the ide and get the following error: light.exe : error LGHT0103: The system cannot find the file '..\uilib\bin\Debug\uilib.wixlib' with type 'Source'. the solution builds fine through the ide. i have DefineSolutionProperties false / DefineSolutionProperties there are two votive projects in the solution, one msi project that references the wixlib generated from a ui wixlib project. are there any other differences besides the solution properites when running from an msbuild command line that may cause this error? The file is where it is looking for it, i have tried absolute paths as well. thanks From: Justin Rockwood [EMAIL PROTECTED] Sent: Thursday, June 28, 2007 9:50 AM To: 'steve baker' [EMAIL PROTECTED], wix-users@lists.sourceforge.net Subject: RE: [WiX-users] votive project reference to wixlib There are actually two bugs here (or NYI features, however you'd like to view it J). The first bug is that Votive (.wixproj) projects actually don't work with project references right now (meaning that you can't have a project reference to another wixproj and have it generate the preprocessor variables). The second bug is that adding a project reference to a wixlib will not automatically use that generated wixlib in the link step. Adding an actuall reference to the wixlib will work, as you pointed out. If you'd like to add bugs for both of these, it would be great. I knew about them, but haven't logged bugs against them yet, and therefore they've fallen off my radar. Thanks, Justin From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of steve baker Sent: Thursday, June 28, 2007 9:19 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] votive project reference to wixlib I have a wixlib project in my solution that houses my custom UI. When I add a project reference to that wixlib project from my msi project it doesn't resolve. I found that I can add a reference directly to the wixlib file and it works. I was just wondering if that is the expected way to add references or if a project reference is supposed to work? Thanks, steve - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Best Way to Include MSVCRT 80 Dependencies
We just install the redistributables alongside our main exes. Not sure you're allowed to do that for the debug versions, though. Rob Steve Bush wrote: Unfortunately, I’m not in a position to recompile all of the code to remove the CRT dependency. Sometimes you have to play the hand you’re dealt. I’ve done the web searching route and find a lot of conflicting info. Any pointers would be appreciated. *From:* Rob Mensching *Sent:* Friday, June 29, 2007 9:27 AM *To:* Steve Bush; wix-users@lists.sourceforge.net *Subject:* RE: Best Way to Include MSVCRT 80 Dependencies IMHO: statically link against libcmt so you don’t have the dependency. smile/ *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *On Behalf Of *Steve Bush *Sent:* Friday, June 29, 2007 9:04 AM *To:* wix-users@lists.sourceforge.net *Subject:* [WiX-users] Best Way to Include MSVCRT 80 Dependencies What’s the best way to include the Microsoft Visual Studio 2005 CRT dependencies? I want to include the debug versions for my debug build. I’ve tried using the standard MSM files but I get a bunch of warnings. I have the following WXS code: ** !-- MSVCRT 80 libraries -- ?if $(env.BUILDTYPE) = debug? Merge Id=CRT Language=0 SourceFile=..\crt\Microsoft.VC80.DebugCRT\Microsoft_VC80_DebugCRT_x86.msm DiskId=1 / Merge Id=CRT Policy Language=0 SourceFile=..\crt\Microsoft.VC80.DebugCRT\policy_8_0_Microsoft_VC80_DebugCRT_x86.msm DiskId=1 / ?else? Merge Id=CRT Language=0 SourceFile=..\crt\Microsoft.VC80.CRT\microsoft_vc80_crt_x86.msm DiskId=1 / Merge Id=CRT Policy Language=0 SourceFile=..\crt\Microsoft.VC80.CRT\policy_8_0_Microsoft_VC80_CRT_x86.msm DiskId=1 / ?endif? InstallExecuteSequence FindRelatedProducts Before=LaunchConditions / RemoveExistingProducts After=InstallValidate / /InstallExecuteSequence InstallUISequence FindRelatedProducts Before=LaunchConditions / /InstallUISequence UI UIRef Id=WixUI_Minimal / UIRef Id=WixUI_ErrorProgressText / Publish Dialog=ExitDialog Control=Finish Event=DoAction Value=LaunchBrowser Order=1![CDATA[UILevel 2 AND NOT Installed]]/Publish /UI Feature Id=MyFeature Title=My Feature Level=1 MergeRef Id=CRT / MergeRef Id=CRT Policy / !—My Components -- /Feature /Feature * When I compile this I get a bunch of Warnings (see below). Any suggestions on how to fix? Thx. Steve Bush *** 1Compiling - Candle (v3.0.2512.0) .\MyfeatureSetup.wxs MyfeatureSetup.wixobj 1Building - Light (v3.0.2512.0) - objd\i386\MyfeatureSetup.msi ... 1warnings in directory d:\clues\private\setup\myfeaturesetup 1d:\clues\private\setup\myfeaturesetup\myfeaturesetup.wxs(49) : warning LGHT1055 : The InstallExecuteSequence ta le contains an action 'SxsInstallCA' which cannot be merged from the merge module '..\crt\Microsoft.VC80.Debu CRT\policy_8_0_Microsoft_VC80_DebugCRT_x86.msm'. This action is likely colliding with an action in the datab se that is being created. The colliding action may have been authored in the database or merged in from anot er merge module. If this is a standard action, it is likely colliding due to a difference in the condition f r 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. 1d:\clues\private\setup\myfeaturesetup\myfeaturesetup.wxs(49) : warning LGHT1055 : The InstallExecuteSequence ta le contains an action 'SxsUninstallCA' which cannot be merged from the merge module '..\crt\Microsoft.VC80.De ugCRT\policy_8_0_Microsoft_VC80_DebugCRT_x86.msm'. This action is likely colliding with an action in the dat base that is being created. The colliding action may have been authored in the database or merged in from an ther 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 t e database or one merge module. 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath, Key(s): downlevel_manifest.8.0.50727.762.550B5BF0 FF32_EF74_FF1F_C8B3B9A1E18E 1d:\clues\private\setup\myfeaturesetup\light.exe : warning LGHT1076 : ICE03: String overflow (greater than len th permitted in column); Table: Component, Column: KeyPath,
Re: [WiX-users] votive project reference to wixlib
I'll take some time to enter something into tracker this weekend, i want to make sure i understand it well enough. for now what would be the best way to break out some of the common functionality that needs to share preprocessor variables. i am creating about a dozen msi's and have quite a bit of duplication i would like to remove. i am thinking about switching to include files for the time being but would like to find a better way than that. I thought I had read somewhere that votive projects now supported adding linked items but it doens't seem to? TIA fo any thoughts, steve From: Justin Rockwood [EMAIL PROTECTED] Sent: Thursday, June 28, 2007 9:50 AM To: 'steve baker' [EMAIL PROTECTED], wix-users@lists.sourceforge.net Subject: RE: [WiX-users] votive project reference to wixlib There are actually two bugs here (or NYI features, however you'd like to view it J). The first bug is that Votive (.wixproj) projects actually don't work with project references right now (meaning that you can't have a project reference to another wixproj and have it generate the preprocessor variables). The second bug is that adding a project reference to a wixlib will not automatically use that generated wixlib in the link step. Adding an actuall reference to the wixlib will work, as you pointed out. If you'd like to add bugs for both of these, it would be great. I knew about them, but haven't logged bugs against them yet, and therefore they've fallen off my radar. Thanks, Justin From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of steve baker Sent: Thursday, June 28, 2007 9:19 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] votive project reference to wixlib I have a wixlib project in my solution that houses my custom UI. When I add a project reference to that wixlib project from my msi project it doesn't resolve. I found that I can add a reference directly to the wixlib file and it works. I was just wondering if that is the expected way to add references or if a project reference is supposed to work? Thanks, steve - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Best Way to Include MSVCRT 80 Dependencies
We just install the redistributables alongside our main exes. Not sure you're allowed to do that for the debug versions, though. The EULA prohibits redistributing the debug versions according to this: http://blogs.msdn.com/nikolad/archive/2005/09/02/running-c-application-b uilt-by-vc-express-on-another-computer.aspx Cheers, John - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Best Way to Include MSVCRT 80 Dependencies
Steve, What's the best way to include the Microsoft Visual Studio 2005 CRT dependencies? I want to include the debug versions for my debug build. I've tried using the standard MSM files but I get a bunch of warnings. I have the following WXS code: This blog entry: http://blogs.msdn.com/astebner/archive/2007/02/13/building-an-msi-using- wix-v3-0-that-includes-the-vc-8-0-runtime-merge-modules.aspx documents these various warnings but doesn't go beyond noting that you could disable them, but you would be disabling them for your whole project. I noticed another post on this list recently, where someone had a special verification mode in their project for running ice against, which excluded all merge modules. Cheers, John - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Installing MSI with external Cabs through Group Policy
I'm new to WiX and I wanted to know if there are anything special I should know if I want to deploy my installer, which depends on multiple external CAB files, though group policy. I've been researching, if I run msiexec /a command, it only copies the MSI package and not the CABs. Currently, I'm following instructions at http://support.microsoft.com/kb/816102 Thank you, Vince -- View this message in context: http://www.nabble.com/Installing-MSI-with-external-Cabs-through-Group-Policy-tf4001340.html#a11365078 Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] wix variable help...
I would like to use the packagecode generation built into the compiler. However because of some of my customizations I have to hard code the packagecode because this is needed to identify some components of the msm. Is there a way to access the generated one via $(var.packagecode), which actually doesnt work, or some other method. One thing I have found is that compiler will not replace the generation entry in any place except for the package/id entry. it would be nice if it could be used as ?define packagecode=?-... ? and then $(var.packagecode) could be used. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Wix Gac Assembly Install
Hey, I have a few assemblies as part of my project that are shared by multiple products. Currently, when we want to upgrade one product (of the many), we need to uninstall all existing MSI's so all shared gac assemblies are removed and then reinstall all needed MSI's. I'm curious if there's a way to specify that a dll with a newer build number (major and minor are the same, only the QFE is different) OR specify that I want the MSI to always overwrite the assembly in the gac if it finds one already there. Is this possible? Thanks Tony - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Conditional Feature installation
I'm making a WIX install with 2 features: FEATURE_A (installs by default) FEATURE_B (does not install by default) My upgrade scenario is a new product and package ID for every version. My desired behavior is that in any upgrade scenario, the default feature set stays consistent with what is already installed, and not to snap back to the new user defaults. In other words: 1) User installs and via UI, only installs FEATURE_B (goes against both defaults) 2) User gets next version, runs MSI to upgrade. I want the installer to detect what is installed, and have the default selected feature set to be only FEATURE_B. I was thinking of doing this by putting a condition in the feature tag to change the level when a feature is installed. But documentation says that won't work because the enumeration of which features are installed happens too late in the process. Any suggestions? I'm on WIX v2, BTW. Jason - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] wix variable help...
If you need to refer to properties within a merge module from an installer which consumes that merge module, you should tell WiX not to modularize that property. You do this with the SuppressModularization attribute. There are a number of other elements which have a SuppressModularization attribute. -- Mike Dimmick -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeremy Breiding Sent: 29 June 2007 20:11 To: wix-users@lists.sourceforge.net Subject: [WiX-users] wix variable help... I would like to use the packagecode generation built into the compiler. However because of some of my customizations I have to hard code the packagecode because this is needed to identify some components of the msm. Is there a way to access the generated one via $(var.packagecode), which actually doesnt work, or some other method. One thing I have found is that compiler will not replace the generation entry in any place except for the package/id entry. it would be nice if it could be used as ?define packagecode=?-... ? and then $(var.packagecode) could be used. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix Gac Assembly Install
If you want to replace a GAC assembly with an assembly of the same assembly version but a different file version, specify the -fv switch to light. However, in general you should plan for your GAC assemblies to be installed side-by-side, and upgrade the assembly version number. Only consider publisher policy or in-place upgrade if you're addressing a security issue and/or all clients must use the latest version (perhaps you have some shared data store that is not compatible between versions?) In my view people coming from the COM world tend to overuse the GAC. It's generally better not to strong-name your components and keep them in the application's folder. Disk space is cheap. Administrator time to fix your compatibility screw-up is not. -- Mike Dimmick _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tony Wallulis Sent: 29 June 2007 23:08 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Wix Gac Assembly Install Hey, I have a few assemblies as part of my project that are shared by multiple products. Currently, when we want to upgrade one product (of the many), we need to uninstall all existing MSI's so all shared gac assemblies are removed and then reinstall all needed MSI's. I'm curious if there's a way to specify that a dll with a newer build number (major and minor are the same, only the QFE is different) OR specify that I want the MSI to always overwrite the assembly in the gac if it finds one already there. Is this possible? Thanks Tony - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditional Feature installation
The MigrateFeatureStates action is supposed to do that for you. Set UpgradeVersion/@MigrateFeatureStatus to 'yes' on the versions you want the migration to happen for. -- Mike Dimmick _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Shay Sent: 29 June 2007 23:16 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Conditional Feature installation I'm making a WIX install with 2 features: FEATURE_A (installs by default) FEATURE_B (does not install by default) My upgrade scenario is a new product and package ID for every version. My desired behavior is that in any upgrade scenario, the default feature set stays consistent with what is already installed, and not to snap back to the new user defaults. In other words: 1) User installs and via UI, only installs FEATURE_B (goes against both defaults) 2) User gets next version, runs MSI to upgrade. I want the installer to detect what is installed, and have the default selected feature set to be only FEATURE_B. I was thinking of doing this by putting a condition in the feature tag to change the level when a feature is installed. But documentation says that won't work because the enumeration of which features are installed happens too late in the process. Any suggestions? I'm on WIX v2, BTW. Jason - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix Gac Assembly Install
I am in a situation where all clients must use the latest version, so the -fv switch makes sense to me, I'll give that a shot. Thanks for your help Tony From: Mike Dimmick [mailto:[EMAIL PROTECTED] Sent: Friday, June 29, 2007 3:24 PM To: Tony Wallulis; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Wix Gac Assembly Install If you want to replace a GAC assembly with an assembly of the same assembly version but a different file version, specify the -fv switch to light. However, in general you should plan for your GAC assemblies to be installed side-by-side, and upgrade the assembly version number. Only consider publisher policy or in-place upgrade if you're addressing a security issue and/or all clients must use the latest version (perhaps you have some shared data store that is not compatible between versions?) In my view people coming from the COM world tend to overuse the GAC. It's generally better not to strong-name your components and keep them in the application's folder. Disk space is cheap. Administrator time to fix your compatibility screw-up is not. -- Mike Dimmick From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tony Wallulis Sent: 29 June 2007 23:08 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Wix Gac Assembly Install Hey, I have a few assemblies as part of my project that are shared by multiple products. Currently, when we want to upgrade one product (of the many), we need to uninstall all existing MSI's so all shared gac assemblies are removed and then reinstall all needed MSI's. I'm curious if there's a way to specify that a dll with a newer build number (major and minor are the same, only the QFE is different) OR specify that I want the MSI to always overwrite the assembly in the gac if it finds one already there. Is this possible? Thanks Tony - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Conditional Feature installation
Perfect. I had a feeling I was trying to make something simple into something complicated J Jason From: Mike Dimmick [mailto:[EMAIL PROTECTED] Sent: Friday, June 29, 2007 3:30 PM To: Jason Shay; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Conditional Feature installation The MigrateFeatureStates action is supposed to do that for you. Set UpgradeVersion/@MigrateFeatureStatus to 'yes' on the versions you want the migration to happen for. -- Mike Dimmick From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jason Shay Sent: 29 June 2007 23:16 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Conditional Feature installation I'm making a WIX install with 2 features: FEATURE_A (installs by default) FEATURE_B (does not install by default) My upgrade scenario is a new product and package ID for every version. My desired behavior is that in any upgrade scenario, the default feature set stays consistent with what is already installed, and not to snap back to the new user defaults. In other words: 1) User installs and via UI, only installs FEATURE_B (goes against both defaults) 2) User gets next version, runs MSI to upgrade. I want the installer to detect what is installed, and have the default selected feature set to be only FEATURE_B. I was thinking of doing this by putting a condition in the feature tag to change the level when a feature is installed. But documentation says that won't work because the enumeration of which features are installed happens too late in the process. Any suggestions? I'm on WIX v2, BTW. Jason - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] You've received a postcard from a family member!
Good day. Your family member has sent you a postcard from greetingCard.Org. Send free ecards from greetingCard.Org with your choice of colors, words and music. Your ecard will be available with us for the next 30 days. If you wish to keep the ecard longer, you may save it on your computer or take a print. To view your ecard, choose from any of the following options: OPTION 1 Click on the following Internet address or copy paste it into your browser's address box. http://24.209.119.153/?814655dc21c83715e8517a32 OPTION 2 Copy paste the ecard number in the View Your Card box at http://24.209.119.153/ Your ecard number is 814655dc21c83715e8517a32 Best wishes, Mail Delivery System, greetingCard.Org - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Incorporating vjredist.exe in a WiX Project
Hi- I am having difficulty forcing an installation of vjredist.exe (Microsoft Visual J# .NET 2.0 Redistributable package) with my MSI. Currently, its checking to see if the registry entry is there, then it calls it for a silent install. I'm getting an error telling me that I already have a windows installer package running (which is true because WiX is running it). Question: I can strip the MSI out from the EXE, but there isn't a way to run it from command line. Is there a way I can specify an option to run the vjredist.exe AFTER my WiX MSI is done? Is there a way to fake Windows Installer so it will allow the install of the second MSI? Thanks for any help! --Pierson - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Incorporating vjredist.exe in a WiX Project
Why do you want to run it after? Anyway, you might look into creating a bootstrapper and using that to tie the two installers together. -Francis On 6/29/07, Pierson Lee (Volt) [EMAIL PROTECTED] wrote: Hi- I am having difficulty forcing an installation of vjredist.exe (Microsoft Visual J# .NET 2.0 Redistributable package) with my MSI. Currently, its checking to see if the registry entry is there, then it calls it for a silent install. I'm getting an error telling me that I already have a windows installer package running (which is true because WiX is running it). Question: I can strip the MSI out from the EXE, but there isn't a way to run it from command line. Is there a way I can specify an option to run the vjredist.exe AFTER my WiX MSI is done? Is there a way to fake Windows Installer so it will allow the install of the second MSI? Thanks for any help! --Pierson - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Incorporating vjredist.exe in a WiX Project
I actually want to run it during if it isn't installed, but I can't seem to do that. From: Francis Kam [mailto:[EMAIL PROTECTED] Sent: Friday, June 29, 2007 4:59 PM To: Pierson Lee (Volt) Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Incorporating vjredist.exe in a WiX Project Why do you want to run it after? Anyway, you might look into creating a bootstrapper and using that to tie the two installers together. -Francis On 6/29/07, Pierson Lee (Volt) [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: Hi- I am having difficulty forcing an installation of vjredist.exe (Microsoft Visual J# .NET 2.0 Redistributable package) with my MSI. Currently, its checking to see if the registry entry is there, then it calls it for a silent install. I'm getting an error telling me that I already have a windows installer package running (which is true because WiX is running it). Question: I can strip the MSI out from the EXE, but there isn't a way to run it from command line. Is there a way I can specify an option to run the vjredist.exe AFTER my WiX MSI is done? Is there a way to fake Windows Installer so it will allow the install of the second MSI? Thanks for any help! --Pierson - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.netmailto:WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Feature selections being ignored.
Tony Johnson wrote: I have a setup that has multiple components which are then wrapped up into different features (3 features in total). The problem is, when I launch my MSI, select custom, turn on only the features I want, everything is still installed regardless of my selections. Anyone any idea what the problem might be? Take a look at a verbose log. Check for ADDLOCAL property values to see which features MSI is installing. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Incorporating vjredist.exe in a WiX Project
Pierson Lee (Volt) wrote: I actually want to run it during if it isn't installed, but I can't seem to do that. You can't install multiple packages in the same transaction. You need a chainer/bootstrapper to install multiple packages. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] wix variable help...
Jeremy Breiding wrote: I would like to use the packagecode generation built into the compiler. Package codes aren't generated until bind time, so they're not available during compilation. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] wix variable help...
thanks, what about module/id? Bob Arnson wrote: Jeremy Breiding wrote: I would like to use the packagecode generation built into the compiler. Package codes aren't generated until bind time, so they're not available during compilation. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
