[WiX-users] issue with a condition
Hi: In an install I am writing I have the following property: On my machine this parent key exists but the default key of type res_sz is not set to anything. I then have the following in my On my machine the product is installed, but I keop being told it isn't installed. Anyone spot the issue, as I'm stumpte, and other than using a custom action I carn't see the way forward-the installer has a number of properties like this! Any help appreciated. Sean. -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] avoiding GUID decoration in merge module property name
Property/@SuppressModularization documentation says: SuppressModularization YesNoType Use to suppress modularization of this property identifier in merge modules. Using this functionality is strongly discouraged; it should only be necessary as a workaround of last resort in rare scenarios. On Mon, Nov 15, 2010 at 6:09 PM, Alan Sinclair wrote: > I need to set a property "MYSPECIALDATA" in a merge module, but the > property name cannot have a guid appended because MYSPECIALDATA is read > later by the consuming MSI (which doesn't know guids). > > Is there any way this can be done in WiX 3? I'd like to use a type 51 > custom action to set the property, but can't get an undecorated property > name; it doesn't seem to make a difference whether the property name is > defined outside of the custom action or not. > > I'd hate to have to script up removing the guid after the merge module is > compiled! > > thanks > Alan > > > > -- > Beautiful is writing same markup. Internet Explorer 9 supports > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. > Spend less time writing and rewriting code and more time creating great > experiences on the web. Be a part of the beta today > http://p.sf.net/sfu/msIE9-sfdev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] avoiding GUID decoration in merge module property name
I need to set a property "MYSPECIALDATA" in a merge module, but the property name cannot have a guid appended because MYSPECIALDATA is read later by the consuming MSI (which doesn't know guids). Is there any way this can be done in WiX 3? I'd like to use a type 51 custom action to set the property, but can't get an undecorated property name; it doesn't seem to make a difference whether the property name is defined outside of the custom action or not. I'd hate to have to script up removing the guid after the merge module is compiled! thanks Alan -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] $(env.ProgramFiles) is set incorrectly on non-US WinXP?
Thanks, it explains everything. Andrei > $(env.ProgramFiles) is a pre-processor variable. Candle expands the value at > compile time replacing it with the value of the environment variable of the > compilation system rather than the target system. > > [ProgramFilesFolder] is a Windows Installer property that is expanded at > install time on the target system. > > Edwin G. Castro > Software Developer - Staff > Electronic Banking Services > Fiserv > Office: 503-746-0643 > Fax: 503-617-0291 > www.fiserv.com > Please consider the environment before printing this e-mail > >> -Original Message- >> From: Andrei Korostelev [mailto:roknap...@mail.ru] >> Sent: Monday, November 15, 2010 10:54 AM >> To: wix-users@lists.sourceforge.net >> Subject: [WiX-users] $(env.ProgramFiles) is set incorrectly on non-US WinXP? >> >> I bumped into the following problem on WinXP German. >> >> The Windows environment variable %ProgramFiles% correctly points to >> "C:\Programme" (checked using "set" command). However wix expands >> $(env.ProgramFiles) as "C:\Program Files" i.o. "C:\Programme" >> >> Replacing $(env.ProgramFiles) with [ProgramFilesFolder] fixes the issue, but >> I >> am wondering about the problem roots. Do I miss something? >> >> The issue is reproducible on wix-2.0.5805 and wix-3.0.5419.0, WinXP SP1 and >> SP3 German (32-bit). >> >> Regards, >> Andrei >> >> -- >> Centralized Desktop Delivery: Dell and VMware Reference Architecture >> Simplifying enterprise desktop deployment and management using Dell >> EqualLogic storage and VMware View: A highly scalable, end-to-end client >> virtualization framework. Read more! >> http://p.sf.net/sfu/dell-eql-dev2dev >> ___ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users > -- > Centralized Desktop Delivery: Dell and VMware Reference Architecture > Simplifying enterprise desktop deployment and management using > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end > client virtualization framework. Read more! > http://p.sf.net/sfu/dell-eql-dev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] $(env.ProgramFiles) is set incorrectly on non-US WinXP?
Thanks, Blair, Very clear explanation. Build machine is US with regular "C:\Program Files" of course The question closed Adrei > Generally speaking, $(env.ProgramFiles) captures the value of the > environment variable %ProgramFiles% on the BUILD machine, and > [ProgramFilesFolder] provides the 32-bit Program Files folder on the > INSTALLING machine (runtime, so to speak). The two variables really have > nothing to do with each other since they relate to different machines and > are evaluated at different times. > > Here's the rule: If the value of a path will be evaluated as part of the > build (such as: in the Source* attribute of some element) use WiX's > $(type.name) [or even !(type.name)] syntax. If the value of a path must be > evaluated at runtime (since "common" paths such as Program Files varies with > localized OSs and other customizations) use Windows Installer's > [PropertyOrDirectoryName] syntax. > > Did you really get "C:\Program Files" on a German WinXP build machine that > you ran the candle.exe tool on? > > -Original Message- > From: Andrei Korostelev [mailto:roknap...@mail.ru] > Sent: Monday, November 15, 2010 10:54 AM > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] $(env.ProgramFiles) is set incorrectly on non-US WinXP? > > I bumped into the following problem on WinXP German. > > The Windows environment variable %ProgramFiles% correctly points to > "C:\Programme" (checked using "set" command). However wix expands > $(env.ProgramFiles) as "C:\Program Files" i.o. "C:\Programme" > > Replacing $(env.ProgramFiles) with [ProgramFilesFolder] fixes the issue, > but I am wondering about the problem roots. Do I miss something? > > The issue is reproducible on wix-2.0.5805 and wix-3.0.5419.0, WinXP SP1 > and SP3 German (32-bit). > > Regards, > Andrei > > > -- > Centralized Desktop Delivery: Dell and VMware Reference Architecture > Simplifying enterprise desktop deployment and management using > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end > client virtualization framework. Read more! > http://p.sf.net/sfu/dell-eql-dev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > -- > Centralized Desktop Delivery: Dell and VMware Reference Architecture > Simplifying enterprise desktop deployment and management using > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end > client virtualization framework. Read more! > http://p.sf.net/sfu/dell-eql-dev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Creating virtual directories to UNC shares
How do I set a pre-defined directory to be configured to use a UNC share? Note that I want my web site to be installed to a local path, but I want the virtual directories under my web site to point to a network path. I tried also using a mapped network drive, but I get a validation error. This is what I tried to do: These are the error details: c:\enlistments\pinmain\private\dev\Deployment\EktronUpdate\setup\EktronUpdate.wxs(17): error CNDL0027: The Directory/@Name attribute's value, 'X:\UploadedFiles', is not a valid long name because it contains illegal characters. Legal long names contain no more than 260 characters and must contain at least one non-period character. Any character except for the follow may be used: \ ? | > < : / * ". c:\enlistments\pinmain\private\dev\Deployment\EktronUpdate\setup\EktronUpdate.wxs(17): error CNDL0205: The Directory with Id 'UPLOADEDFILES_FOLDER' is not a valid root directory. There may only be a single root directory per product or module and its Id attribute value must be 'TARGETDIR' and its Name attribute value must be 'SourceDir'. Done Building Project "c:\enlistments\pinmain\private\dev\Deployment\EktronUpdate\setup\wixmsi_EktronUpdate.wixproj" (BuildLinked target(s)) -- FAILED. Error : [Project] c:\enlistments\pinmain\private\dev\Deployment\EktronUpdate\setup\wixmsi_EktronUpdate.wixproj Done Building Project "c:\enlistments\pinmain\private\dev\Deployment\EktronUpdate\setup\wixmsi_EktronUpdate.wixproj" (default targets) -- FAILED. -Original Message- From: Blair [mailto:os...@live.com] Sent: Monday, November 15, 2010 12:34 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Creating virtual directories to UNC shares The FileSource attribute to the Directory element provides a hint to the toolset where to find the files that you place in components that are installed to that directory. Its value is not preserved in the MSI anywhere and thus is only available at build time, not at runtime. The directory tree doesn't automatically have any directories using UNC shares unless one of the pre-defined directories was somehow configured to use a UNC share. If you need your web site to use a UNC share instead of an install-local path, you need to set the directory's value to that path yourself at an appropriate place in your installation sequence. -Original Message- From: Johanna Hawkins (ORTIZ) [mailto:johan...@microsoft.com] Sent: Monday, November 15, 2010 9:20 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Creating virtual directories to UNC shares I need to create a virtual directory within my application that points to a UNC share in another machine. Is this supported or should I use a custom action for this? I tried this but it didn't work, the virtual directory got created to the local path, not the UNC share: -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] XmlConfig's dependency on MSXML
I've gotten spoiled in using .NET / Linq-to-XML. In an unmanaged world, what else would you suggest WiX use? (Seriously, I don't know the alternatives anymore.) I think I recall InstallShield has the same dependency. If there is no other choice, perhaps you could author an AppSearch and LaunchCondition to abort the install for these machines and let the user know they have a problem. Or bring msxml along for the ride via bootstrapper and try to fix it for them first. Christopher Painter, Author of Deployment Engineering Blog Have a hot tip, know a secret or read a really good thread that deserves attention? E-Mail Me - Original Message From: Jeff Buda To: wix-users@lists.sourceforge.net Sent: Mon, November 15, 2010 2:09:53 PM Subject: [WiX-users] XmlConfig's dependency on MSXML Is there any chance that the XmlConfig Wix-provided custom action will be reimplemented without the use of MSXML? We started using XmlConfig in my product's most recent release, and based on customer feedback, XmlConfig's use of / dependency on MSXML has turned our product's installer into an "invalid MSXML installation detector" of sorts. Apparently, XmlConfig tries to load MSXML, which is improperly registered on some customers' machines, and then XmlConfig fails, as does our entire installation package. It seems to be a someone common problem, as there is a similar-sounding issue affecting MS Office 2010 installer. See http://social.technet.microsoft.com/Forums/en/officesetupdeploy/thread/86787c69-5909-4885-843e-b8b977e5cc33 -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Creating virtual directories to UNC shares
The FileSource attribute to the Directory element provides a hint to the toolset where to find the files that you place in components that are installed to that directory. Its value is not preserved in the MSI anywhere and thus is only available at build time, not at runtime. The directory tree doesn't automatically have any directories using UNC shares unless one of the pre-defined directories was somehow configured to use a UNC share. If you need your web site to use a UNC share instead of an install-local path, you need to set the directory's value to that path yourself at an appropriate place in your installation sequence. -Original Message- From: Johanna Hawkins (ORTIZ) [mailto:johan...@microsoft.com] Sent: Monday, November 15, 2010 9:20 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Creating virtual directories to UNC shares I need to create a virtual directory within my application that points to a UNC share in another machine. Is this supported or should I use a custom action for this? I tried this but it didn't work, the virtual directory got created to the local path, not the UNC share: -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] $(env.ProgramFiles) is set incorrectly on non-US WinXP?
Generally speaking, $(env.ProgramFiles) captures the value of the environment variable %ProgramFiles% on the BUILD machine, and [ProgramFilesFolder] provides the 32-bit Program Files folder on the INSTALLING machine (runtime, so to speak). The two variables really have nothing to do with each other since they relate to different machines and are evaluated at different times. Here's the rule: If the value of a path will be evaluated as part of the build (such as: in the Source* attribute of some element) use WiX's $(type.name) [or even !(type.name)] syntax. If the value of a path must be evaluated at runtime (since "common" paths such as Program Files varies with localized OSs and other customizations) use Windows Installer's [PropertyOrDirectoryName] syntax. Did you really get "C:\Program Files" on a German WinXP build machine that you ran the candle.exe tool on? -Original Message- From: Andrei Korostelev [mailto:roknap...@mail.ru] Sent: Monday, November 15, 2010 10:54 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] $(env.ProgramFiles) is set incorrectly on non-US WinXP? I bumped into the following problem on WinXP German. The Windows environment variable %ProgramFiles% correctly points to "C:\Programme" (checked using "set" command). However wix expands $(env.ProgramFiles) as "C:\Program Files" i.o. "C:\Programme" Replacing $(env.ProgramFiles) with [ProgramFilesFolder] fixes the issue, but I am wondering about the problem roots. Do I miss something? The issue is reproducible on wix-2.0.5805 and wix-3.0.5419.0, WinXP SP1 and SP3 German (32-bit). Regards, Andrei -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] $(env.ProgramFiles) is set incorrectly on non-US WinXP?
$(env.ProgramFiles) is a pre-processor variable. Candle expands the value at compile time replacing it with the value of the environment variable of the compilation system rather than the target system. [ProgramFilesFolder] is a Windows Installer property that is expanded at install time on the target system. Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail > -Original Message- > From: Andrei Korostelev [mailto:roknap...@mail.ru] > Sent: Monday, November 15, 2010 10:54 AM > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] $(env.ProgramFiles) is set incorrectly on non-US WinXP? > > I bumped into the following problem on WinXP German. > > The Windows environment variable %ProgramFiles% correctly points to > "C:\Programme" (checked using "set" command). However wix expands > $(env.ProgramFiles) as "C:\Program Files" i.o. "C:\Programme" > > Replacing $(env.ProgramFiles) with [ProgramFilesFolder] fixes the issue, but I > am wondering about the problem roots. Do I miss something? > > The issue is reproducible on wix-2.0.5805 and wix-3.0.5419.0, WinXP SP1 and > SP3 German (32-bit). > > Regards, > Andrei > > -- > Centralized Desktop Delivery: Dell and VMware Reference Architecture > Simplifying enterprise desktop deployment and management using Dell > EqualLogic storage and VMware View: A highly scalable, end-to-end client > virtualization framework. Read more! > http://p.sf.net/sfu/dell-eql-dev2dev > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] XmlConfig's dependency on MSXML
Is there any chance that the XmlConfig Wix-provided custom action will be reimplemented without the use of MSXML? We started using XmlConfig in my product's most recent release, and based on customer feedback, XmlConfig's use of / dependency on MSXML has turned our product's installer into an "invalid MSXML installation detector" of sorts. Apparently, XmlConfig tries to load MSXML, which is improperly registered on some customers' machines, and then XmlConfig fails, as does our entire installation package. It seems to be a someone common problem, as there is a similar-sounding issue affecting MS Office 2010 installer. See http://social.technet.microsoft.com/Forums/en/officesetupdeploy/thread/86787c69-5909-4885-843e-b8b977e5cc33 -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] $(env.ProgramFiles) is set incorrectly on non-US WinXP?
I bumped into the following problem on WinXP German. The Windows environment variable %ProgramFiles% correctly points to "C:\Programme" (checked using "set" command). However wix expands $(env.ProgramFiles) as "C:\Program Files" i.o. "C:\Programme" Replacing $(env.ProgramFiles) with [ProgramFilesFolder] fixes the issue, but I am wondering about the problem roots. Do I miss something? The issue is reproducible on wix-2.0.5805 and wix-3.0.5419.0, WinXP SP1 and SP3 German (32-bit). Regards, Andrei -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Creating virtual directories to UNC shares
I need to create a virtual directory within my application that points to a UNC share in another machine. Is this supported or should I use a custom action for this? I tried this but it didn't work, the virtual directory got created to the local path, not the UNC share: -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] CloseApplication issue
Message was shown when I used WiX 3.5. I try to compile msi with WiX 3.6 and there was no message! Hurray!!! So on WiX 3.6 there is no problem! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/CloseApplication-issue-tp5731506p5739838.html Sent from the wix-users mailing list archive at Nabble.com. -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WIXUI_INSTALLDIR and remembered properties
It doesn't as far as I know unless you store the it in ARPINSTALLLOCATION. You can't use that method for any other properties. If you're not explicitly putting it in there then you're likely seeing the same default path being generated whenever you run your MSI. If you want to store & retrieve your own properties you'll need to write code to do it manually. Rob M. wrote a blog on how to do exactly that http://robmensching.com/blog/posts/2010/5/2/The-WiX-toolsets-Remember-Pr operty-pattern Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -Original Message- From: Alex McCool [mailto:amcc...@pcts.com] Sent: 12 November 2010 17:30 To: wix-users@lists.sourceforge.net Subject: [WiX-users] WIXUI_INSTALLDIR and remembered properties How does WIXUI_INSTALLDIR remember where it was installed to? Is there any way I can add my own properties to that storage mechanism? Alex -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
