Re: [WiX-users] Upgrade (options?)
Currently I have constructed a custom dialog to prompt the user for the settings required for the installation. If this is an upgrade then I will have saved those settings in the registry and I obviously don't want to prompt the user/installer for those settings again. How do I bypass this dialog on an upgrade? Thank you. Kevin -Original Message- From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 12, 2008 11:25 PM To: [EMAIL PROTECTED] Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Upgrade (options?) [EMAIL PROTECTED] wrote: The question that comes up is after this conditional block and there is a major upgrade, when should the settings that are saved in the registry be read in? Is there a conditional clause on saving that setting in the registry that I am missing? No. Just always do it: If the product is being installed for the first time, there won't be any registry values found. During an initial install or an upgrade, you want the registry values written back out. How do I read these settings in an bypass the dialog prompt that is part of the normal installation (UI and UIREF)? Which dialog prompt? As I understand it a property 'NEWERFOUND' will be set if a newer version is detected (major upgrade). Right? Yes, if you have an UpgradeVersion element with Property=NEWERFOUND with the right versions. Gabor covers that at http://www.tramontana.co.hu/wix/lesson4.php. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. 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] heat.exe -scom produces incorrect regasm fragments for COM interop ?
What version of WiX are you using? The RegistryHarvester should be
handling empty leaf keys, but it may not have always been this way.
Looking at RegistrationServices (the class that both WiX and regasm.exe
use to register assemblies) Implemented Categories seems to be the
only empty key.
Jantzen, Andrej wrote:
Hello,
I tried to use heat.exe
heat.exe file -scom MyDotNetCOM.dll -out MyDotNetCOM.wxs
to generate a WiX fragment equivalent to the command
regasm MyDotNetCOM.dll /tlb
and noted that compared with execution of regasm command some things are
missing/suspect:
- the key HKCR\CLSID\{--SomeClassUUID--}\Implemented
Categories\{62C8FE65-4EBB-45E7-B440-6E39B2CDBF29}
is missing for all coclasses in my DLL (this entry marks coclasses
implemented by .NET assemblies)
- but the key
RegistryValue Root=HKCR Key=Component
Categories\{62C8FE65-4EBB-45e7-B440-6E39B2CDBF29} Name=0 Value=.NET
Category Type=string Action=write /
is created, although, in my opinion, this is a global key managed by the
.NET framework.
Is this behavour correct?
Regards,
Andrej Jantzen
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
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
--
Heath Stewart
Deployment Technology Group, Microsoft
http://blogs.msdn.com/heaths
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
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] Need help to check if a file exists in the installation folder
Path should be a directory. Use INSTALLDIR without brackets (which is a property). You don't need a custom action. Justin Zhen Tu wrote: Hi there, I am having problem with my WIX installer and I wonder if there anyone can help me out. The problem is I need to check if this file “localappsetting.config” exists in the installation folder, copy a new file if it doesn’t exist otherwise ignore. Below is my code and it does work: Property Id=FILEEXISTS DirectorySearch Id=CheckFileDir Path=[INSTALLDIR] Depth=0 FileSearch Id=CheckFile Name=LocalAppSettings.config / /DirectorySearch /Property Feature Id='LocalAppSettingsTemplate' Level='1' ComponentRef Id='C_LocalAppSettings' / Condition Level=0FILEEXISTS/Condition /Feature I have read a post here said I need to schedule a Custom Action and I wonder if someone can point me an example on how to do it. Many thanks. Jusitn - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. 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 -- Heath Stewart Deployment Technology Group, Microsoft http://blogs.msdn.com/heaths - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. 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] Design recommendations and best practice
One thing to consider is making it granular such that if you later patch you can patch more granular resources. If you refer to one Component, for example, everything in that fragment is pulled in. So put each component in a separate fragment. Group custom actions and their binary (if binary CAs) into separate fragments. Even put the ProductVersion property in a separate fragment so that you can use author a patch family to update the ProductVersion or not (constituting a minor upgrade patch if ProductVersion changes). Stas Klyachkovsky wrote: Hi there, I’ve decompiled my IS MSI and now I have one big .wxs file, which I want to fragment. Before I start, I want to gather WiX design best practice. Could somebody share or recommend any resources? Thanks, Stas - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. 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 -- Heath Stewart Deployment Technology Group, Microsoft http://blogs.msdn.com/heaths - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. 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] adding WixUIExtension produces Error HRESULT E_FAIL has been returned from a call to a COM component. when reopening solution
I've just installed the latest wix3.msi on XP SP2 with VS2008 rtm and am getting the same error on attempting to open a solution containing a WiX project. The project is then marked as unavailable in the IDE. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert O'Brien Sent: 13 March 2008 04:25 To: wix-users@lists.sourceforge.net Subject: [WiX-users] adding WixUIExtension produces Error HRESULT E_FAIL has been returned from a call to a COM component. when reopening solution After adding the following entry to my wix setup project using the votive vs08 project extensions support everything works fine. ItemGroup WixExtension Include=WixUIExtension HintPathC:\Program Files (x86)\Windows Installer XML v3\bin\WixUIExtension.dll/HintPath /WixExtension /ItemGroup Later when I close and try to reopen the project I get the following error which I can only resolve by removing the above entry Error HRESULT E_FAIL has been returned from a call to a COM component. I'm running on a clean vista sp1 x64 setup with vs08 rtm in place and latest wix3.msi installed. Is this a known issue? +++ Virus-scanned by MailControl for Oxford Instruments +++ ___ThThis e-mail is confidential and is for the addressee only. Please refer to www.oxinst.com/email-statement for regulatory information. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. 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] MultiPart Installer
You can condition your WiX source based on properties to pass into candle.exe. But because the product composition would be different, you should use different ProductCodes. This is important if you intend to patch the product later, as you don't want a single, all-inclusive patch to add everything back in if you don't want it, and there would otherwise be no other way to target a specific product with a specific patch - all traits that patch transform target would be exactly the same. Using different ProductCodes also avoids Windows Installer picking the wrong MSI out of the Installer cache and using that instead of the actual source MSI (if installing two different compositions on the same machine). nils_gate wrote: I am trying to create an installer, which has 4 components. In QC Version, I want to include all the 4 components. While in Final release, I want to include 1 of 4 components based on requirement. I can acheive this using Conditional Installation of a particular feature at installation time. But, in this case I have to include all the components into Installer Database. I want to conditionally include only required component into Installer Databse. I suppose using EmbeddedChainer, I can do this. Have any one done any hands on it? Please help Me N!ls -- Heath Stewart Deployment Technology Group, Microsoft http://blogs.msdn.com/heaths - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. 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] heat.exe -scom produces incorrect regasm fragments for COM interop ?
At least 3.0.3725.0 didn't produced Implemented Categories keys.
I've now tried the version 3.0.3829.0 - it seems to do it correctly!
Thanks,
Andrej
Heath Stewart wrote:
What version of WiX are you using? The RegistryHarvester should be
handling empty leaf keys, but it may not have always been this way.
Looking at RegistrationServices (the class that both WiX and regasm.exe
use to register assemblies) Implemented Categories seems to be the
only empty key.
Jantzen, Andrej wrote:
Hello,
I tried to use heat.exe
heat.exe file -scom MyDotNetCOM.dll -out MyDotNetCOM.wxs
to generate a WiX fragment equivalent to the command
regasm MyDotNetCOM.dll /tlb
and noted that compared with execution of regasm command some things are
missing/suspect:
- the key HKCR\CLSID\{--SomeClassUUID--}\Implemented
Categories\{62C8FE65-4EBB-45E7-B440-6E39B2CDBF29}
is missing for all coclasses in my DLL (this entry marks coclasses
implemented by .NET assemblies)
- but the key
RegistryValue Root=HKCR Key=Component
Categories\{62C8FE65-4EBB-45e7-B440-6E39B2CDBF29} Name=0 Value=.NET
Category Type=string Action=write /
is created, although, in my opinion, this is a global key managed by the
.NET framework.
Is this behavour correct?
Regards,
Andrej Jantzen
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
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] Специальное предложение - помо жет сэкономить
8 nbsp; (9O3) nbsp; 7 О 7 nbsp; 9 2 9З [EMAIL PROTECTED] ПРЕДЛОЖЕНИЕ реклама по юридическим и физическим адресам Москвы 4,63 миллиона писем или реклама по юридическим адресам Москвы и России 3,95 миллиона писем ВСЕГО 3999 РУБ.* две рассылки ВСЕГО 5500 РУБ.* три рассылки ВСЕГО 6999 РУБ.* при оплате яндекс-деньгами или веб-мани - скидка 7% !- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. 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 in entering nodes to machine.config using XmlConfig of Wix
Hi, The idea you are giving is not working because if u specify an Id as an ElementPath then you cannot use the Node=element attribute of XmlConfig. So any thing that is created is by using the method you mentioned is getting formed as an attribute rather than being formed as an element. In case I am getting you wrong in this please correct me and if you can could you please send me a code snippet of what you meant. Thanks and Regards, Abhradeep Guha Thakurta From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Thursday, March 13, 2008 9:37 AM To: Abhradeep Thakurta Cc: Laxmi Narsimha Rao Oruganti (SQL CE); WiX-users Subject: Re: [WiX-users] Problem in entering nodes to machine.config using XmlConfig of Wix Please keep wix-users on the list so everyone can participate. Abhradeep Thakurta wrote: In such a situation we should enter the new node inside the empty dependentAssembly . Now my major problem is how do I define the XPath for such a situation. You don't. If you use the Id of the dependentAssembly XmlConfig as the ElementPath of another XmlConfig, the XmlConfig custom action uses that newly-created node as the parent. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. 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] Get Target machine name
Hi, This is probably an easy answer for someone but I need to know how to get the Target machine name (Domain) during installation? It looks like I need this when trying to add the App Pool user to the IIS_WPG group. Thanks in advance. Tris _ Get Hotmail on your mobile, text MSN to 63463! http://mobile.uk.msn.com/pc/mail.aspx- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. 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] Get Target machine name
For the machine name, use the ComputerName property. I will let someone else answer the Domain question, but so far it appears that there is no obvious way. From: Tris Hodges Sent: Thursday, March 13, 2008 2:39 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Get Target machine name Hi, This is probably an easy answer for someone but I need to know how to get the Target machine name (Domain) during installation? It looks like I need this when trying to add the App Pool user to the IIS_WPG group. Thanks in advance. Tris Think you know your TV, music and film? Try Search Charades! - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. 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 2008. 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] Get Target machine name
Thanks for the reply, I assume you meant like the following.. $(sys.COMPUTERNAME)? I believe this is set at compilation and thus gives me the build machine name. What I am after is the machine name on which the installer is being run? As IIS_WPG is a local group this will enable me to add the machine name into the domain field of the Group element. Unless of course there is a better way to achieve this? From: [EMAIL PROTECTED]: [EMAIL PROTECTED]; [EMAIL PROTECTED]: Re: [WiX-users] Get Target machine nameDate: Thu, 13 Mar 2008 15:08:35 +0100 For the machine name, use the ComputerName property. I will let someone else answer the Domain question, but so far it appears that there is no obvious way. From: Tris Hodges Sent: Thursday, March 13, 2008 2:39 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Get Target machine name Hi, This is probably an easy answer for someone but I need to know how to get the Target machine name (Domain) during installation? It looks like I need this when trying to add the App Pool user to the IIS_WPG group. Thanks in advance. Tris Think you know your TV, music and film? Try Search Charades! -This SF.net email is sponsored by: MicrosoftDefy all challenges. Microsoft(R) Visual Studio 2008.http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___WiX-users mailing [EMAIL PROTECTED]://lists.sourceforge.net/lists/listinfo/wix-users _ Share what Santa brought you https://www.mycooluncool.com- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. 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] Multiple installs of same product/service
Hello. We have a need for a service we develop (Windows Service) to be installed side-by-side multiple times on a single computer, differing by installation path and configuration file(connection string, log path etc). I've developed a WIX Installer that does the custom installation part just fine, but ofcourse I'm hitting a snag when I want to install another service of the same type, with the same installation program. MSI thinks(knows) that the product is already installed, and just gives the option to uninstall. What I'd like is for the installer to accept multiple installs of the same product but to different paths. Is there a way to achieve this? Some sort of GUID auto generation? Here's the wxs file for reference (our company name has been replace with OurCompany and the application we're integrating with with this service has been replaced with ExternalApplication). ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:util=http://schemas.microsoft.com/wix/UtilExtension; Product Id=ccebbaed-ba86-4942-a93c-5939f5baca16 Name=OurCompany ExternalApplication Integration Service Language=1033 Version=1.2.0.0 Manufacturer=OurCompany AS UpgradeCode=e883a4fe-b855-4856-b2d5-d9993a6b6809 Package InstallerVersion=200 Compressed=yes InstallPrivileges=elevated / Media Id=1 Cabinet= OurCompany.Integration.ExternalApplication.WIXInstaller.cab EmbedCab=yes / Directory Id=TARGETDIR Name=SourceDir Component Id=ServiceComponent Guid=c12f647b-67f0-4b95-87c5-86ef9ff85b30 Location=local File Id=ExternalApplicationServiceEXE Name=OurCompany.Integration.ExternalApplication.exe Source=../../OurCompany.Integration.ExternalApplication/bin/$(var.BUILD )/OurCompany.Integration.ExternalApplication.Exe / File Id=ELCommonDLL Name=Microsoft.Practices.EnterpriseLibrary.Common.dll Source=../../OurCompany.Integration.ExternalApplication/bin/$(var.BUILD )/Microsoft.Practices.EnterpriseLibrary.Common.dll / File Id=ELLoggingDLL Name=Microsoft.Practices.EnterpriseLibrary.Logging.dll Source=../../OurCompany.Integration.ExternalApplication/bin/$(var.BUILD )/Microsoft.Practices.EnterpriseLibrary.Logging.dll / File Id=ELObjectBuilderDLL Name=Microsoft.Practices.ObjectBuilder.dll Source=../../OurCompany.Integration.ExternalApplication/bin/$(var.BUILD )/Microsoft.Practices.ObjectBuilder.dll / File Id=CONFIGBase Name=OurCompany.Integration.ExternalApplication.exe.config Source=../../OurCompany.Integration.ExternalApplication/bin/$(var.BUILD )/OurCompany.Integration.ExternalApplication.Exe.config / util:XmlConfig Id=AddDSN Action=create ElementPath=//configuration/connectionStrings File=[TARGETDIR]\OurCompany.Integration.ExternalApplication.exe.config Name=add Node=element On=install Sequence=1/ util:XmlConfig Id=AddDSNKey File=[TARGETDIR]\OurCompany.Integration.ExternalApplication.exe.config ElementPath=AddDSN Name=name Value=OdbcConnectionString Sequence=2 / util:XmlConfig Id=AddDSNValue File=[TARGETDIR]\OurCompany.Integration.ExternalApplication.exe.config ElementPath=AddDSN Name=connectionString Value=DSN=[ODBCDSN]; Sequence=3 / ServiceInstall Id=ExternalApplicationServiceEXE Name=ExternalApplicationService_[ODBCDSN] DisplayName=OurCompany ExternalApplication Service [ODBCDSN] Type=ownProcess Interactive=yes Start=auto Vital=yes ErrorControl=normal / ServiceControl Id=ExternalApplicationServiceEXE Name=ExternalApplicationService_[ODBCDSN] Stop=uninstall Remove=uninstall Wait=yes / /Component /Directory Feature Id=ServiceFeature Title= OurCompany.Integration.ExternalApplication.WIXInstaller Level=1 ComponentRef Id=ServiceComponent / /Feature UIRef Id=WixUI_Common/ UI !--Begin Stock stuff -- Property Id=DefaultUIFont Value=WixUI_Font_Normal / TextStyle Id=WixUI_Font_Normal FaceName=Tahoma Size=8 / TextStyle Id=WixUI_Font_Bigger FaceName=Tahoma Size=12 / TextStyle Id=WixUI_Font_Title FaceName=Tahoma Size=9 Bold=yes / Property Id=WIXUI_INSTALLDIR Value=TARGETDIR / Property Id=ARPNOMODIFY Value=1 / DialogRef Id=BrowseDlg / DialogRef Id=DiskCostDlg / DialogRef Id=ErrorDlg / DialogRef Id=FatalError / DialogRef Id=FilesInUse / DialogRef Id=MsiRMFilesInUse / DialogRef Id=PrepareDlg /
Re: [WiX-users] Upgrade (options?)
Kevin Burton wrote: Currently I have constructed a custom dialog to prompt the user for the settings required for the installation. If this is an upgrade then I will have saved those settings in the registry and I obviously don't want to prompt the user/installer for those settings again. How do I bypass this dialog on an upgrade? How are you showing this dialog? If you're using InstallUISequence, then you can add a condition to the Show element using any of the properties (i.e., NOT PROPERTYNAME to show the dialog if the value wasn't found). If you're using a control event, put the condition in the Publish element. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. 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] Multiple installs of same product/service
Henning Kilset wrote: MSI thinks(knows) that the product is already installed, and just gives the option to uninstall. What I'd like is for the installer to accept multiple installs of the same product but to different paths. Is there a way to achieve this? Some sort of GUID auto generation? MSI supports this via instance transforms, which are natively supported by WiX via the InstanceTransforms element. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. 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] adding WixUIExtension produces Error HRESULT E_FAIL has been returned from a call to a COM component. when reopening solution
RAYMENT Tim wrote: I've just installed the latest wix3.msi on XP SP2 with VS2008 rtm and am getting the same error on attempting to open a solution containing a WiX project. The project is then marked as unavailable in the IDE. *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *On Behalf Of *Robert O'Brien *Sent:* 13 March 2008 04:25 *To:* wix-users@lists.sourceforge.net *Subject:* [WiX-users] adding WixUIExtension produces Error HRESULT E_FAIL has been returned from a call to a COM component. when reopening solution After adding the following entry to my wix setup project using the votive vs08 project extensions support everything works fine. ItemGroup WixExtension Include=WixUIExtension HintPathC:\Program Files (x86)\Windows Installer XML v3\bin\WixUIExtension.dll/HintPath /WixExtension /ItemGroup Later when I close and try to reopen the project I get the following error which I can only resolve by removing the above entry Error HRESULT E_FAIL has been returned from a call to a COM component. Can either of you build your projects from the command line or is this specific to use inside Visual Studio? In either case, please enter a bug so the folks working on Votive have the details of the problem. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. 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 in entering nodes to machine.config using XmlConfig of Wix
Abhradeep Thakurta wrote: The idea you are giving is not working because if u specify an Id as an ElementPath then you cannot use the Node=element attribute of XmlConfig. Yes, that's true. Sorry, I misread the code. That said, it would be a fairly easy change to support child elements: The code already tracks the newly-created element to support adding attributes to it. You could also use the XPath support in recent builds of WiX to use the last() selector in ElementPath. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. 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] ICE79 feature based conditions
Hello, I have a feature with the ID f_20_Programs and want test if this feature is installed. So I've a condition for one custom action in the InstallUISequence after CostFinalize with the following content: Custom Action=MyAction Sequence=1203![CDATA[!f_20_Programs=3]]/Custom My Feature is defined as follows: Feature Id=f_20_Programs Title=Programme Description=sisNET Suite Programme Level=3 Absent=allow AllowAdvertise=no ConfigurableDirectory=SISNETPATH ... ... /Feature I'm using WIX 3.0.3815.0. When I build my project I receive the following ICE79 error: ICE79: Feature 'f_20_Programs' referenced in column 'InstallUISequence'.'Condition' of row 'MyAction' is invalid. When I run the setup the condition is evaluated to True if the feature is installed and to False if the feature is not installed. But why comes this ICE79 error? Can anybody help me? What's wrong? Matthias - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. 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 set Title in Summary Information Stream
Hi all, I'm using WiX 2.0.5325.0 and have the following question: Is it possible to set the Title attribute in the msi Summary Information Stream? So far I have not found a way to do this. It works fine with the Subject, Author, Keywords and Comments. But when I open the summary information of a msi/msm created with WiX 2.0.5325.0 Title is always set to Installation Database. The Package tag does not seem to offer this... Regards, ACKH -- View this message in context: http://www.nabble.com/How-to-set-Title-in-Summary-Information-Stream-tp16030521p16030521.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 2008. 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] Problem with iis:WebDir ...
Hi,
Does anybody have a good working example of using the iis:WebDir
element?
I'm using WiX 3.0.3907.0 with the following illustrated example:
Fragment
DirectoryRef Id="INSTALLDIR" Component Id="MyWeb" Guid="{...}" CreateFolder/ !-- To avoid ICE018 errors
--
iis:WebDir Id="MyWebDir" Path="Dir/SubDir" WebSite="DefaultWebSite" iis:WebDirProperties Id="MyWebDirProps" AnonymousAccess="yes"/ /iis:WebDir /Component
/Directory
iis:WebSite Id="DefaultWebSite" Description="Default Web Site" iis:WebAddress Id="AllUnassigned" Port="80"/ /iis:WebSite /FragmentBut it does not work as expected. I would expect that a "C:\Inetpup\wwwroot\Dir\SubDir" folder were created (but I'm not sure that I've specified the @Path attribute
correct).
What is the difference (advantage/disadvantage) between using iis:WebDir elementto using plain Directory
elements?
Thanks in advance for all replies,
/Michael
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
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] Get Target machine name
[EMAIL PROTECTED] wrote: For the machine name, use the ComputerName property. Tris Hodges wrote: I assume you meant like the following.. $(sys.COMPUTERNAME)? I believe this is set at compilation [ ] No, Calin meant the Windows Installer property ComputerName, see the Windows Installer Property Reference, http://msdn2.microsoft.com/en-us/library/aa370905(VS.85).aspx For domain name, I'm pretty sure it needs a custom action, e.g. your own C++ DLL. Or, a quick search shows that Matthew Rowan posted a simple VBScript custom action to do it to this list previously: http://www.nabble.com/domain-name-to9381200.html#a9381200 ... and InstallSite has a CA DLL that provides it as well: http://www.installsite.org/pages/en/isp_svc.htm Daryn. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. 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] Get Target machine name
If you run install by user logged in as domain user you can just reference environment variable like this [%USERDOMAIN] in MSI/WiX. But if that user is logged in locally then USERDOMAIN holds just a computer name. Thursday, March 13, 2008, 12:43:52 PM, you wrote: [EMAIL PROTECTED] wrote: For the machine name, use the ComputerName property. Tris Hodges wrote: I assume you meant like the following.. $(sys.COMPUTERNAME)? I believe this is set at compilation [ ] No, Calin meant the Windows Installer property ComputerName, see the Windows Installer Property Reference, http://msdn2.microsoft.com/en-us/library/aa370905(VS.85).aspx For domain name, I'm pretty sure it needs a custom action, e.g. your own C++ DLL. Or, a quick search shows that Matthew Rowan posted a simple VBScript custom action to do it to this list previously: http://www.nabble.com/domain-name-to9381200.html#a9381200 ... and InstallSite has a CA DLL that provides it as well: http://www.installsite.org/pages/en/isp_svc.htm Daryn. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. 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 -- Best regards, Alexei Boukirev == The ability to destroy a mainframe is insignificant next to the power of The Source. - Darth Archtitect - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. 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] Silent Mode installation without command line option...
Is there any way to install MSI in silent mode without using command line option.. msiexec /q .msi Thanks!! - Never miss a thing. Make Yahoo your homepage.- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. 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] Help with Wix...UI to select Installation Drive.
Hello I need some guidance in getting my Wix script, to let users select the installation drive only. I experimented with WixUI_InstallDir, but this one allows users to select the complete path/directory and not just the drive. My requirement is to give the option only to select the installation drive [C: or D: for example], and not the path/Directory. Thanks for your help, Arun Kumar [EMAIL PROTECTED] - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. 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
