[WiX-users] Change TARGETDIR if space is not avilable and installs in another drive In Silent Mode(not in UI mode)
hi,
My requirement is
- In case of Silent Install, when user give the command msiexec /i abcdef.msi
/q
by default it installs in C drive.
If C drive doesn't have enough space, then my installer automatically selects
another drive
which has space and should install there silently.
Following is the corresponding dll.
Here
- for PATH am setting through custom action
- First it checks default dir ie TARGETDIR ie C:\
_ If space is not avialble it will take another dir(through for loop) and
checks space there.
-Once the space is ok it setts PATh to
MsiSetProperty(hInstaller,MYPROP,PATH);
UINT __stdcall DiskSpace(MSIHANDLE hInstaller)
{
-
-
rc = MsiGetProperty(hInstaller, PATH, PATH[0], PATHSize);
space = findDiskSpace(PATH); /*fn that checks space and checks with
req_space and if it satisfies returns TRUE */
if(space)
{
rc = MsiSetProperty(hInstaller,MYPROP,PATH);
if (rc != ERROR_SUCCESS)
{
::MessageBox(NULL, MsiSetProperty(ProductId) failed., Error,
MB_OK);
return ERROR_INSTALL_FAILURE;
}
-
-
return 0;
}
Below is my wix code:
Directory Id='TARGETDIR' Name='SourceDir'
Directory Id='ProgramFilesFolder' Name='PFiles'
Directory Id='MyDir' Name='TestProg' LongName='Test Program'
Component Id='MyComponent'
Guid='12345678-1234-1234-1234-123456789012'
File Id='readme' Name='read.txt' LongName='readme.txt'
DiskId='1' src='C:\readme.txt' Vital='yes' /
/Component
/Directory
/Directory
/Directory
Feature Id='MyFeature' Title='My 1st Feature' Level='1'
ComponentRef Id='MyComponent' /
/Feature
InstallExecuteSequence
Custom Action=SetPATHValue After=AppSearch
SilentInstall/Custom
Custom Action=DiskSp
Before=LaunchConditionsSilentInstall/Custom
Custom Action='DirectorySet' Before='LaunchConditions'NOT TARGETDIR AND
SilentInstall/Custom
/InstallExecuteSequence
Binary Id=BinDiskSp SourceFile=C:\SampleDLL.dll/Binary
CustomAction Id=DiskSp BinaryKey=BinDiskSp
DllEntry=DiskSpace/CustomAction
CustomAction Id=SetPATHValue Property=PATH Value=[TARGETDIR] /
CustomAction Id=DirectorySet Property=TARGETDIR
Value=[MYPROP]/CustomAction
Property Id=MsiLoggingvoicewarmupx/Property
Property Id=SilentInstallINSTALLUILEVEL_NONE/Property
Note: My C drive doesn't have enough space. So it will select D drive(From Dll)
When I execute msi in silent mode through it is installing in C drive only.
Any inputs where am wrong?
-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Light.exe: error LGHT0094
Hi,
I have generated a wxs file using heat.exe (I have installed Wix3.0.3530.0.msi)
and used the option -template:product.
I have fixed all GUIDs and errors generated by candle.exe and obtained a wixobj
file.
Now when I ran the linker light.exe against the object file, I get the
following error:
C:\WIX\Fundamental.wxs(3122) : error LGHT0094 : Unresolved reference to symbol
'File:ADODB.dll' in section 'Fragment:'.
The section of the wxs file that it is complaining about is the following:
FragmentDirectoryRef Id=ServiceComponent
Id=ADODB.dll_1 Guid={F8212B96-ABAB-49db-80B5-ECB8E0445F20}
Class Id={0507--0010-8000-00AA006D2EA4} Context=InprocServer32
Server=ADODB.dll /Class
Id={050B--0010-8000-00AA006D2EA4} Context=InprocServer32
Server=ADODB.dll /Class
Id={0514--0010-8000-00AA006D2EA4} Context=InprocServer32
Server=ADODB.dll /Class
Id={0535--0010-8000-00AA006D2EA4} Context=InprocServer32
Server=ADODB.dll /Class
Id={0560--0010-8000-00AA006D2EA4} Context=InprocServer32
Server=ADODB.dll /Class
Id={0566--0010-8000-00AA006D2EA4} Context=InprocServer32
Server=ADODB.dll /File Id=ADODB.dll_1 Name=ADODB.dll
KeyPath=yes Source=C:\Program Files\Fundamental Software\Portfolio
Manager\Service\ADODB.dll TypeLib
Id={EF53050B-882E-4776-B643-EDA472E8E3F2} Language=1033 MajorVersion=2
MinorVersion=7 //File ProgId Id=Record
/RegistryValue Root=HKCR
Key=CLSID\{0507--0010-8000-00AA006D2EA4}\InprocServer32\7.0.3300.0
Name=Class Value=ADODB.CommandClass Type=string Action=write /
RegistryValue Root=HKCR
Key=CLSID\{0507--0010-8000-00AA006D2EA4}\InprocServer32\7.0.3300.0
Name=Assembly Value=ADODB, Version=7.0.3300.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a Type=string Action=write /
RegistryValue Root=HKCR
Key=CLSID\{0507--0010-8000-00AA006D2EA4}\InprocServer32\7.0.3300.0
Name=RuntimeVersion Value=v1.1.4322 Type=string Action=write /
RegistryValue Root=HKCR
Key=CLSID\{0507--0010-8000-00AA006D2EA4}\InprocServer32\7.0.3300.0
Name=CodeBase Value=[#ADODB.dll_1] Type=string Action=write /
I have the library ADODB.dll file in C:\Program Files\Fundamental
Software\Portfolio Manager\Service\
Can somebody tell me what I am missing with the above?
Many Thanks,
David Nsengiyumva email:[EMAIL PROTECTED]
+++
Date: Mon, 3 Dec 2007 07:50:18 -0800From: [EMAIL PROTECTED]: [EMAIL PROTECTED]:
[EMAIL PROTECTED]: Re: [WiX-devs] Light.exe: error LGHT0093
Please use the wix-users list for questions about using WiX. NSENGIYUMVA DAVID
wrote:
Light.exe : error LGHT0093 : Could not find entry section in provided list of
intermediaries.That means you didn't give light a .wixobj that contained a
Product or Module (or a couple of patch-related ones).--
sig://boB
http://joyofsetup.com/
_
Get the next generation of Windows Live services now!
http://get.live.com-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Using -loc
Hi, Is there a way for using -loc with wild cards instead of mentioning the actual file names one by one?? For example, something like: Light.exe -cultures:en-US -loc *_en-us.wxl -out MyProd.msi MyProd.wixobj - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Listing extant websites
Just so I don't find myself reinventing the wheel, is it possible to get a list of the currently provisioned websites in IIS using WixIISExtension? I ask because the current behavior seems to be a silent overwrite of any existing website with the same settings as the one being installed. This obviously isn't the best of plans, so I am looking for a way to prevent it. Duncan Lundie Privileged/Confidential information may be contained in this email and is intended for the use of the addressee only. If you are not the addressee, you may not copy or otherwise use the information. If you receive this email by mistake, please notify us immediately at: [EMAIL PROTECTED] Although this message and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus-free and no responsibility is accepted by Letsure Limited (Letsure) for any loss or damage in any way arising from its use. Letsure Limited Registered in England No. 03010153 Registered Office: Hargrave House Belmont Road Maidenhead Berkshire SL6 6TB Letsure Limited is authorised and regulated by the Financial Services Authority. Registration number is 313817. Letsure Limited is part of the Erinaceous Group plc. Registered in England No. 3732607 Registered Office: Phoenix House, 11 Wellesley Road, Croydon CR0 2NW- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] MsiSetProperty - Value is not displaying
Hi, INSTALLPATH refers - Property Id=INSTALLPATHC:\/Property char PATH[256]; DWORD PATHSize = sizeof(PATH); MsiGetProperty(hInstaller, INSTALLPATH, PATH[0], PATHSize); Now am the same am trying to assign new ppty ie INSTALLNEWPATH MsiSetProperty(hInstaller,INSTALLNEWPATH,PATH); When am trying to print the ppty INSTALLNEWPATH , nothing is printing. Can any one tell me what is the wrong here. -- View this message in context: http://www.nabble.com/MsiSetProperty---Value-is-not-displaying-tf4943019.html#a14150359 Sent from the wix-users mailing list archive at Nabble.com. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Handling Feature Dependencies
Thanks For the Response John, But that is what I did with the segment below. It kept giving me, this error however - error LGHT0095 : Multiple primary references were found for Feature 'fC' ... Or Am I missing something in my Fragment? It is a FeatureGroup including MergeRefs. I did include it as you stated. From: John Hall [mailto:[EMAIL PROTECTED] Sent: Monday, December 03, 2007 2:59 PM To: Robert Priest; [EMAIL PROTECTED] Cc: wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Handling Feature Dependencies Robert, What you need to do is put the MergeRefs under the FeatureGroup, and then include the FeatureGroup using FeatureGroupRefs in the Features that need the merge modules. Cheers, John From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 03 December 2007 17:04 To: [EMAIL PROTECTED]; John Hall Cc: wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Handling Feature Dependencies Yes. That is true. But what I used is a FeatureGroup element. Then, under the FeatureGroup Element, I use a mergeref. So I have something like: Fragment FeatureGroup Id=grpRequiredFeatures Feature Id=fC Title=FeatureFC Level=1 Absent=disallow Display=hidden MergeRef Id=MFC / MergeRef Id=MFCPolicy / /Feature /FeatureGroup /Fragment But that still presents a problem because it appears you can't include one feature under multiple features... Is that correct? I keep getting: error LGHT0095 : Multiple primary references were found for Feature 'fC' ... Is there really no way to group these merge modules (and possibly other components) together and use them under different features. Sounds like what I have to do is to include each MergeRef multiple times. So fA and fB must both include MergeRef MFC and MergeRef MFCPolicy... So if I have 10 merge modules that should get delivered with two different features, I will end up with 20 MergeRef lines? Is there no better way to group merge modules together and use them in different features? BTW - part of me doing this is so that the next button on the Feature Selection screen gets disabled. However, even when I have nothing selected in the Feature Tree, the next button is still enabled. How do I stop that? From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Monday, December 03, 2007 10:59 AM To: John Hall Cc: Robert Priest; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Handling Feature Dependencies John Hall wrote: FeatureGroupRefs can contain MergeRefs though. Good point. I haven't needed FeatureGroups before. -- sig://boB http://joyofsetup.com/ - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Specifying name dynamically for environment variable doesn't seem to work.
I believe the Environment WiX element maps to a row in the Environment table. The Name column only allows for a text string (which is not further evaluated) and not a formatted string (which allows property replacement), so I think you are hosed but I could be wrong. Jim -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Reed (MCS - HOUSTON) Sent: Tuesday, December 04, 2007 8:46 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Specifying name dynamically for environment variable doesn't seem to work. Howdy, folks. I'm trying to accomplish the following (without success): Environment Id=Framework.Configuration.Path Name=[TARGETENV] Value=[TARGETDIR]Configuration\Framework.dtsconfig Action=set System=yes / This creates an environment variable named [TARGETENV] *not* an environment variable of the name specified in the installer form's edit field. I can understand Id not supporting property expansion, but I'm hosed if Name doesn't. Am I doing something wrong? Or is this just something thou shalt not? - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error 2908
I found the reason of that problem by using RegMon where I saw the 1450 error when opening a registry key. Then I found those following URLs which perfectly match my problem: - http://tinyurl.com/2rj93p - http://tinyurl.com/3ey6fe Getting rid of the `Components' subtree (there was only one child in it, the offending key) made my installation works just fine. Thanks, Manu Emmanuel Stapf [ES] wrote: I did try to run my installation after a fresh reboot and uninstalling whatever I did not need on this machine. Any idea what kind of resources it might be? Thanks, Manu Bob Arnson-6 wrote: Error 1450 is ERROR_NO_SYSTEM_RESOURCES. Have you tried an installation after a fresh reboot? -- sig://boB http://joyofsetup.com/ - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- View this message in context: http://www.nabble.com/Error-2908-tf4789609.html#a14156848 Sent from the wix-users mailing list archive at Nabble.com. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error 2908
Emmanuel Stapf [ES] wrote: I found the reason of that problem by using RegMon where I saw the 1450 error when opening a registry key. Then I found those following URLs which perfectly match my problem: - http://tinyurl.com/2rj93p - http://tinyurl.com/3ey6fe This is why validation is on by default in WiX v3. -- sig://boB http://joyofsetup.com/ - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] More languages done?
Jim Hewes wrote: Ah. I was only looking in the WiX v3 source. Thanks. Currently the full set of loc strings hasn't been ported to v3. There are some missing strings because of changes in v3. -- sig://boB http://joyofsetup.com/ - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using -loc
Albert Shamsiyan wrote: Is there a way for using --loc with wild cards instead of mentioning the actual file names one by one?? Not from light itself, though you could do it from a batch file or MSBuild project. -- sig://boB http://joyofsetup.com/ - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Light.exe: error LGHT0094
NSENGIYUMVA DAVID wrote:
I have generated a wxs file using heat.exe (I have installed
Wix3.0.3530.0.msi) and used the option -template:product.
I have fixed all GUIDs and errors generated by candle.exe and obtained
a wixobj file.
Now when I ran the linker light.exe against the object file, I get the
following error:
C:\WIX\Fundamental.wxs(3122) : error LGHT0094 : Unresolved reference
to symbol 'File:ADODB.dll' in section 'Fragment:'.
The section of the wxs file that it is complaining about is the following:
Fragment
DirectoryRef Id=Service
Component Id=ADODB.dll_1
Guid={F8212B96-ABAB-49db-80B5-ECB8E0445F20}
Class Id={0507--0010-8000-00AA006D2EA4}
Context=InprocServer32 Server=ADODB.dll /
Class Id={050B--0010-8000-00AA006D2EA4}
Context=InprocServer32 Server=ADODB.dll /
Class Id={0514--0010-8000-00AA006D2EA4}
Context=InprocServer32 Server=ADODB.dll /
Class Id={0535--0010-8000-00AA006D2EA4}
Context=InprocServer32 Server=ADODB.dll /
Class Id={0560--0010-8000-00AA006D2EA4}
Context=InprocServer32 Server=ADODB.dll /
Class Id={0566--0010-8000-00AA006D2EA4}
Context=InprocServer32 Server=ADODB.dll /
File Id=ADODB.dll_1 Name=ADODB.dll KeyPath=yes
Source=C:\Program Files\Fundamental Software\Portfolio
Manager\Service\ADODB.dll
The Class/@Server attribute needs to be the File/@Id attribute of the
server binary. So it needs to be ADODB.dll_1 to match. If Heat produced
that output, it's definitely a bug with the stock harvester code --
please file a bug so if someone starts maintaining Heat again, it'll be
on the list.
--
sig://boB
http://joyofsetup.com/
-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Changing PushButton Text on Dialogs
Rob Jones wrote: I need to change the text on the Back and Next buttons on all dialogs used in my WiX 3.0.2925.0 setup. I'm currently using the WixUI_InstallDir dialog set. I thought that the following might work: All the controls use loc strings, so you can replace the text by overriding the loc strings by adding your own .wxl file. For example: String Id=WixUIBackGo amp;hither/String String Id=WixUINextGo amp;yon/String -- sig://boB http://joyofsetup.com/ - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error 2908
Emmanuel Stapf [ES] wrote: I found the reason of that problem by using RegMon where I saw the 1450 error when opening a registry key. Then I found those following URLs which perfectly match my problem: - http://tinyurl.com/2rj93p - http://tinyurl.com/3ey6fe This is why validation is on by default in WiX v3. What do you mean by that? My install is compiled with WiX v3 and I hadn't see any errors. Are you saying that my package was faulty? If so, what is the fault exactly? Thanks, Manu - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Changing PushButton Text on Dialogs
I need to change the text on the Back and Next buttons on all dialogs used in my WiX 3.0.2925.0 setup. I'm currently using the WixUI_InstallDir dialog set. I thought that the following might work: UI Dialog Id=WelcomeDlg Width=370 Height=270 Control Id=Next Text=Next gt; Type=PushButton Width=56 Height=17 X=236 Y=243/Control Control Id=Back Text=lt; Back Type=PushButton Width=56 Height=17 X=180 Y=243/Control /Dialog /UI However, that results in a compile error of 'Duplicate symbol 'Dialog:WelcomeDlg' found. Another option that I have tried (and it will work) is to change the MSI file after it has been built so that the text column of the Control table has the desired text. I've tried this using Orca and it works, so I suppose I could use Automation to edit the built MSI after each successful build (I'm using Visual Studio 2005). That seems clunkly. Does anyone know of a less-clunky method to accomplish this? Rob Jones, Developer Lightspeed Systems www.lightspeedsystems.com http://www.lightspeedsystems.com - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] show progress text for custom action
Thanks Stefan, I tried using that, and the Progress Text in the dialog shows Removing Backup Files during the execution of my slow custom action, it never renders my text... Heres what I have: CustomAction Id='DEVENV_SETUP' Property='DEVENV8' ExeCommand='/setup' Return='check' Execute='commit' Impersonate='no' / UI ProgressText Action=DEVENV_SETUPConfiguring Visual Studio... (this may take a few minutes)/ProgressText /UI InstallExecuteSequence Custom Action=DEVENV_SETUP After=InstallFiles 1/Custom /InstallExecuteSequence My CA is definitely executing, I can see its process start and chew away at 15% CPU for 3-4 minutes, but the progress text just stays on Removing Backup Files... Thanks - Adam Langley Secon NZ Ltd. A1/400 Rosedale Road Albany North Shore 0632 New Zealand Tel. +64 (0)9 414 4071 Fax. +64 (0)9 414 4072 www.seconag.com -Original Message- From: Stefan Pavlik [mailto:[EMAIL PROTECTED] Sent: Tuesday, 4 December 2007 8:26 p.m. To: Adam Langley Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] show progress text for custom action Hi Adam... You should use the ProgressText element ProgressText Action=YourCustomActionDescription of the custom action/ProgressText Of course you can also use the $(loc.LocalizedDescription) notation for the description (in conjunction with .wxl files) Regards Stefan Adam Langley wrote: Hi guys, I have a custom action which calls a batch file during installation, and it takes a couple of minutes to execute. How can I have the progress-text display “Executing real slow batch file now...this may take a while.” (or something (c; )? Is there a declarative way of describing this? Thanks - Adam Langley Secon NZ Ltd.* *A1/400 Rosedale Road Albany North Shore 0632 New Zealand Tel. +64 (0)9 414 4071 Fax. +64 (0)9 414 4072 www.seconag.com http://www.seconag.com - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Stefan Pavlik | [EMAIL PROTECTED] Whitestein Technologies s.r.o. | www.whitestein.com Panenska 28 | 811 03 Bratislava | Slovak Republic Main +421 2 5443-5502 | Direct +421 2 5930-0735 - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] show progress text for custom action
Adam Langley wrote: ... the Progress Text in the dialog shows Removing Backup Files during the execution of my slow custom action, it never renders my text ... CustomAction ... Execute='commit' ... / My guess: You should make your action be deferred instead of commit. a) Wix ProgressText maps to Windows Installer ActionText table (Wix.chm) b) Action text is only displayed for actions that run within the installation script. Therefore, action text is only displayed for actions that are sequenced between the InstallInitialize and InstallFinalize actions (Windows Installer docs for ActionText Table) c) Your action is a Commit CA. Commit custom actions run after InstallFinalize is finished. (Windows Installer docs for Commit Custom Actions). Therefore I figure the progress is not showing because you've made it a Commit action. Your symptom may have been useful because it raises the question, why is your CA a commit action, rather than deferred? - The purpose of commit actions is to remove any backup information that had been created by a custom action. (Installsite, http://www.installsite.org/pages/en/isnews/200108/index.htm) - That's exactly what you saw the WiX UI choose for the progress text during the commit phase, Removing Backup Files. So... would it be more appropriate for your CA to be a deferred action instead? If so, then you'll have solved your progress text too. Daryn. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] show progress text for custom action
Thanks Daryn, that completely fixed my problem, cheers for the clear explanation aswell! Im always stumbling around exactly when I want to execute my custom actions. Is there a diagram somewhere listing all the install sequence execute events (InstallInitialize, InstallFinalize, etc etc) - in their executed order, explaining what they're doing? Also, if my CA uses Properties, at what point are the properties evaluated and assigned? For example, if I have a deferred CA, which gets passed the installation folder, its possible the CA gets queued before the property has been assigned (I've seen this before trying to use the Quiet Execute Action)... Thanks Regards, Adam Langley Secon NZ Ltd. A1/400 Rosedale Road Albany North Shore 0632 New Zealand Tel. +64 (0)9 414 4071 Fax. +64 (0)9 414 4072 www.seconag.com -Original Message- From: Daryn Mitchell [mailto:[EMAIL PROTECTED] Sent: Wednesday, 5 December 2007 11:29 a.m. To: 'Adam Langley'; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] show progress text for custom action Adam Langley wrote: ... the Progress Text in the dialog shows Removing Backup Files during the execution of my slow custom action, it never renders my text ... CustomAction ... Execute='commit' ... / My guess: You should make your action be deferred instead of commit. a) Wix ProgressText maps to Windows Installer ActionText table (Wix.chm) b) Action text is only displayed for actions that run within the installation script. Therefore, action text is only displayed for actions that are sequenced between the InstallInitialize and InstallFinalize actions (Windows Installer docs for ActionText Table) c) Your action is a Commit CA. Commit custom actions run after InstallFinalize is finished. (Windows Installer docs for Commit Custom Actions). Therefore I figure the progress is not showing because you've made it a Commit action. Your symptom may have been useful because it raises the question, why is your CA a commit action, rather than deferred? - The purpose of commit actions is to remove any backup information that had been created by a custom action. (Installsite, http://www.installsite.org/pages/en/isnews/200108/index.htm) - That's exactly what you saw the WiX UI choose for the progress text during the commit phase, Removing Backup Files. So... would it be more appropriate for your CA to be a deferred action instead? If so, then you'll have solved your progress text too. Daryn. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Problems deploying Microsoft MSM module to SystemFolder
Can I not deploy files to System32? S:\release\cabs\product.msi.wxs(15) : warning LGHT1056 : The Directory table contains a row with primary key(s) 'SystemFolder' which cannot be merged from the merge module 'S:\build\msm\comcat.msm'. This is likely due to collision of rows with the same primary key(s) (but other different values in other columns) between the database and the merge module. Directory Id=TARGETDIR Directory Id=SystemFolder Merge DiskId=1 Id=comcat_mod Language=1033 SourceFile=S:\build\msm\comcat.msm / . . . . /Directory /Directory Feature Id=ThirdPartyComponents Title=Supporting Files Level=1 MergeRef Id=comcat_mod / . . . /Feature - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] CreateDatabase failed when User attribute is specified.
Hi, I have following User and SqlDatabase defined in WIX 3.0: Product Id=test ... util:User Id=SQLUser Domain=[SQLDOMAIN] Name=[SQLUSER] Password=[SQLPASSWORD] / ... Component ... CreateFolder / sql:SqlDatabase Id=SQLDB Server=[SQLSERVER] Database=[SQLDATABASE] CreateOnInstall=yes ConfirmOverwrite=yes DropOnUninstall=no User=SQLUser /sql:SqlDatabase /Component ... --- When I run the install it fails with the following logged ERROR message: MSI (s) (40:08) [18:13:55:027]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSIFF.tmp, Entrypoint: CreateDatabaseCreateDatabase: Error 0x80004005: failed to check if database exists: 'TestDatabase', error: unknown errorMSI (c) (48:68) [18:13:55:566]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg Error 26201. Error -2147467259: failed to create SQL database: TestDatabase, error detail: unknown error. --- - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Failed to get group 'STUONBBOX5DOM/Administrators'
Hi, We are facing a issue. Actually our MSI occasionally fails when it tries to add a user to the Administrators group. It is not able to find out Administrators group itself ???.This is a random behavior. It has been observed that the problem happens more often when virtual 1-box is being used Instead of physical 1-box. The MSI is installed using the Administrator login and the machine is a domain controller named (STUONBBOX5DOM).The OCSDumpUser is the Domain user of STUONBBOX5DOM. The following is the log that is being generated which is of interest MSI (s) (D8:24) [00:54:45:062]: Executing op: ActionStart(Name=CreateUser,,) MSI (s) (D8:24) [00:54:45:062]: Executing op: CustomActionSchedule(Action=CreateUser,ActionType=11265,Source=BinaryData,Target=**,CustomActionData=**) MSI (s) (D8:24) [00:54:45:062]: Creating MSIHANDLE (138) of type 790536 for thread 1572 MSI (s) (D8:A8) [00:54:45:062]: Invoking remote custom action. DLL: D:\WINDOWS\Installer\MSIE7.tmp, Entrypoint: CreateUser MSI (s) (D8:80) [00:54:45:062]: Generating random cookie. MSI (s) (D8:80) [00:54:45:062]: Created Custom Action Server with PID 2984 (0xBA8). MSI (s) (D8:64) [00:54:45:078]: Running as a service. MSI (s) (D8:64) [00:54:45:078]: Hello, I'm your 32bit Elevated custom action server. MSI (s) (D8!78) [00:55:06:828]: Creating MSIHANDLE (139) of type 790531 for thread 4728 CreateUser: Error 0x80004005: Failed to get group 'STUONBBOX5DOM/Administrators'. MSI (s) (D8!78) [00:55:06:828]: Closing MSIHANDLE (139) of type 790531 for thread 4728 MSI (s) (D8!78) [00:55:06:828]: Creating MSIHANDLE (140) of type 790531 for thread 4728 CreateUser: Error 0x80004005: failed to add user: OCSDumpUser to group Administrators The following is the lines in the wxs file that does the needful. Group Id='AdministratorsGroup' Domain='[PCFDUMPTOOLDOMAIN]' Name='Administrators' / : : : User Id='PCFDumpUser' Name='[PCFDUMPTOOLACCOUNT]' Domain='[PCFDUMPTOOLDOMAIN]' CreateUser='yes' UpdateIfExists='yes' RemoveOnUninstall='no' Password='[PCFDUMPTOOLPASSWORD]' GroupRef Id='AdministratorsGroup' / /User Please give me some pointers on how the problem can be debugged. Regards Bikash - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
