Re: [WiX-users] Shared Files
Bob Arnson wrote: I didn't find an obvious way to include a file only once in the MSI and install it to serveral locations ... Generally you don't. Instead, you can use WiX's support for smart cabbing so that only a single copy of the file is included in your MSI package regardless of how many times it's installed. See http://robmensching.com/blog/archive/2007/06/01/quotSmart-cabbingquot-added-to-WiX-toolset.aspx for details. Yeah, I've found this article before ... but how would I do this within my app? Do I have to create multiple (identical) File-elements like this: Component Id=CompA Guid=... File Id=CompA.SharedAssembly Source=... / File Id=CompAExe Source=... / /Component Component Id=CompB Guid=... File Id=CompB.SharedAssembly Source=... / File Id=CompBExe Source=... / /Component This seems to be quite hard to maintain, especially if the list of shared assemblies grows longer! -- ... Gentlemen: Start your debuggers... - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] FileShare - Question
Could you also give an example please? I tried following but it also didn't work - it says Failed to create network share. ( -2147 Root): Property Id=ROOTDRIVE Value=C:\/ Directory Id=TARGETDIR Name=SourceDir Component Id=FirstFileShare Guid=6f051579-2950-42e3-9381-2f538ae1de12 CreateFolder/ util:User Id=MyUser Name=user Password=password PasswordNeverExpires=yes RemoveOnUninstall=yes UpdateIfExists=yes CreateUser=yes/ util:FileShare Id =ShareRoot Name=Root util:FileSharePermission GenericAll=yes User=MyUser Read=yes/ /util:FileShare /Component /Directory And additionally I have another question: How can I set the share-permission for a usergroup and not for a single user only? - Chris -- Set the ROOTDRIVE property to C:\ and Move your component under the TARGETDIR DirectoryId tag. I am not sure why you would want your setup package to share the root. That seems a little dangerous and counterintuitive. //aj On Jan 2, 2008 8:14 AM, Chris [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi there, I probably have a quite simple question: How can I set the sharing of my C-drive and name it as Root? I tried something like this but it creates the Root-folder: Directory Id=TARGETDIR Name=SourceDir Directory Id=INSTALLDIR Directory Id=MyRoot Name=Root Component Id=FirstFileShare Guid=6f051579-2950-42e3-9381-2f538ae1de12 CreateFolder/ util:User Id=MyUser Name=user Password=password PasswordNeverExpires=yes RemoveOnUninstall=yes UpdateIfExists=yes CreateUser=yes/ util:FileShare Id =ShareRoot Name=Root util:FileSharePermission GenericAll=yes User=MyUser Read=yes/ /util:FileShare /Component /Directory /Directory /Directory Thank's in advance, Chris - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] FileShare - Question
Could you also give an example please? I tried following but it also didn't work - it says Failed to create network share. ( -2147 Root): Property Id=ROOTDRIVE Value=C:\/ Directory Id=TARGETDIR Name=SourceDir Component Id=FirstFileShare Guid=6f051579-2950-42e3-9381-2f538ae1de12 CreateFolder/ util:User Id=MyUser Name=user Password=password PasswordNeverExpires=yes RemoveOnUninstall=yes UpdateIfExists=yes CreateUser=yes/ util:FileShare Id =ShareRoot Name=Root util:FileSharePermission GenericAll=yes User=MyUser Read=yes/ /util:FileShare /Component /Directory And additionally I have another question: How can I set the share-permission for a usergroup and not for a single user only? - Chris -- Set the ROOTDRIVE property to C:\ and Move your component under the TARGETDIR DirectoryId tag. I am not sure why you would want your setup package to share the root. That seems a little dangerous and counterintuitive. //aj On Jan 2, 2008 8:14 AM, Chris [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi there, I probably have a quite simple question: How can I set the sharing of my C-drive and name it as Root? I tried something like this but it creates the Root-folder: Directory Id=TARGETDIR Name=SourceDir Directory Id=INSTALLDIR Directory Id=MyRoot Name=Root Component Id=FirstFileShare Guid=6f051579-2950-42e3-9381-2f538ae1de12 CreateFolder/ util:User Id=MyUser Name=user Password=password PasswordNeverExpires=yes RemoveOnUninstall=yes UpdateIfExists=yes CreateUser=yes/ util:FileShare Id =ShareRoot Name=Root util:FileSharePermission GenericAll=yes User=MyUser Read=yes/ /util:FileShare /Component /Directory /Directory /Directory Thank's in advance, Chris - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix 3.0.3621.0
I did find the new WIX project types.. I guess I expected to find a WIX Add-In.. which must not apply in this case. I will move forward and work with the WIX project types. Thanks for your assistance. Philip From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 02, 2008 10:15 PM To: Philip Lippard Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Wix 3.0.3621.0 Philip Lippard wrote: What is the status of the above WIX install with VS.NET 2008 RTM ? Is Votive still installed with this release ? Yes. What features are shown if you click Advanced? -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Crystal Reports Merge Module Installation Woes
Bob Arnson írta: Szentpali Janos wrote: Merge modules are generally now considered bad practice... If this is true than what is the point of the whole MSI system? I mean if I have a 3rd party component (x.dll) that 4th party and 5th party are using too, how does the system decide that the x.dll component installed by the 4th party's installer and the x.dll component installed by the 5th party's installer are the same and how does it make sure that upon un-install it is only un-installed if both (all) products are un-installed and that it IS un-installed if both (all) products are un-installed? I'm thinking of a common file placed under say %COMMONPROGRAMFILES%\3rd Party\x.dll.. MSI manages that at the component level; merge modules are an authoring construct, not an installation construct. Because patches target products, not components, however, most redistributables are shipped as MSI packages, not merge modules. Does that mean that the same file, installed by two unrelated setup packages into the same path, with two distinct component and file ids (guids) will still be correctly uninstalled/managed? I mean if you uninstall the product that was installed last, will the file be left for the first product to use? Will the file be completly removed when both products will have been uninstalled? -- Szentpáli János - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] tallow and empty directories
I am new to WIX and am using tallow -d to generate a FileSet for a specific directory and all the directories and files below. The output is a FileSet that contains several components, each one for the files of a certain directory. These components get collected in the FeatureSet for later installation. But what about installing empty directories? They do not contain files, therefore no components are created and thus they are not installed. How can I use tallow to collect all files and create a component for the empty directories, too? Thanks for your help in advance. -- View this message in context: http://www.nabble.com/tallow-and-empty-directories-tp14598129p14598129.html Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Problem Starting service on XP
In the end it was the the exe.config file not being included with the serice.exe file. I added the following in the service component and it works. File Id='ServiceConfig' Name='Call Manager Service.exe.config' Source='Call Manager Service.exe.config' ReadOnly='no' Vital='yes' Hidden='no' System='no' Checksum='no' / Thanks for all your help identifying this. Wilson, Phil wrote: If it can be started ok after the install then the issue could be dependencies. If it's dependent on an assembly in the GAC or (on Vista) the C++ CRT support being installed from a merge module these won't be available at StartServices time. Phil Wilson -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Graham Vickrage Sent: Wednesday, January 02, 2008 10:42 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Problem Starting service on XP I am trying to install and start a service but its coming back with. Error msg: Verify that you have sufficient priveleges to start system services. I am running the msi file as an administrator. I can install / start the service manually but not via wix, has anyone seen this before and do they have sample code? Much appreciated. Graham Code: Component Id='ServiceExeComponent' Guid='6ca52ece-6346-4bbf-ae10-248cc3ab74c4' SharedDllRefCount='no' KeyPath='no' NeverOverwrite='no' Permanent='no' Transitive='no' Win64='no' Location='either' File Id='ServiceExeFile' Name='Call Manager Service.exe' DiskId='1' Source='Call Manager Service.exe' ReadOnly='no' KeyPath='yes' Vital='yes' Hidden='no' System='no' Checksum='no' / ServiceInstall Id='CMServiceInstall' DisplayName='Call Manager Service' Name='Call Manager Service' ErrorControl='normal' Start='auto' Type='ownProcess' Vital='yes' Interactive=no / ServiceControl Id='CMServiceControl' Name='Call Manager Service' Start='install' Stop='both' Remove='uninstall' Wait='yes' / /Component - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] SQL Elements are not recognized in Visual Studio?
I did not have those so I added them, the top of my file now looks like this: Wix xmlns='http://schemas.microsoft.com/wix/2006/wi' xmlns:util=http://schemas.microsoft.com/wix/UtilExtension; xmlns:sql= http://schemas.microsoft.com/wix/SqlExtension; xmlns:ui=http://schemas.microsoft.com/wix/UIExtension; I added a reference to WixSqlExtension, WixUIExtension and WixUtilExtension in my VS project as well. I still get an error that says the Product element contains an unexpected child element 'User'. I get another one that says the Component element contains an unexpected child element 'SqlDatabase'. Any other ideas? Did you add the references to your extensions in your WiX project? ...and, did you add the schemas to the wxs file? i.e. Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:util=http://schemas.microsoft.com/wix/UtilExtension; xmlns:sql=http://schemas.microsoft.com/wix/SqlExtension; xmlns:ui=http://schemas.microsoft.com/wix/UIExtension; Regards, //aj -- View this message in context: http://www.nabble.com/SQL-Elements-are-not-recognized-in-Visual-Studio--tp14587359p14599738.html Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] tallow and empty directories
Joa wrote: But what about installing empty directories? They do not contain files, therefore no components are created and thus they are not installed. How can I use tallow to collect all files and create a component for the empty directories, too? Tallow doesn't support that. You can use a CreateFolder element to create empty directories but you'll have to edit the output by hand. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Shared Files
Henning Eiben wrote: Yeah, I've found this article before ... but how would I do this within my app? Do I have to create multiple (identical) File-elements like this: Yes. You can use CopyFile to install one and copy it elsewhere but it's about the same amount of work and CopyFile isn't necessarily serviceable. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Crystal Reports Merge Module Installation Woes
Szentpali Janos wrote: Does that mean that the same file, installed by two unrelated setup packages into the same path, with two distinct component and file ids (guids) will still be correctly uninstalled/managed? No, that's what component rules are about. The component GUID and resource IDs must be stable. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] SQL Elements are not recognized in Visual Studio?
JCWrs wrote: I still get an error that says the Product element contains an unexpected child element 'User'. I get another one that says the Component element contains an unexpected child element 'SqlDatabase'. Are you supplying the namespace in the element name (i.e., util:User... and sql:SqlDatabase)? -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] SQL Elements are not recognized in Visual Studio?
Nope, I wasn't. That fixed it. Thanks all! -Original Message- From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Thursday, January 03, 2008 10:31 AM To: Alex Steen Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] SQL Elements are not recognized in Visual Studio? JCWrs wrote: I still get an error that says the Product element contains an unexpected child element 'User'. I get another one that says the Component element contains an unexpected child element 'SqlDatabase'. Are you supplying the namespace in the element name (i.e., util:User... and sql:SqlDatabase)? -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to create help file shortcut icon?
On Jan 2, 2008 4:22 PM, Mike Dimmick [EMAIL PROTECTED] wrote: What you specify in the Icon elements gets incorporated in your .msi as a binary at build time, so it should be something you have control over, not attempting to use a system executable. The warning message is described in the documentation for the Icon table, where it states: Icon files that are associated with shortcuts must be in the EXE binary format and must be named such that their extension matches the extension of the target. The shortcut will not work if this rule is not followed. For example, if a shortcut is to point to a resource having the key file Red.bar, then the icon file must also have the extension .bar. Multiple icons can be stuffed into the same icon file as long as all of the target files have the same extension. The Id attribute is used for the icon file's name when it is extracted onto the system. So you should use something like: Icon Id=helpicon.chm SourceFile=myhelpicon.dll / Thanks for the reply, but I'm even more confused now... Doesn't the above code violate the above paragraph? Having the icon for a *.chm pointing to a *.dll? I'm still not sure how to solve the problem of creating a help icon for my .CHM shortcut. Should I be creating a single DLL that only contains the help icon (and if I copy the one from WinHlp32.exe, am I violating some sort of Microsoft copyright)? Is there some way to have the icon point to a file that's already installed? Surely others have solved this, what was your solution? -- -Chris - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Disable autoplay on multidisk installs?
Does anyone have a suggestion on how to disable autoplay after the first disk in a multi-disk install? Right now I have the following: - Insert Disk 1: Autoplay runs and executes my setup.msi via a setup.exe program. Disk 1 files are installed. - Installer prompts for Disk 2, but at the same time autoplay executes and opens Disk 2 in explorer. I'm trying to disable the latter action. Thanks for the help. This list and the archives have been invaluable in climbing the Wix learning curve. Regards, Craig --- http://www.overlandnavigator.com Touchscreen Friendly GPS Mapping - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to create help file shortcut icon?
On Thu, 3 Jan 2008 08:57:04 -0800, Chris Weiss wrote: Chris, the problem of creating a help icon for my .CHM shortcut. Should I be creating a single DLL that only contains the help icon (and if I copy the one from WinHlp32.exe, am I violating some sort of Microsoft copyright)? Yes, create a small DLL with only the icon. I don't know about the copyright issues but there are lots of free icons to be downloaded from the net, they usually come with the standard icon set redesigned and they will have a question mark icon for sure. Their copyright status might be easier to check. Bye, Gábor --- DEÁK JAHN, Gábor -- Budapest, Hungary E-mail: [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Localization of Product ID and other GUIDs -- Is bug 1075824 fixed?
I'm trying to prepare my product for localization and I ran into a problem localizing the GUIDs for the Product ID and Upgrade Code. I noticed a couple messages about this and I also saw that a bug about this was closed several months ago, and I'm curious if this has been fixed in a more-recent build of WiX than I'm using (3.0.2723.0)? We plan on upgrading to the latest version of WiX v3 soon anyhow to get the event manifest installation functionality, so it would be nice to get this issue resolved too. -- View this message in context: http://www.nabble.com/Localization-of-Product-ID-and-other-GUIDsIs-bug-1075824-fixed--tp14604758p14604758.html Sent from the wix-users mailing list archive at Nabble.com. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Crystal Reports Merge Module Installation Woes
Bob Arnson írta: Szentpali Janos wrote: Does that mean that the same file, installed by two unrelated setup packages into the same path, with two distinct component and file ids (guids) will still be correctly uninstalled/managed? No, that's what component rules are about. The component GUID and resource IDs must be stable. Can you suggest some strategy to help one install components that do not come in msi-s or msm-s but that are shared/common components that could/would possibly be installed by non msi setups? -- Szentpáli János - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ICE03: String overflow warning
My question is: Can I safely ignore this warning?
It would be wise to avoid the warning.
Schema of the CustomAction table shows that Action field is S255 which is up to
255 characters.
CustomAction.idt
Action TypeSource Target
s72 i2 S72 S255
CustomActionAction
Property.idt
PropertyValue
s72 l0
PropertyProperty
However, Value field in Property table is not bound to 255 characters.
You can define a property (e.g. MyCaData) and use the property in CustomAction
definition using brackets. (e.g. [MyCaData])
Just out of curiosity: You say you have an immediate action which calls
DoAction to run your deferred action. Do you have a reason for this? I
have just an immediate action (Type 51) which sets the property and
hardcoded my deferred action in the InstallExecuteSequence...
You can also schedule an immediate custom action and a deferred one in
InstallExecuteSequence in pairs.
But in a way using MsiDoAction, you only have to schedule an immediate custom
action. And from an immediate custom action, you can schedule a deferred custom
action several times.
for (int i = 0; i 10; ++i) {
/* You can also set progress bar estimate here as well */
MsiSetProperty(MyDeferredCustomAction, mydata[i]);
MsiDoAction(MyDeferredCustomAction);
}
The above will schedule MyDeferredCustomAction several times with different
data, usually read from a custom table.
Custom actions in wix source codes may be a good reference. Hope this helps.
Regards,
Chesong Lee
-Original Message-
From: Krause, Henning [mailto:[EMAIL PROTECTED]
Sent: Saturday, December 29, 2007 2:25 AM
To: Chesong Lee; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] ICE03: String overflow warning
Hi Lee,
thanks for your reply. I know about all these restrictions. That's why
my CustomActionData property is so big :-)
I have already scheduled an immediate property which puts all the needed
properties in the appropriate custom action property. The point is that
the property exceeds 255 chars and causes this ICE03 warning.
My question is: Can I safely ignore this warning?
Just out of curiosity: You say you have an immediate action which calls
DoAction to run your deferred action. Do you have a reason for this? I
have just an immediate action (Type 51) which sets the property and
hardcoded my deferred action in the InstallExecuteSequence...
Kind regards,
Henning Krause
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of
Chesong Lee
Sent: Saturday, December 29, 2007 3:39 AM
To: wix-users@lists.sourceforge.net
Cc: Krause, Henning
Subject: Re: [WiX-users] ICE03: String overflow warning
Codes in deferred custom action cannot directly access MSI database.
In the function, you can only read CustomActionData property, of
which value is set as the name of the custom action.
For example, to transfer the data to the deferred custom action named
MyDeferredCustomAction, you have to set the property
MyDeferredCustomAction by defining it in the MSI Property table or
using immediate custom actions. And then in your deferred custom
action code, you use MsiGetProperty(_T(CustomActionData), ...) to
retrieve the value.
See this: http://msdn2.microsoft.com/en-us/library/aa370543.aspx
In well-coded custom actions where deferred custom actions are
required, we only schedule the immediate custom actions in the
InstallExecutionSequence table, and in an immediate custom action
(MyImmediateCustomAction) , we access the MSI table and set
MyDeferredCustomAction property appropriately and call
DoMsiAction(MyDeferredCustomAction). As MSI properties only can be
strings, you may have to use parsers or use binary-to-text
encoder/decoder (e.g. binhex, base64 or ascii85).
Hope this helps.
On Dec 28, 2007 8:47 AM, Krause, Henning [EMAIL PROTECTED] wrote:
Hi,
When I compile my WIX project, I get the following warning:
ICE03: String overflow (greater than length permitted in column);
Table:
CustomAction, Column: Target
Is this something I should care about? After all, the column is
limited
(according to Orca) to 255 chars which is not enough given that I
must
put in all the data I want to access from a deferred custom action.
Or
is there another way to transfer data from the MSI database to a
deferred custom action?
Kind regards,
Henning
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R)
[WiX-users] 32 64 bit
Hi,
1) Is it possible to create one MSI for both 32bit and 64 bit OS
2) If yes
my queries are
1) In my case, except 2 binaries, remaining all binaries are same.
The binaries which are different are service32.exe for 32bit and
service64.exe for 64 bit
So I added win64=yes for service64.exe.
2)Following is my Directory structure
Directory Id=ProgramFilesFolder Name=PFiles LongName=program files
Directory Id=Test Program Name=Test_1 LongName =Test program
Directory Id=INSTALLDIR Name=Clint LongName=Client
Directory Id=Manifests Name=MANIFE_1 LongName=manifests/
/Directory
/Directory
/Directory
I saw there is ProgramFiles64Folder for 64bit OS. So how can I modify the
above code
3)Registry
following is my component(same for both 3264)
here am creating registry key and setting its value.
Component Id=xyz.exe Guid={???} DiskId=1
File Id=xyz.exe Name=xyz.exe KeyPath=yes Source=xyzexe /
Registry Root=HKLM Key=SOFTWARE\TestProgram\Client Name=InstallRoot
Action=write Type=expandable Value=[INSTALLDIR] /
Registry Root=HKLM Key=SOFTWARE\test program\Client\Diagnostic
Logging\Default Name=Severity Type=string Value=ERROR /
/Component
Here am using Root=HKLM Key=SOFTWARE\TestProgram\Client is ok for 32
bit.
Will the same code create the key for 64bit. I think for 64bit registry
entries will create
under WOW64 hive. How can I modify here?
--
View this message in context:
http://www.nabble.com/32---64-bit-tp14611317p14611317.html
Sent from the wix-users mailing list archive at Nabble.com.
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ICE03: String overflow warning
In article [EMAIL PROTECTED], Chesong Lee [EMAIL PROTECTED] writes: My question is: Can I safely ignore this warning? It would be wise to avoid the warning. While I agree with this, I would add that in practice I've never seen a problem arising from overflowing the field. Still, it puts you in a position of working by accident instead of working by design. I've learned the hard way over the years that working by accident situations eventually break when they change the implementation in some way. -- The Direct3D Graphics Pipeline -- DirectX 9 draft available for download http://www.xmission.com/~legalize/book/download/index.html Legalize Adulthood! http://blogs.xmission.com/legalize/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
