Re: [WiX-users] Testing Framework
Deployment Tools Foundation (DTF) which ships with WiX provides APIs for working with MSIs (among other things) and querying machine state. From: Kyle Huey [ksh...@ufl.edu] Sent: Wednesday, January 13, 2010 7:17 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Testing Framework http://msdn.microsoft.com/en-us/library/aa369554%28VS.85%29.aspx On Wed, Jan 13, 2010 at 12:05 PM, Andrew Faust afa...@microsoft.com wrote: Is there an existing framework for creating automated tests for installers built with WiX? Thanks, Andrew Faust -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Angle brackets as property value
You can do it in the inner text of a Property element as CDATA, eg: Property Id=MyPropertyAngle Brackets: ![CDATA[]]/Property From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Roger Yen Sent: Monday, April 14, 2008 1:32 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Angle brackets as property value Hi, I got a REALLY short question, is there any way to assign angle brackets as property/string values? Thanks, Roger Yen - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] format of wix project suppress specific warnings text box
Hmm, this looks like a warning from VS doing XML schema validation, not from WiX. So you're right, there's no warning number and thus it can't be suppressed. I don't know how to turn this off though :( FWIW I don't think you will get these warnings if you build outside of VS. Is there a problem that these warnings are causing you or do you just want to be clean? From: Robert O'Brien Sent: Friday, April 11, 2008 1:58 PM To: Jordan Fitzgibbon; 'wix-users@lists.sourceforge.net' Subject: RE: [WiX-users] format of wix project suppress specific warnings text box Agreed that would be preferred versus the numbering game I'm currently playing. Looking at the 13 warnings I'm getting for the same issue none of them have a wix specific warning numberunless I'm overlooking it, e.g. Warning 9 The 'Win64' attribute is invalid - The value '$(var.Win64)' is invalid according to its datatype 'http://schemas.microsoft.com/wix/2006/wi:YesNoType' - The '$' character, hexadecimal value 0x24, cannot be included in a name. From: Jordan Fitzgibbon Sent: Friday, April 11, 2008 1:51 PM To: Robert O'Brien; 'wix-users@lists.sourceforge.net' Subject: RE: [WiX-users] format of wix project suppress specific warnings text box You actually want to use the WiX warning number in the SuppressWarnings field/element, not the number that is used in the VS Errors window. Most WiX warnings and errors have a unique number. Eg: warning LGHT1079: The cabinet 'WixProject1.cab' does not contain any files. If this installation contains no files, this warning can likely be safely ignored. Otherwise, please add files to the cabinet or remove it. The error number is 1079 for the example above. This information is printed in the Output window when building in VS. You should look at the output window to determine the warning number for the warnings that you want to suppress and then add them to the SuppressSpecificWarnings1079/SuppressSpecificWarnings field. From: Robert O'Brien Sent: Friday, April 11, 2008 12:57 PM To: Jordan Fitzgibbon; 'wix-users@lists.sourceforge.net' Subject: RE: [WiX-users] format of wix project suppress specific warnings text box Fyi - I ended up with three additional warnings showing up which were getting numbered as 1, 2 and 3. I tried adding 11;12;13 to my SuppressSpecificWarnings element, e.g. 1;2;3;4;5;6;7;8;9;10;11;12;13, but that didn't help. I added 1;2;3;4;5;6;7;8;9;10;1;2;3; and that did so it seems the warning numbers cycle once you suppress existing ones and suppressing the new ones involves starting at 1 again.. From: Robert O'Brien Sent: Thursday, April 10, 2008 8:24 PM To: Jordan Fitzgibbon; 'wix-users@lists.sourceforge.net' Subject: RE: [WiX-users] format of wix project suppress specific warnings text box Thanks. Adding SuppressSpecificWarnings1;2;3;4;5;6;7;8;9;10/SuppressSpecificWarnings to the project did the trick. From: Jordan Fitzgibbon Sent: Thursday, April 10, 2008 6:14 PM To: Robert O'Brien; 'wix-users@lists.sourceforge.net' Subject: RE: [WiX-users] format of wix project suppress specific warnings text box The format is supposed to be: warning number(;warning number)* In your case, just put 9 in the text box. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert O'Brien Sent: Thursday, April 10, 2008 6:01 PM To: 'wix-users@lists.sourceforge.net' Subject: [WiX-users] format of wix project suppress specific warnings text box What is the format of of the wix project suppress specific warnings text box, e.g. I'd like to enter something there that suppresses the following warning that my sources are generating which as I understand it relates to a known bug that will cause this warning not to occur in some future build. Warning 9 The 'Win64' attribute is invalid - The value '$(var.Win64)' is invalid according to its datatype 'http://schemas.microsoft.com/wix/2006/wi:YesNoType' - The '$' character, hexadecimal value 0x24, cannot be included in a name. /tia - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] format of wix project suppress specific warnings text box
The format is supposed to be: warning number(;warning number)* In your case, just put 9 in the text box. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert O'Brien Sent: Thursday, April 10, 2008 6:01 PM To: 'wix-users@lists.sourceforge.net' Subject: [WiX-users] format of wix project suppress specific warnings text box What is the format of of the wix project suppress specific warnings text box, e.g. I'd like to enter something there that suppresses the following warning that my sources are generating which as I understand it relates to a known bug that will cause this warning not to occur in some future build. Warning 9 The 'Win64' attribute is invalid - The value '$(var.Win64)' is invalid according to its datatype 'http://schemas.microsoft.com/wix/2006/wi:YesNoType' - The '$' character, hexadecimal value 0x24, cannot be included in a name. /tia - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Reverse engineered VS2003 MSI
What errors did you get when you tried to build your MSI *with* the 3 CAs listed below? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Butcher Sent: Tuesday, April 08, 2008 9:13 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Reverse engineered VS2003 MSI Hi guys I've run DARK on a VS2003 MSI for a Web Service. Using the WXS generated I've built a new MSI using CANDLE and LIGHT. On first attempt it didn't work. I discovered that it would work when I removed the following three lines and then massaged the InstallExecutionSequence to cope with their disappearance. CustomAction Id=WEBCA_GatherWebFolderProperties Return=check BinaryKey=MSVBDPCADLL DllEntry=GatherWebFolderProperties / CustomAction Id=WEBCA_ApplyWebFolderProperties Return=check Execute=commit BinaryKey=MSVBDPCADLL DllEntry=ApplyWebFolderProperties / CustomAction Id=WEBCA_RollbackApplyWebFolderProperties Return=check Execute=rollback BinaryKey=MSVBDPCADLL DllEntry=RollbackApplyWebFolderProperties / Build the MSI - it installs ok. However... It does not set the default document for the web application. The custom table entry appears to be correct; CustomTable Id=_IISProperties Column Id=Directory_ Type=string Width=72 PrimaryKey=yes / Column Id=Attributes Type=int Width=2 / Column Id=DefaultDoc Nullable=yes Type=string Width=255 / Row Data Column=Directory_![CDATA[TARGETDIR]]/Data Data Column=Attributes![CDATA[594]]/Data Data Column=DefaultDoc![CDATA[MyWebService.asmx]]/Data /Row /CustomTable CustomTable Id=_VDirToUrl ... /CustomTable CustomTable Id=_UrlToDir ... /CustomTable CustomTable Id=_AppRootCreate .. /CustomTable CustomTable Id=_VsdLaunchCondition ... /CustomTable But it just won't set. I could understand how the removal of the 3 custom actions above might be causing this. But to be honest, unless I remove them, the MSI won't run successfully. I've read lots of mini-guides explaining to use WebSite, WebVirtualDir and WebApplication. But they are all for WXS scripts started from scratch. I'm trying to modify this VS2003 MSI so that I can preserve the basic UI it already has in place. Does anyone else have any experience of building customised WIX scripts based on WXS extracted by DARK from VS2003 MSI's? Krs Chris Disclaimer of IDOX Group plc (IDOX) This e-mail and any attachments are confidential, may be privileged and are intended solely for the use of the intended recipient/s. If you are not an intended recipient, please (a) notify the sender immediately, copying [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] as appropriate; and (b) delete the original e-mail and your reply from your system. Unless authorized by IDOX, copying, forwarding, disclosing or using this e-mail is prohibited. No liability is accepted for damage caused by the presence of any virus. The contents of this e-mail are provided subject to contract. Views or opinions in this e-mail are those of the author and not necessarily those of IDOX . IDOX may intercept, copy or monitor e-mails from or to anyone using its facilities in accordance with the law. - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Register now and save $200. Hurry, offer ends at 11:59 p.m., Monday, April 7! Use priority code J8TLD2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] case-insensitive comparison in include file
According to wix.chm, comparisons are case-sensitive. You'll have to use 'Or', eg. ?if $(env.BLD_ARCH)=X86 Or $(env.BLD_ARCH)=x86? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stas Klyachkovsky Sent: Monday, March 31, 2008 12:53 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] case-insensitive comparison in include file Hi, I have the following line in wxi file: ?if $(env.BLD_ARCH)=X86 ? How can I make this comparison case-insensitive? Thanks, Stas - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Inbuilt variable for identifying preprocessor
I'm not sure how Buildtracker works but I can see a few solutions (in priority order). 1. The ideal way is to use Candle's -platform switch which sets the preproc system variable sys.PLATFORM. So you would do something like: -Package Platform=$(sys.PLATFORM) / -Then call candle.exe product.wxs -platform [x86|x64|ia64] Unfortunately, there is a bug in candle that won't let you do this right now :) You can keep an eye on it to see when it gets fixed: http://sourceforge.net/tracker/index.php?func=detailaid=1928162group_id=105970atid=642714 2. A second option is to set a preprocessor variable on the command line call to candle -Package Platform=$(var.PLATFORM) / -candle.exe product.wxs -dPLATFORM=[intel|x64|intel64] 3. Lastly you can use an environment variable -Package Platform=$(env.PLATFORM) / -set the environment variable %PLATFORM% to [intel|x64|intel64] -candle.exe product.wxs Hope that helps. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WiXButterfly Sent: Thursday, March 27, 2008 5:57 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Inbuilt variable for identifying preprocessor Hello I need to set the 'Platforms' attribute on the 'Package' element to be x64 or otherwise depending on the arguments supplied while building the wxs. Is there an in-built variable in Wix that will help me determine that? Builds are generated for both the x86 and x64 platforms by Buildtracker, so I need to be able to set the Platforms element based on the arguments supplied by Buildtracker to build each of them. If an in-built variable is not available, I guess a pre-processor variable will need to be supplied, but what is the way to do that in an automated build and deployment process? Thanks, Sameeksha -- View this message in context: http://www.nabble.com/Inbuilt-variable-for-identifying-preprocessor-tp16343593p16343593.html Sent from the wix-users mailing list archive at Nabble.com. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] how does preprocessor suppose to work
The syntax for ifdef is ?ifdef MyVariable?, not ?ifdef $(var.MyVariable)?. So, it would appear that ifdef only checks for preprocessor variables and not environment variables. Even if you had ?ifdef $(env.PATH)? or any other existing environment variable, the ifdef wouldn't be working as you'd expect it to. Your other approach, ?if $(env._BuildArch)!=null? won't work because the preprocessor doesn't know about 'null' (that's what ifdef is for). I don't think it would be unreasonable to log a feature request on sourceforge to have an undefined environment variable resolve to an empty string instead of a compiler error. A possible solution for you would be evaluate _BuildArch on the command line and pass it as a preprocessor variable to candle. 1. You'll want to use a command line like: Candle.exe source.wxs -out out.wixobj -dBuildArchVar=%_BuildArch% 2. And sse authoring similar to this: ?if $(var.BuildArchVar)=x86? ?define _X86_ = yes? ?endif? If %_BuildArch% is defined in your environment, it will be resolved before it gets passed to candle. If it is not defined in your environment, it will get resolved to the string %_BuildArch% which is fine because the ?if? won't evaluate to true. Hope this helps. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of zhisheng huang Sent: Monday, March 24, 2008 2:38 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] how does preprocessor suppose to work Hi, When environment variable _BuildArch is not defined. The following code fails with Undefined preprocessor variable '$(env._BuildArch)'. ?ifdef $(env._BuildArch)? ?warning You should not see this? ?if $(env._BuildArch) != null and $(env._BuildArch) = x86 ? ?define _X86_ = yes? ?endif? ?endif? Actually I think I should use if $(env._BuildArch) != null for the first statement. But I got Undefined preprocessor variable '$(env._BuildArch)' for that too. The warning text You should not see this is NOT displayed, which means the the first statement is evaluated false. Then why is the ?if? inside that ?ifdef is evaluated? How can I check if an environment variable is defined or not? I am using Wix 3.0. Thanks for any comment or suggestion! Zhisheng Test your Star IQ Play now!http://club.live.com/red_carpet_reveal.aspx?icid=redcarpet_HMTAGMAR - 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] Pyro and .mst File
Can you elaborate a bit more on what UI elements you would like to change? Is that the purpose of creating your patch? Or is it to patch an existing product? To answer your question on how to use Pyro, Peter Marcu has some blog entries on how to build an MSP with WiX. You could start here: http://blogs.msdn.com/pmarcu/archive/2007/04/27/building-a-patch-using-wix-v3-0.aspx The two mst files you are seeing in the patch are transforms. One mst describes the changes that will be made to the targeted product and the other has information about how to install the patch. The cabs likely contain new files that will patch over the existing files on the targeted product. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Murray Sent: Friday, March 21, 2008 3:56 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Pyro and .mst File Hey everyone, I was looking through the WiX Help (wix.chm) and found a nifty diagram called the WiX Toolset Interaction Diagram (under About WiX | Tools and Concepts). In the diagram it shows you can take a .mst transform file and convert it into a .msp patch installer using the Pyro utility. Can anyone tell me how this is done and what command line parameters you would use? To give some background, I have created an MSI installer using VS 2008 and now I need to patch the installation. So I updated the source and rebuilt another updated MSI installer. Then I used the MSIMSP.exe utility in the Windows SDK Toolkit to create an .msp patch installer. It is functional, but I would like to modify some UI elements of this automatically created .msp file. I found some neat Windows Installer db editor called appEditor from http://www.camwood.com/. I loaded up the auto-generated .msp file and it pulled out the .mst transform file. Then I it told me to select the base transform, so I assumed it meant the original version of the .msi installer. When it came up, I was able to look at the dialog screens and it looks like I will be able to edit some of the strings and other UI elements. So anyway, now I'm thinking I will be able to save the modified .mst file and somehow get it back into the .msp file. I will keep looking around the Camwood application for a way to reconstitute the .msp, but I am wondering if there is an alternate way using the Pyro utility. I have the .mst file (for some reason there is a targetToupgrade.mst and a #targetToupgrade.mst) and then there are 7 .cab files (with their filenames being a bunch of square characters for some reason). Will the Pyro utility work for me at all? Thank you in advance. Mike - 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] Location of SourceDir?
You probably want to use the File/@Source attribute. This tells Light where to pick up your file when it's building the MSI. The file will still get installed to c:\Program Files\RRHome\RRFoo because your component is nested under that directory structure. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ken MacDonald Sent: Thursday, March 20, 2008 11:07 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Location of SourceDir? Hi all, I'm real new at MSI and WiX. I've created a Votive/ Visual Studio project 'wixfoo' - currently there's only a single file in the WiX, macdok.foo, and it should be installed on a target system at c:\program files\RR Landscapes\RRfoo\macdok.foo. I've tried placing the .foo file in a ..\RR Landscapes\RRfoo\ subdirectory in a variety of places including c:\auth\wixfoo\RR Landscapes\RRfoo\ c:\auth\wixfoo\wixfoo\RR Landscapes\RRfoo\ c:\auth\wixfoo\wixfoo\bin\RR Landscapes\RRfoo\ c:\auth\wixfoo\wixfoo\bin\Debug\RR Landscapes\RRfoo\ but always get the error: C:\auth\wixfoo\wixfoo\Product.wxs(14) : error LGHT0100 : File of type 'File' with name 'SourceDir\RR Landscapes\RRfoo\macdok.foo' could not be found. I've looked at the documentation (the getting started page is blank?!?) and the online tutorial, and all I found that seemed relevant was that the source directory tree should be the same as the target - does this mean I must put my .foo file in my build system's c:\Program Files\... etc? Any clues as to how to do this appreciated. Ken Here's most of my .wxs: = Media Id=1 Cabinet=Product.cab EmbedCab=yes / Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFilesFolder Directory Id=RRhome LongName=RR Landscapes Name=RRhome Directory Id=INSTALLLOCATION Name=RRfoo Component Id=SoftFooWare Guid=SOMEGUID-7bb3-4ab2-aa54-da09c5e8be4f File Id=macdok.foo Name=macdok.foo Vital=yes KeyPath=yes DiskId=1 / /Component /Directory /Directory /Directory /Directory - 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] wix and the preprocessor...
I would suggest logging a bug on this. I think that this type of XML validation shouldn't happen until after pre-processing. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, March 19, 2008 11:12 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] wix and the preprocessor... My guess would be that the intention was that wix input files should be valid xml. In your case, the initial file wasn't (even though the effective file, after post-processing, would have been). Personally, I wouldn't consider that a defect, more a case of that's how it works. :) Regards, Richard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeremy Breiding Sent: Wednesday, March 19, 2008 12:33 PM To: Foster, Richard - PAL Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] wix and the preprocessor... such a simple solution and it worked, thanks for pointing that out! as far as using multiple files, my intention is to go away from that. i am making heavy use of the preprocessor so i can reuse components making them slightly different based on the variables set. thanks again. should i write this up as a preprocessor defect or was the intention of the preprocessor to ever work this way? ~Jeremy Subject: RE: [WiX-users] wix and the preprocessor... Date: Wed, 19 Mar 2008 12:24:47 -0400 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: wix-users@lists.sourceforge.net Jeremy, Just for stupidity's sake, is everything OK if you reverse the order of the second test? [Remainder of history trimmed] * C O N F I D E N T I A L I T Y N O T I C E * --- The content of this e-mail is intended solely for the use of the individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited. Quixote Traffic Corporation is neither liable for the contents, nor for the proper, complete and timely transmission of (the information contained in) this communication. If you have received this communication in error, please notify the author by replying to this e-mail immediately and delete the material from any computer. - 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] How to generate a shortcut with Start In property being specified
I think you need to either set the INSTALLDIR property or have WorkingDirectory point to a Directory that you have defined. Eg. Shortcut Id=StudioDesktopShortcut Name=Demo Directory=DesktopFolder WorkingDirectory=dir Advertise=yes Icon=main.exe IconIndex=0 / From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of YungWei Chen Sent: Tuesday, February 05, 2008 6:38 PM To: WixUser Subject: [WiX-users] How to generate a shortcut with Start In property being specified Hi, I am wondering how to generate a shortcut with Start In property specified. I tried the following, but the Start In property of the generated shortcut is always empty. Do I miss anything here? Thanks. ?xml version=1.0 encoding=UTF-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://schemas.microsoft.com/wix/2006/wi C:\wix-3.0.2211.0-binaries\doc\wix.xsd Product Id=... Name=Demo Language=1033 Version=1.0.0.0 Manufacturer=m UpgradeCode=... Package Description=This is a demo Comments=Demo InstallerVersion=200 Compressed=yes/ Media Id=1 Cabinet=product.cab EmbedCab=yes/ Directory Id='TARGETDIR' Name='SourceDir' Directory Id='ProgramFilesFolder' Name='PFiles' Directory Id=Demo Name=Demo1 Directory Id=dir Name=Demo2 Component Id=MainExecutable Guid=... File Id=main_exe Name=main.exe DiskId=1 Source=main.exe Vital=yes Shortcut Id=StudioDesktopShortcut Name=Demo Directory=DesktopFolder WorkingDirectory=INSTALLDIR Advertise=yes Icon=main.exe IconIndex=0 / /File File Id=main_exe_config Name=main.exe.config DiskId=1 Source=main.exe.config Vital=yes/ /Component /Directory Directory Id=DesktopFolder Name=Desktop//Directory /Directory /Directory Feature Id=Complete Level=1 ComponentRef Id=MainExecutable/ /Feature Icon Id=main.exe SourceFile=main.exe / /Product /Wix Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.http://us.rd.yahoo.com/evt=51733/*http:/mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ%20 - 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
