[WiX-users] IIS Web Address problem
I'm trying to get my IIS site to only listen on the IP address that I'm providing. When I use the following snippet of WiX code, though, I get two addresses in the IIS site properties, and the one that is selected for it to listen on is 'All Unassigned'. How do I replace All Unassigned with my IP address/hostname combo? iis:WebSite Id=PartnerXSite Directory=mainDirectory WebLog=DefaultLogging Description=PartnerX Web Site AutoStart=yes DirProperties=SoapWebProperties ConfigureIfExists=yes iis:WebAddress Id=PartnerXAddrId IP=[PartnerX.IPAddress] Header=$(var.PartnerXHeader) Port=80 / iis:WebApplication Id=PartnerXWebApp Isolation=high WebAppPool=PartnerXPool Name=PartnerX Web Site / /iis:WebSite - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How do i embedd and install a 3rd party msi (eg directx or wse runtime) if not already installed
Create a bootstrapper. Check out msdn documentation on the msbuild GenerateBootstrapper task. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gareth at Serif Sent: Thursday, March 29, 2007 10:23 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How do i embedd and install a 3rd party msi (eg directx or wse runtime) if not already installed I regularly install DirectX as part of my WiX packages, here's the code for a file I just include for the functionality to 'appear': ?xml version='1.0' encoding=utf-8? Include xmlns='http://schemas.microsoft.com/wix/2003/01/wi' Feature Id=DirectX9 Title=DirectX9 Level=100 Description=DirectX9 AllowAdvertise=no Display=hidden ComponentRef Id=DirectX9 / /Feature Property Id=DirectXDllDirectX9\dsetup.dll/Property Property Id=InstallDXNo/Property CustomAction Id=SetInstallDX Property=InstallDX Value=Yes / CustomAction Id=MsiInstDX BinaryKey=MsiCustomActions DllEntry=MsiInstDX Impersonate=yes / CustomAction Id=MsiInstDXProp Property=MsiInstDXDeferred Value=[UILevel];[SourceDir][DirectXDll] Impersonate=yes / CustomAction Id=MsiInstDXDeferred BinaryKey=MsiCustomActions DllEntry=MsiInstDX Execute=deferred Impersonate=yes / InstallExecuteSequence Custom Action=SetInstallDX After=LaunchConditions(NOT Installed) AND ((DXMajorVersion lt; 4) OR (DXMajorVersion = 4 AND DXMinorVersion lt; 9))/Custom Custom Action=MsiInstDX After=InstallInitialize(NOT Installed) AND (InstallDX = Yes)/Custom Custom Action=MsiInstDXProp After=MsiInstDX(NOT Installed) AND (InstallDX = Yes)/Custom Custom Action=MsiInstDXDeferred After=MsiInstDXProp(NOT Installed) AND (InstallDX = Yes)/Custom /InstallExecuteSequence InstallUISequence Custom Action=SetInstallDX After=LaunchConditions(NOT Installed) AND ((DXMajorVersion lt; 4) OR (DXMajorVersion = 4 AND DXMinorVersion lt; 9))/Custom Custom Action='SetRebootRequired' After='SetInstallDX'(NOT Installed) AND (InstallDX = Yes)/Custom /InstallUISequence DirectoryRef Id=TARGETDIR Directory Id=DirectX9 Name=DirectX9 src=Installs\Common\DirectX9c Component Id=DirectX9 Guid=80A814B2-E059-4A83-9533-C9A9A694C869 DiskId=1 File Id=DX9BDA.cab Name=BDA.cab Compressed=no / File Id=DX9BDANT.cab Name=BDANT.cab Compressed=no / File Id=DX9BDAXP.cab Name=BDAXP.cab Compressed=no / File Id=DX9DirectX.cab Name=DirectX.cab Compressed=no / File Id=DX9dsetup32.dll Name=dsetup32.dll Compressed=no / File Id=DX9DSETUP.dll Name=DSETUP.dll Compressed=no / File Id=DX9dxnt.cab Name=dxnt.cab Compressed=no / File Id=DX9DXSETUP.exe Name=DXSETUP.exe Compressed=no / File Id=DX9ManagedDX.CAB Name=ManagdDX.CAB LongName=ManagedDX.CAB Compressed=no / /Component /Directory /DirectoryRef /Include AS for other MSIs (Adobe Reader, for example) so long as there's only one to install, you can call the MSI in a deferred custom action that'll launch after your own installation had finished - I've done that a few times with great success too. Good luck, Gareth -- View this message in context: http://www.nabble.com/How-do-i-embedd-and-install-a-3rd-party-msi-%28eg-directx-or-wse-runtime%29-if-not-already-installed-tf3469351.html#a9738492 Sent from the wix-users mailing list archive at Nabble.com. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] multiple file compilation
I have a bunch of one-file installers (one .wxs file per installer, many installers). Can I run candle once, with *.wxs, then run light separately on each wixobj? Will there be any problems doing this? Cullen Waters SDET Microsoft Office Live - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] multiple file compilation
Thanks, Rob From: Rob Mensching Sent: Tuesday, March 20, 2007 3:31 PM To: Rob Mensching; Cullen Waters; WiX-users@lists.sourceforge.net Subject: RE: Re: [WiX-users] multiple file compilation Sorry, that's terribly ambiguous. Yes, you can run candle once with all the .wxs files then link many times. No, there will not be any problems. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Tuesday, March 20, 2007 3:29 PM To: Cullen Waters; WiX-users@lists.sourceforge.net Subject: Re: [WiX-users] multiple file compilation No. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cullen Waters Sent: Tuesday, March 20, 2007 2:16 PM To: WiX-users@lists.sourceforge.net Subject: [WiX-users] multiple file compilation I have a bunch of one-file installers (one .wxs file per installer, many installers). Can I run candle once, with *.wxs, then run light separately on each wixobj? Will there be any problems doing this? Cullen Waters SDET Microsoft Office Live - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ?Bug? in linker
That's not the behavior I'm seeing. I saved the wixlib files, so you can see the paths that are in there. The wixlib and the file it references are both built to the same directory, but the wixlib contains the path from the .wxs source file to the binary reference. Since we build to a 'Target' directory, that path is invalid when the wixlib is compiled. From: Rob Mensching Sent: Tuesday, February 13, 2007 10:26 AM To: Cullen Waters; WiX-users@lists.sourceforge.net Subject: RE: [WiX-users] ?Bug? in linker No, .wixlibs are designed to be portable. There was actually a bug a long time ago that absolute paths were preserved in the .wixlib. Thus the .wixlibs were looking for the server CustomAction files in the location we built them on the build server. That's obviously bad. What should actually be happening is that files referenced by the .wixlib should be relative to the location of the .wixlib (wherever that might be). That way you can move around the .wixlibs and their referenced files together (the way we used to move sca.wixlib, scasched.dll and scaexec.dll together). From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cullen Waters Sent: Tuesday, February 13, 2007 10:05 AM To: WiX-users@lists.sourceforge.net Subject: [WiX-users] ?Bug? in linker In my application, we have several wixlibs that we use to wrap functionality for Custom Actions. Recently, we changed the way we were building these slightly, and it broke our build. Previously, we were relying on a particular environment variable to be set, in order for the build to work. This environment variable was the full path to the root of our source control tree, and is different on each machine. We've been moving to Votive, and in doing so, have been removing the dependency on environment variables from our wix source (so we can build in VS). I changed the paths of the files to relative paths. Candle compiled the wixobj file fine, and lit created the wixlib that I expected. When I try to link an MSI that uses this wixlib, though, I get an error that a file with a relative path couldn't be found. I went to the directory where the wixlib was compiled and linked from, and pasted in the path that couldn't be found. It was there, just as expected. Eventually, I realized that light seemed to be resolving the path from the directory where the MSI was linking from, not the directory where the wxs file for the wixlib resided. This seemed strange, since light has the directory of the source file. I think this is a bug, and I think that Lit should be changed to resolve all relative paths to absolute paths when it builds the wixlib file. What do others think? Cullen Waters SDET Office Live +1 425 706 6809 x 66809 - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ?Bug? in linker
We've found a workaround for now, so it's not a critical issue for us, but something that probably should be fixed. From: Rob Mensching Sent: Tuesday, February 13, 2007 10:37 AM To: Cullen Waters; WiX-users@lists.sourceforge.net Subject: RE: [WiX-users] ?Bug? in linker That sounds like the bug I remember. Maybe it hasn't been fixed yet. I have not been in to the WiX v3 Binder in a long time... focused on finishing WiX v2. From: Cullen Waters Sent: Tuesday, February 13, 2007 10:28 AM To: Rob Mensching; WiX-users@lists.sourceforge.net Subject: RE: [WiX-users] ?Bug? in linker That's not the behavior I'm seeing. I saved the wixlib files, so you can see the paths that are in there. The wixlib and the file it references are both built to the same directory, but the wixlib contains the path from the .wxs source file to the binary reference. Since we build to a 'Target' directory, that path is invalid when the wixlib is compiled. From: Rob Mensching Sent: Tuesday, February 13, 2007 10:26 AM To: Cullen Waters; WiX-users@lists.sourceforge.net Subject: RE: [WiX-users] ?Bug? in linker No, .wixlibs are designed to be portable. There was actually a bug a long time ago that absolute paths were preserved in the .wixlib. Thus the .wixlibs were looking for the server CustomAction files in the location we built them on the build server. That's obviously bad. What should actually be happening is that files referenced by the .wixlib should be relative to the location of the .wixlib (wherever that might be). That way you can move around the .wixlibs and their referenced files together (the way we used to move sca.wixlib, scasched.dll and scaexec.dll together). From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cullen Waters Sent: Tuesday, February 13, 2007 10:05 AM To: WiX-users@lists.sourceforge.net Subject: [WiX-users] ?Bug? in linker In my application, we have several wixlibs that we use to wrap functionality for Custom Actions. Recently, we changed the way we were building these slightly, and it broke our build. Previously, we were relying on a particular environment variable to be set, in order for the build to work. This environment variable was the full path to the root of our source control tree, and is different on each machine. We've been moving to Votive, and in doing so, have been removing the dependency on environment variables from our wix source (so we can build in VS). I changed the paths of the files to relative paths. Candle compiled the wixobj file fine, and lit created the wixlib that I expected. When I try to link an MSI that uses this wixlib, though, I get an error that a file with a relative path couldn't be found. I went to the directory where the wixlib was compiled and linked from, and pasted in the path that couldn't be found. It was there, just as expected. Eventually, I realized that light seemed to be resolving the path from the directory where the MSI was linking from, not the directory where the wxs file for the wixlib resided. This seemed strange, since light has the directory of the source file. I think this is a bug, and I think that Lit should be changed to resolve all relative paths to absolute paths when it builds the wixlib file. What do others think? Cullen Waters SDET Office Live +1 425 706 6809 x 66809 - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Votive - Adding File as a Link
When I did this, I still got the ugly folders. From: Justin Rockwood [mailto:[EMAIL PROTECTED] Sent: Thursday, February 08, 2007 12:51 PM To: Cullen Waters; Justin Rockwood; 'Mark Capaldi'; WiX-users@lists.sourceforge.net Subject: RE: [WiX-users] Votive - Adding File as a Link Another thing you can try, which is the way it's supposed to officially work, is this: ItemGroup Compile Include=..\..\..\FileName.cs LinkFileName.cs/Link /Compile /ItemGroup I can't remember if this works in Votive or not. I think it does, though. Try it out and let me know. Justin From: Cullen Waters [mailto:[EMAIL PROTECTED] Sent: Thursday, February 08, 2007 12:47 PM To: Justin Rockwood; 'Mark Capaldi'; WiX-users@lists.sourceforge.net Subject: RE: [WiX-users] Votive - Adding File as a Link If you edit the project file directly, you can do this. In the ItemGroup Compile Include=my file.wxs / /ItemGroup Section, just add another entry like this: Compile Include=PathToFileMySecondFIle.wxs/ Now, there is a catch. When you reload the project in VS, it's going to be ugly. VS will add a Folder tag for each folder in the relative path from your project directory to the file. And it adds one folder entry for each level of folder. For instance, I have a file that is two directories up from my project file. So, when I open the project in VS, I have an empty folder for .., an empty folder for ..\.., and a folder that is for ..\..\, but has the item in it. Not pretty, but it works. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Rockwood Sent: Thursday, February 08, 2007 12:28 PM To: 'Mark Capaldi'; WiX-users@lists.sourceforge.net Subject: Re: [WiX-users] Votive - Adding File as a Link It's one of the things on my list to do, but linked files do not currently work yet. Sorry about that. Justin From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Capaldi Sent: Thursday, February 08, 2007 6:10 AM To: WiX-users@lists.sourceforge.net Subject: [WiX-users] Votive - Adding File as a Link Hi, I'm playing around with Votive v3.0.2211.0 in Visual Studio 2005 Team Edition for Software Developers. I would like to add an existing item into my WiX project as a link, but the dialog box doesn't have the drop down box on the Add button like other projects. I can only Add files, which means that the file is physically copied into the project folder on the file system Is there any way to add files to a Votive projects as a link? Regards, Mark Capaldi - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Votive - Adding File as a Link
If you edit the project file directly, you can do this. In the ItemGroup Compile Include=my file.wxs / /ItemGroup Section, just add another entry like this: Compile Include=PathToFileMySecondFIle.wxs/ Now, there is a catch. When you reload the project in VS, it's going to be ugly. VS will add a Folder tag for each folder in the relative path from your project directory to the file. And it adds one folder entry for each level of folder. For instance, I have a file that is two directories up from my project file. So, when I open the project in VS, I have an empty folder for .., an empty folder for ..\.., and a folder that is for ..\..\, but has the item in it. Not pretty, but it works. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Justin Rockwood Sent: Thursday, February 08, 2007 12:28 PM To: 'Mark Capaldi'; WiX-users@lists.sourceforge.net Subject: Re: [WiX-users] Votive - Adding File as a Link It's one of the things on my list to do, but linked files do not currently work yet. Sorry about that. Justin From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Capaldi Sent: Thursday, February 08, 2007 6:10 AM To: WiX-users@lists.sourceforge.net Subject: [WiX-users] Votive - Adding File as a Link Hi, I'm playing around with Votive v3.0.2211.0 in Visual Studio 2005 Team Edition for Software Developers. I would like to add an existing item into my WiX project as a link, but the dialog box doesn't have the drop down box on the Add button like other projects. I can only Add files, which means that the file is physically copied into the project folder on the file system Is there any way to add files to a Votive projects as a link? Regards, Mark Capaldi - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix 3.0 and Votive?
What I did was set a property called DefineConstants in my MSBuild file. Then, when candle is executed, the WixTasks convert that semicolon separated list of variables into -dname=value when passed into the candle command line. The only thing you might have to do is change the env. prefix to var., if nant was setting an environment variable for you. From: Scott Sam [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 07, 2007 8:58 AM To: Cullen Waters; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Wix 3.0 and Votive? Thanks, I've gotten the wxs files updated, and added them to the projects in TFS. How do you handle the source path for the files being added to the msi? Before I used a nant variable in the wix as part of the path. Is there a similar way to do this using MSBuild? It looks like the path will change based on whether or not it is a debug or release build. From: Cullen Waters [mailto:[EMAIL PROTECTED] Sent: Thursday, February 01, 2007 1:54 PM To: Scott Sam; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Wix 3.0 and Votive? I just moved my whole team from v2 to v3. In general, the update went really smoothly. You can use wixcop.exe to update all of the xml for you. Wixcop doesn't, however remove shortnames, which might cause you some headaches. I went through all my xml and manually deleted all the short names. What might cause you some extra work, depending on how you use v2, is that v3 runs msi validation as part of light. We found a bunch of msival errors in our MSIs when we went to v3, and it took some time to work through them. This is a good thing, though, since you have essentially raised the quality bar of your installers by doing this. We use votive with VS Team Suite, and we haven't had any problems yet. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam Sent: Thursday, February 01, 2007 10:47 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Wix 3.0 and Votive? I was thinking of trying out votive. We are using Visual Studio Team Edition for Developers with Team Foundation Server. We are also using WIX v2 for the msi. I was wondering, is Wix v3 stable enough to use if we are deploying our next version of our product in about 3-5 months. Has anyone used votive with team foundation server? Are there any problems to be expected when moving from wix v2 to wix v3? - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix 3.0 and Votive?
Actually, for us, we use a common settings file Import Include=PathToFile\MySettings.settings / at the top of the file. In the settings file, we have DefineConstants. This element can be overridden in each project file. If you go to the property pages for a wix project, there is a button on the compiler tab for Advanced Properties, or something like that. Put your semicolon separated list in there. Alternatively, if you like to edit XML by hand, you can right click on any project (for any project type, actually), and select unload project. Once it's greyed out in solution explorer, right click again, and select Edit MyProj.wixproj. It will open in the VS main window, with the XML editor open. From: Scott Sam [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 07, 2007 11:00 AM To: Cullen Waters; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Wix 3.0 and Votive? Sorry I'm kind of new to this. Is that the msbuild file for the specific project correct? Is there a way to edit that in VS/TFS? From: Cullen Waters [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 07, 2007 1:01 PM To: Scott Sam; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Wix 3.0 and Votive? What I did was set a property called DefineConstants in my MSBuild file. Then, when candle is executed, the WixTasks convert that semicolon separated list of variables into -dname=value when passed into the candle command line. The only thing you might have to do is change the env. prefix to var., if nant was setting an environment variable for you. From: Scott Sam [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 07, 2007 8:58 AM To: Cullen Waters; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Wix 3.0 and Votive? Thanks, I've gotten the wxs files updated, and added them to the projects in TFS. How do you handle the source path for the files being added to the msi? Before I used a nant variable in the wix as part of the path. Is there a similar way to do this using MSBuild? It looks like the path will change based on whether or not it is a debug or release build. From: Cullen Waters [mailto:[EMAIL PROTECTED] Sent: Thursday, February 01, 2007 1:54 PM To: Scott Sam; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Wix 3.0 and Votive? I just moved my whole team from v2 to v3. In general, the update went really smoothly. You can use wixcop.exe to update all of the xml for you. Wixcop doesn't, however remove shortnames, which might cause you some headaches. I went through all my xml and manually deleted all the short names. What might cause you some extra work, depending on how you use v2, is that v3 runs msi validation as part of light. We found a bunch of msival errors in our MSIs when we went to v3, and it took some time to work through them. This is a good thing, though, since you have essentially raised the quality bar of your installers by doing this. We use votive with VS Team Suite, and we haven't had any problems yet. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam Sent: Thursday, February 01, 2007 10:47 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Wix 3.0 and Votive? I was thinking of trying out votive. We are using Visual Studio Team Edition for Developers with Team Foundation Server. We are also using WIX v2 for the msi. I was wondering, is Wix v3 stable enough to use if we are deploying our next version of our product in about 3-5 months. Has anyone used votive with team foundation server? Are there any problems to be expected when moving from wix v2 to wix v3? - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix 3.0 and Votive?
I just moved my whole team from v2 to v3. In general, the update went really smoothly. You can use wixcop.exe to update all of the xml for you. Wixcop doesn't, however remove shortnames, which might cause you some headaches. I went through all my xml and manually deleted all the short names. What might cause you some extra work, depending on how you use v2, is that v3 runs msi validation as part of light. We found a bunch of msival errors in our MSIs when we went to v3, and it took some time to work through them. This is a good thing, though, since you have essentially raised the quality bar of your installers by doing this. We use votive with VS Team Suite, and we haven't had any problems yet. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam Sent: Thursday, February 01, 2007 10:47 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Wix 3.0 and Votive? I was thinking of trying out votive. We are using Visual Studio Team Edition for Developers with Team Foundation Server. We are also using WIX v2 for the msi. I was wondering, is Wix v3 stable enough to use if we are deploying our next version of our product in about 3-5 months. Has anyone used votive with team foundation server? Are there any problems to be expected when moving from wix v2 to wix v3? - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Upgrading to v3 and Vista...
Two answers: 1) use quot; in your xml, that should evauluate to at runtime. 4)you have to put in ICE64, not just 64. If you look at the build output, you can see the command lines that get generated for light and candle. If you look there, you'll see that the ICE you put in that field is being passed in as /sice:64 instead of /sice:ICE64, which is what you want. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gordon Watts Sent: Sunday, January 28, 2007 12:28 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Upgrading to v3 and Vista... Hi there, First of all, Votive v3 and the error messages that come from v3 of light/etc. are fantastic. That and the mailing list archives allowed me to answer most of my questions. Kudos! A few issues/questions remain. 1) I'd like to convert the following to the new RegistryValue wix element, but I'm not sure how to deal with the double-quotes in my CDATA: Registry Action=write Id=TortCVSSHArgs Key=Software\TortoiseCVS Name=External SSH Params Type=string Root=HKLM RegistryValue![CDATA[-o StrictHostKeyChecking no -2 -l %u %h]]/RegistryValue /Registry Is there some obvious format, or a way to continue to use the CDATA specification? 2) This used to work on windows XP and v2 of WiX. I have a custom action which I schedule to run Before the InstalFinalize. This custom action (deferred) runs an executable that I've installed. When I run the installer it bombs because the file hasn't been copied to its final location. When I look at the verbose log file I see that, indeed, the FileCopy operation seems to be executed only after the InstallFinalize action is started. I want this guy to run deferred because it needs elevated privs, but if I do run it deferred then I have to run it before the InstallFinalize. I'm sensing a catch-22 here... So, what can I do to get around this? 3) In converting my wix source over to v3 I had the same problem lots of other people seem to have had with short cuts. I moved almost all my shortcuts over to be advertised. Much to my surprise, they just worked. Both in non-admin and admin worlds. Neat. We'll see if they survie deployment in a Terminal Server environment! But, there is one short cut I can't crack. This is a short cut to cmd.exe. It executes a script as an argument. So it isn't really associated with a file I install, and so (as far as I understand) can't be advertised. However, one of its command line arguments is a file that I do install. Originally that file and this shortcut were in the same component but I got the system and user profile items in same component: use registry value in HKCU as key path. There was a great email that explained to me (at least) why this should be avoided, so I moved it into a second component. Now, however..., I am getting the warning ICE69: cross component reference (bad because if a component isn't installed during upgrade the reference may evaluate to null -- that would be bad if the shortcut to cmd was made and didn't reference anything!). What is the proper method to fix this? Is there a way to advertise a shortcut like this? 4) At one point I experimented with ignoring warnings/errors in the IDE. Specifically, I wanted light to ignore ICE64 (which is an error). When I entered 64 in suppress warnings this didn't alter behavior. Is this expected behavior because this is an error? Thanks a lot in advance for any help! Cheers, Gordon. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] What happened to Tallow.exe
Heat replaced tallow in v3. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dan Hoeger Sent: Thursday, January 04, 2007 1:14 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] What happened to Tallow.exe I'm having trouble with this on Vista so I thought I would download v3.0.2420.0 and it doesn't have this exe. Without this tool what is the recommended way to extract the registration information for a DLL? Thanks, Dan - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ICE20 with WiX v3
The biggest difference, and the reason you're seeing the errors now when you didn't before, is that wix 3 runs ICE validation on the MSI that is created by light, while wix 2 didn't. Most likely, if you run ice validation on the msi you created with wix 2, you'll see the same errors. You just have to run ICE validation manually, like through Orca. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Levi Wilson Sent: Thursday, December 21, 2006 12:54 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] ICE20 with WiX v3 I receive the following errors when trying to follow along with part 8 of the tutorial when linking with version 3 (all ICE20s BTW): * Standard Dialog: 'FilesInUse' not found in Dialog table * ErrorDialog Property not specified in Property table * Exit dialog/action not found in AdminUISequence (and one about InstallUISequence * etc. Can anyone offer me any insight or point me to a website that indicates some of the differences between version 2 and 3 of the linker and why I keep running into ICExxx errors? Any help would be greatly appreciated, thanks! Levi - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] ICE20 with WiX v3
The wix team generally asks that you keep the alias on replies, so everyone can learn together. I don't know much about custom dialogs. Actually, I don't know anything. I can tell you, though, from personal experience, that moving from v2 to v3 *will* identify lots of errors that have existed in your MSIs all along, but which you didn't know about, because v2 didn't run validation. Hopefully, someone else can help you with the custom dialogs. From: Levi Wilson [mailto:[EMAIL PROTECTED] Sent: Thursday, December 21, 2006 1:25 PM To: Cullen Waters Subject: Re: [WiX-users] ICE20 with WiX v3 I guess I just don't understand why adding a single dialog to display caused all these problems for a project that previously didn't have any UI. Does adding the show/ tag in the InstallUISequence force new requirements upon the MSI? I'm just playing around with custom dialogs. Any help would be greatly appreciated. On 12/21/06, Cullen Waters [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: The biggest difference, and the reason you're seeing the errors now when you didn't before, is that wix 3 runs ICE validation on the MSI that is created by light, while wix 2 didn't. Most likely, if you run ice validation on the msi you created with wix 2, you'll see the same errors. You just have to run ICE validation manually, like through Orca. From: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED]] On Behalf Of Levi Wilson Sent: Thursday, December 21, 2006 12:54 PM To: wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge.net Subject: [WiX-users] ICE20 with WiX v3 I receive the following errors when trying to follow along with part 8 of the tutorial when linking with version 3 (all ICE20s BTW): * Standard Dialog: 'FilesInUse' not found in Dialog table * ErrorDialog Property not specified in Property table * Exit dialog/action not found in AdminUISequence (and one about InstallUISequence * etc. Can anyone offer me any insight or point me to a website that indicates some of the differences between version 2 and 3 of the linker and why I keep running into ICExxx errors? Any help would be greatly appreciated, thanks! Levi - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] IIS CustomAction not registering Cert properly (ver 3.0.2330.0)
The build of v2 we were using was really old, and this code worked on that build. Was there a known regression in the code from v2 to v3? From: Rob Mensching Sent: Thursday, December 21, 2006 2:51 PM To: Cullen Waters; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] IIS CustomAction not registering Cert properly (ver 3.0.2330.0) The cert fixes in v2 has not been ported to WiX v3 yet. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cullen Waters Sent: Thursday, December 21, 2006 13:45 To: wix-users@lists.sourceforge.net Subject: [WiX-users] IIS CustomAction not registering Cert properly (ver 3.0.2330.0) I have some wix code that is creating a web application, and assigning a cert to that web app. Everything seems to work okay, but the cert is not getting associated with the correct website. This error just started, after moving from v2 to v3. I didn't change anything in the code in question, except to run wixcop, and have the iis: appended to the elements. Component Id=component14 Guid=316CF6D6-F173-413C-9BC0-294139F10FDA iis:Certificate Id=IWSWebSiteCert StoreName=my StoreLocation=localMachine Overwrite=yes Request=yes CertificatePath=[UIWebServer.CertificateFileName] PFXPassword=[UIWEBSERVER.CERTIFICATEPASSWORD] / iis:WebSite Id=IWSWebSite Description=UI Web Site WebLog=DefaultLogging Directory=directory16 DirProperties=IWSWebSite ConfigureIfExists=yes iis:WebAddress Id=UIHostName IP=[MYIWSWEBSITEIP] Header=[IWSWEBSITEHOST] Port=80 / iis:WebAddress Id=LocalHost IP=127.0.0.1 Header=localhost Port=80 / iis:WebAddress Id=Default_Secure IP=[MYIWSWEBSITEIP] Port=443 Secure=yes / iis:WebApplication Id=IWSWebApplication Isolation=high WebAppPool=Standard Name=IWS UI Web Site iis:CertificateRef Id=IWSWebSiteCert Permissions=8 / /iis:WebApplication /iis:WebSite /Component iis:WebDirProperties Id=IWSWebSite AnonymousAccess=yes AnonymousUser=AnonymousUserAccount LogVisits=yes Script=yes Execute=yes Read=yes DefaultDocuments=default.aspx / The installer executes fine, but when I go into inetmgr, and look at the properties of the website, the certificate is not properly associated. It looks like there is a certificate there, but when you click view cert, nothing happens. If I manually replace the cert with the one in the cert store, which this msi installed, the cert shows up properly. Anyone run into this before? Cullen Waters SDET Office Live +1 425 706 6809 x 66809 - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Comparing two MSIs
I was getting errors trying to use the script you suggested, Michael. I ended up using Dark and just eyeballing through Orca, and actually found several items using both methods. Thanks everyone, for the suggestions. From: Michael Osmond [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 06, 2006 7:14 PM To: Cullen Waters; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Comparing two MSIs There's a script in the MSI SDK called WiDiffDb.vbs, I use it on occasion to do this. Michael From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peterson, Joel Sent: Thursday, 7 December 2006 9:36 AM To: Cullen Waters; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Comparing two MSIs Orca is a fair good tool and will allow you to eyeball compare the tables, not sure it has any automatic comparison feature. Joel Peterson Quality Assurance Engineer [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cullen Waters Sent: Wednesday, December 06, 2006 3:28 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Comparing two MSIs Is there a tool out there to compare two MSIs? I'm moving our MSIs to wixv3, and I want to verify that the built MSIs are the same as previously. Cullen Waters SDET Office Live +1 425 706 6809 x 66809 - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] InstallUISequence
Is there a way, in Wix V3, to prevent the InstallUISequence table from being created? I've got a couple of MSIs that don't use UI at all, but the InstallUISequence table is being created, and filled with what looks like some default actions. This is causing problems because we execute some custom actions before LaunchConditions, and then verify that the CAs worked properly in LaunchConditions. Because the InstallUISequence is being created, and populated with the default actions, LaunchConditions is being called before my CAs have a chance to run, and my install is failing. Cullen Waters SDET Office Live +1 425 706 6809 x 66809 - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] error CNDL0036: Could not find extension
If you installed wix using the wixv3 msi, then all of the extension dlls should be in the same location as candle and light. If you used the zip file, just make sure that you unzipped the extension dlls. If it's not finding it using the -ext WixUtilExtension, you can also use -ext [FullPathToFile]WixUtilExtension.dll. From: David Errick Sent: Thursday, December 07, 2006 7:39 AM To: Cullen Waters Subject: error CNDL0036: Could not find extension Dear Cullen, Is the WixUtilExtension.dll the extension specified in the -ext WixUtilExtension? If build from a different folder does an environment value need to set? I am getting this error: candle.exe : error CNDL0036: Could not find extension 'C:\sybld\private\SYBARI\setup\wix\wixv3\WixUtilExtension'. Thanks for your help. From: Cullen Waters Sent: Tuesday, December 05, 2006 3:51 PM To: David Errick; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] using ServiceConfig in wix 3.0 - uitl schema elements will not compile with candle In v3, you have to call candle with -ext WixUtilExtension to use elements from that namespace. Same with light. And, to help you abit, when you call light, you have to specify what cultures to use (like -cultures:en-us) From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Errick Sent: Tuesday, December 05, 2006 12:35 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] using ServiceConfig in wix 3.0 - uitl schema elements will not compile with candle moving form wix 2.0 to wix 3.0 - candle does not compile source with elements from the util scheam - error unexpected child element, ect. do you have an example of using the User or ServiceConfig elements? I know there will be libs to link with light - but need to get source to compile. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] error CNDL0036: Could not find extension
There are a couple of ways to get this information. You could check out the wix .chm file. That has documentation on all of the elements and attributes for all of the 'standard' extensions. If you don't like documentation, you could check out the source, it's all on sourceforge. The extension source is at wix/src/ext/ -Original Message- From: Brent B. Powers [mailto:[EMAIL PROTECTED] Sent: Thursday, December 07, 2006 10:15 AM To: Cullen Waters Subject: Re: [WiX-users] error CNDL0036: Could not find extension Cullen Waters wrote: If you installed wix using the wixv3 msi, then all of the extension dlls should be in the same location as candle and light. If you used the zip file, just make sure that you unzipped the extension dlls. If it's not finding it using the -ext WixUtilExtension, you can also use -ext [FullPathToFile]WixUtilExtension.dll. Is there a list of what is actually in the Extensions? Cheers - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] memory usage
If you make your project use multiple .wxs files, rather than a single .wxs with a bunch of .wxi (which all get added in to the main file), then candle should seem faster, and the processing would show as spikes, rather than constant usage. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of TibTam Sent: Thursday, December 07, 2006 10:35 AM To: Rob Mensching Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] memory usage We have one wxs and many xmls with include. These xmls contain the folders/files/registries. We have the UI in a different xml too. If we can manage the xml files to be smaller, that can speed up the candle? Rob Mensching wrote: Do you have just one gigantic XML file or are you splitting your product into many smaller .wxs files and letting the linker bring them back together? There is nothing special in the compiler. Normally it completes in seconds because there is very little IO. However, if you make one gigantic XML file then candle is probably spending all of its time slogging through the XmlDocument. From: TibTam [mailto:[EMAIL PROTECTED] Sent: Thursday, December 07, 2006 10:21 To: Rob Mensching Cc: wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge.net Subject: Re: [WiX-users] memory usage off topic: Sorry, i pressed Reply instaed of Reply All... on: You are right, light uses lot of memory. About 300-350 MB normally, but some said that on his machine it uses more than 500 MB. This sounds a bit strange to me, because he uses the same files and method to create the msi. Is this posibble? But out bigger problem is the CPU usage, what is made by candle.exe. Light uses about the same memory size that candle uses(bit more), but light does not use the CPU at 100% for all the time. Could you please help me to understand why candle uses the CPU at 100% for long minutes? (10-15-20 mins, depending on the machine) And what can we do to reduce this? (I mean to reduce the time while candle uses the CPU.) If i'll have time, i'll check the code for optimization, but i can't promise anything. :) Thanks Tamas Rob Mensching wrote: Please, keep the mailing list on all replies. I assume all your seeing the memory hit in the linker (light.exe), right? I haven't checked the memory usage in a while but your project is very large so that might be a very reasonable number right now. I don't think Office, VS, or SQL complain about the memory usage for their products because they probably all have at least a GB in all the machines and I'm not sure you'd immediately notice how much memory is being used. That said, if you wanted to profile the WiX toolset and found places where we could optimize our memory usage, that'd be really cool. From: TibTam [mailto:[EMAIL PROTECTED] Sent: Thursday, December 07, 2006 10:02 To: Rob Mensching Subject: Re: [WiX-users] memory usage Package Id=---- Keywords=Installer Description=Software installer Comments=Copyright mycompany Manufacturer=mycompany InstallerVersion=100 Languages=1033 Compressed=yes SummaryCodepage=1252/ Media Id=1 Cabinet=Files.cab EmbedCab=no DiskPrompt=DVD-ROM #1/ But the working scenario is the same if i set the compressed to No. (I do not know where can i check the compression level. :( ) Rob Mensching wrote: Are you compressing your files? If so, what compression level are you using? -Original Message- From: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of TibTam Sent: Thursday, December 07, 2006 09:36 To: wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge.net Subject: Re: [WiX-users] memory usage The result msi is 250MB. About 2500 files are being installed and more then 20 000 registry keys. We split the wix files into many parts. We have one wxs containing the projects and main folders, and many xmls. These xmls are included into the main wxs. Regards, Tamas Rob Mensching wrote: Uhh, maybe but you'd need to be a lot more specific about what in your project is quite big. -Original Message- From: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tamas Tiboldi Sent: Thursday, December 07, 2006 05:58 To: wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge.net Subject: [WiX-users] memory usage Hi! We have a quite big project and wix uses huge amount of memory. (more than 500 MBs) Is there any possibility to maximize the memory usage? How does the package generation works? Thanks a lot Tamas - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash
Re: [WiX-users] WIX Post-Install Dialog Questions
Chris, From the snippet you posted below, it looks like you're trying to, at install time, choose what file gets included in the MSI. That doesn't work. You have to author the MSI (call this build time) before you can try to install it. At build time, you have to supply all of the files that will be included in the MSI. I don't understand why, if the file is already installed to the file system, you would want to include it in your MSI. I don't even understand how that file would be present in your installation directory before you install. Your MSI shouldn't be installing to another program's directory, so you should be creating the directory, and then populating it. The snippet below makes it seem like after you populate the directory with your executable (from the MSI), you want to include the executable in the MSI. If you are just trying to start your app after installing, you want to look at the qt exec custom action, I think. That should let you put in a path to a file, and execute that file. You'll just have to schedule the CA after your install is complete. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, December 07, 2006 4:46 PM To: Rob Mensching Cc: [EMAIL PROTECTED]; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WIX Post-Install Dialog Questions Rob, I have been through the tutorial. I did not see anyplace that shows how to connect an installation directory ID to a path used for a Binary declaration or anything similar to that. All that I need is the syntax to connect MY_APP_TARGET from this snipet: Directory Id=MY_APP_TARGET Name=MyApp LongName=MyApplication to the SourceFile value, $(var.MY_APP_TARGET), in this snipet: Binary Id=MyAppExe SourceFile=$(var.MY_APP_TARGET)\MyApp.exe / Since $(var.MY_APP_TARGET) does not work, nor does [!MY_APP_TARGET], what is the syntax to connect the directory ID to the SourceFile? How should the line starting with Binary Id=MyAppExe ... read? If there is some other way of accomplishing the same thing, that would be fine too. Thanks, Chris Ruel, Automation Consultant, Telvent Farradyne Inc. 3206 Tower Oaks Blvd., Rockville, MD 20852 Email: [EMAIL PROTECTED] Office: 301-984-6460 Fax: 301-816-1884 Rob Mensching [EMAIL PROTECTED] Rob Mensching 12/07/2006 05:13 PM To: [EMAIL PROTECTED] [EMAIL PROTECTED] cc: wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net, [EMAIL PROTECTED] [EMAIL PROTECTED] Subject: RE: [WiX-users] WIX Post-Install Dialog Questions I would encourage you to walk through the WiX tutorial: http://wix.sourceforge.net/tutorial. There is a lot in your snippet below that doesn't make a lot of sense so I'm guessing you're new to setup (I apologize, if I've guessed wrong). From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, December 07, 2006 13:21 To: Rob Mensching Cc: wix-users@lists.sourceforge.net; [EMAIL PROTECTED] Subject: Re: [WiX-users] WIX Post-Install Dialog Questions Rob, I looked at the link you referred. From that info, I still don't see how to get the directory. Is there any chance you could show me an example or make the one below so that it refers to the directory correctly? If you could show me the syntax or way to make the MY_APP_TARGET accessible, that would solve my problem: Directory Id=INSTALLATION_TARGET Name=SourceDir Directory Id=PROGRAM_FILES_TARGET Name=Program LongName=Program Files Directory Id=MY_APP_TARGET Name=MyApp LongName=MyApplication ... Binary Id=MyAppExe SourceFile=$(var.MY_APP_TARGET)\MyApp.exe / CustomAction Id=RunMyAppAction BinaryKey=MyAppExe ExeCommand=[MY_PARAM] Return=check / Chris Ruel, Automation Consultant, Telvent Farradyne Inc. 3206 Tower Oaks Blvd., Rockville, MD 20852 Email: [EMAIL PROTECTED] Office: 301-984-6460 Fax: 301-816-1884 Rob Mensching [EMAIL PROTECTED] Rob Mensching Enviado por: [EMAIL PROTECTED] 12/07/2006 02:42 PM To: [EMAIL PROTECTED] [EMAIL PROTECTED] cc: wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WIX Post-Install Dialog Questions Please keep all threads on the mailing list. You'll want to understand the Directory table in detail. Check out this series of blog entries: http://blogs.msdn.com/robmen/archive/2006/10/17/deciphering-the-msi-directory-table-part-7-directories-are-properties.aspx From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, December 07, 2006 11:35 To: Rob Mensching Subject: RE: [WiX-users] WIX Post-Install Dialog Questions Thanks Rob. I greatly appreciate your timely response. Can you give me a short example of how to refer to a directory from the installation? Sorry, but I don't see how to do it from the SDK you referred me. From this sample... Directory Id=INSTALLATION_TARGET Name=SourceDir Directory Id=PROGRAM_FILES_TARGET
[WiX-users] Comparing two MSIs
Is there a tool out there to compare two MSIs? I'm moving our MSIs to wixv3, and I want to verify that the built MSIs are the same as previously. Cullen Waters SDET Office Live +1 425 706 6809 x 66809 - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Comparing two MSIs
A lot of our installers are pretty complex, and use a bunch of tables. I was hoping for something more automated. From: Peterson, Joel [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 06, 2006 3:36 PM To: Cullen Waters; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Comparing two MSIs Orca is a fair good tool and will allow you to eyeball compare the tables, not sure it has any automatic comparison feature. Joel Peterson Quality Assurance Engineer [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cullen Waters Sent: Wednesday, December 06, 2006 3:28 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Comparing two MSIs Is there a tool out there to compare two MSIs? I'm moving our MSIs to wixv3, and I want to verify that the built MSIs are the same as previously. Cullen Waters SDET Office Live +1 425 706 6809 x 66809 - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing cert using WiX 3.0
Having the cert stuff moved to the util extension would be great for my team. We had to write our own CA for cert work. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joe Kaplan Sent: Tuesday, December 05, 2006 8:54 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Installing cert using WiX 3.0 Yes, that's currently the issue. The build in CAs do not support your scenario, so you'll need to write this yourself. This is why I posted the note I posted on Sunday night. So far, no feedback from the community though... Joe K. On 12/5/06, Rennie Sawade (Volt) [EMAIL PROTECTED] wrote: All I want to do is install the cert. I don't want to do anything with configuring IIS. Does that mean that I should do it in a custom action instead of using the IIS extension? Rennie From: Joe Kaplan on behalf of Joe Kaplan Sent: Mon 12/4/2006 9:03 PM To: wix-users@lists.sourceforge.net Cc: Rennie Sawade (Volt) Subject: Re: [WiX-users] Installing cert using WiX 3.0 It looks like you are missing the culture switch. Does your command line look something like this: light -ext wixiisextension.dll -cultures:en-US -out xxx.msi xxx.wixobj Note that the current IIS CA does not install certificates unless you have other IIS stuff defined as the CA that schedules all of the IIS actions exits out if there are no IIS configuration entries defined in the msi. See my email from yesterday regarding my complaint about that. Joe K. - Original Message - From: Rennie Sawade (Volt) To: wix-users@lists.sourceforge.net Sent: Monday, December 04, 2006 7:18 PM Subject: [WiX-users] Installing cert using WiX 3.0 I tried to install a CA certificate using: iis:Certificate Id='CertRA' StoreLocation='localMachine' StoreName='root'/ I then get quite a few LGHT0102 errors from the linker for different localization variables. Such as The localization variable !(loc.ConfigureIIs) is unkown. Please ensure the variable is defined. The error repeats for other variables such as (loc.StartMetabaseTransaction, loc.RollbackMetabaseTransaction, loc.CommitMetabaseTransaction,.). Can I not just install a certificate using the IIS extension? Or is this a known issue? Thanks, Rennie - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] IIS CA ICE Error
In one of our installers, I've started getting an ICE32 error from the built-in IIS CAs. This is the only installer we have that actually installs web sites, and does some pretty significant IIS configuration (all through the standard CAs in IISExtension). I've gotten an ICE32 error that IIsWebApplication.2 is a localizable string with length 255, but the RegisterIIsSSLCertificate.ApplicationName_ column is a non-localizable string with length 255. Has anyone else seen this error? Is it possible I'm doing something wrong in my wix code to cause this? Cullen Waters SDET Office Live +1 425 706 6809 x 66809 - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] IIsExtension issue
The IIsExtension defines the IIsWebApplicationName (which shows up in MMC as the app name) as a localized string of 255 chars. This string is referenced, as a foreign key, from the RegisterIIsSSLCertificate table. The column in the register table is part of a multi-column primary key for that table. This column is defined as a 255 length string, not localized. Primary key columns cannot be localized, according to ICE03. However, ICE32 throws an error when referencing the ApplicationName column from the RegisterSSLCert column. What is the 'best practice' for using these two tables? Should I just suppress the ICE32 error? Cullen Waters SDET Office Live +1 425 706 6809 x 66809 - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] using ServiceConfig in wix 3.0 - uitl schema elements will not compile with candle
In v3, you have to call candle with -ext WixUtilExtension to use elements from that namespace. Same with light. And, to help you abit, when you call light, you have to specify what cultures to use (like -cultures:en-us) From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Errick Sent: Tuesday, December 05, 2006 12:35 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] using ServiceConfig in wix 3.0 - uitl schema elements will not compile with candle moving form wix 2.0 to wix 3.0 - candle does not compile source with elements from the util scheam - error unexpected child element, ect. do you have an example of using the User or ServiceConfig elements? I know there will be libs to link with light - but need to get source to compile. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing cert using WiX 3.0
You have to include cultures:en-us (or whatever culture your installer is for) on the light command line, in wix v3. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rennie Sawade (Volt) Sent: Monday, December 04, 2006 5:19 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Installing cert using WiX 3.0 I tried to install a CA certificate using: iis:Certificate Id='CertRA' StoreLocation='localMachine' StoreName='root'/ I then get quite a few LGHT0102 errors from the linker for different localization variables. Such as The localization variable !(loc.ConfigureIIs) is unkown. Please ensure the variable is defined. The error repeats for other variables such as (loc.StartMetabaseTransaction, loc.RollbackMetabaseTransaction, loc.CommitMetabaseTransaction,...). Can I not just install a certificate using the IIS extension? Or is this a known issue? Thanks, Rennie - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Need help with a CustomTable
In my app, we are using a couple of CustomTable elements.
The data in one of my columns includes a colon in the string. It looks like
Light uses a colon to delimit the column names and values in the CustomRow
element in the .wixobj file.
Does anyone have any suggestions on how to include the colon in the data for a
column?
I'm getting a null reference exception from light because the linker uses
String.Split(':'), and that is creating an extra, unexpected value in the code.
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Strange error
That error is thrown when an included file uses a prefix that is not declared in the parent file. I'm adding code to properly identify and report the error; it should be in the next release after Monday. From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Fredrik Grohn [EMAIL PROTECTED] Sent: Saturday, December 02, 2006 5:09 PM To: 'Mike Dimmick'; 'Probir Chatterjee'; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Strange error I don’t know much about the error in question here, sorry. However I noticed a different problem with the code in this example; the File element should not have a SelfRegCost attribute set. This would cause the DLL to be registered twice possibly resulting in unexpected behavior during runtime. Fredrik From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Dimmick Sent: Friday, November 10, 2006 12:27 AM To: 'Probir Chatterjee'; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Strange error That error message appears to be erroneously produced for any invalid XML: the catch handler in Preprocessor.cs which catches XmlException on loading the document (line 258) reports SP1ProbablyNotInstalled (error 147). You might try adding the pca namespace to your root document's WiX element. Alternatively, convert your Includes to Fragments. Place your components under a DirectoryRef element. Then, remove the ?Include? directives from your main .wxs file, compile the Fragments separately, and link them all together with light (specifying each .wixobj you need). CWXCom.wxs: ?xml version=1.0 encoding=utf-8? Wix xmlns=http://schemas.microsoft.com/wix/2003/01/wi; xmlns:pca=http://schemas.microsoft.com/wix/2005/02/pubca; Fragment DirectoryRef Id=TARGETDIR Component Id=MyCOM_dll DiskId=1 Guid=DB37D412-2DA6-46b8-866C-5FFA67163B17 File Id=MyCOM_dll Name=CWXBus_1.dll LongName=CWXBusinessRulesII.dll src=..\..\CWXBusinessRulesII\CWXBusinessRulesII.dl KeyPath=yes Vital=yes SelfRegCost=1 / pca:ComPlusApplication Id=MyCOM Name=My COM+ Application pca:ComPlusAssembly Id=MyComPlusAssembly Type=native DllPath=[#MyCOM_dll] pca:ComPlusComponent Id=MyCOM CLSID=8BAC1633-E462-4f56-97EF-E2D48BA61916 / /pca:ComPlusAssembly /pca:ComPlusApplication /Component /DirectoryRef /Fragment /Wix VS2005 has just told me that Component is not valid under Include according to the schema. The schema validation may be what’s causing the XmlException. I’m not sure why Component isn’t allowed when File and Registry are – surely this is also a bug? -- Mike Dimmick From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Probir Chatterjee Sent: 09 November 2006 07:58 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Strange error Importance: High Hi Everyone, I am trying to create an installer using WIX and it has started giving me strange problems. I need to install 2 websites, 1 webservice, 1 db and a COM component. I could do the 1st four without any problem, but when tried putting in the code for COM component I have run into a strange problem On running candle.exe, I am receiving this error: Candle.exe : error CNDL0147 : An error has occurred that most likely indicates that .NET framework 1.1 Service Pack 1 has not been installed. Please see the following website for more information about the service pack and how to install it : http://support.microsoft.com/?kbid=867460 I have installed .net framework 1.1 sp1 but the problem won’t go away I am using the following file for candle and light: d:\tools\wix-2.0.4415.0-binaries\candle.exe cwx_arabic.wxs -ext Microsoft.Tools.WindowsInstallerXml.PcaCompiler,pcaext d:\tools\wix-2.0.4415.0-binaries\light.exe -out cwx_arabic.msi cwx_arabic.wixobj D:\tools\wix-2.0.4415.0-binaries\wixui.wixlib D:\tools\wix-2.0.4415.0-binaries\sca.wixlib -loc D:\tools\wix-2.0.4415.0-binaries\WixUI_en-us.wxl D:\tools\wix-2.0.4415.0-binaries\pubca.wixlib -ext Microsoft.Tools.WindowsInstallerXml.PcaCompiler,pcaext The code for my CWXCom.wxi looks like the following: ?xml version='1.0' encoding='UTF-8'? Include xmlns=http://schemas.microsoft.com/wix/2003/01/wi; xmlns:pca=http://schemas.microsoft.com/wix/2005/02/pubca; Component Id=MyCOM_dll DiskId=1 Guid=DB37D412-2DA6-46b8-866C-5FFA67163B17 File Id=MyCOM_dll Name=CWXBus_1.dll LongName=CWXBusinessRulesII.dll src=..\..\CWXBusinessRulesII\CWXBusinessRulesII.dl KeyPath=yes Vital=yes SelfRegCost=1 / pca:ComPlusApplication Id=MyCOM Name=My COM+ Application pca:ComPlusAssembly Id=MyComPlusAssembly Type=native DllPath=[#MyCOM_dll] pca:ComPlusComponent Id=MyCOM CLSID=8BAC1633-E462-4f56-97EF-E2D48BA61916 / /pca:ComPlusAssembly /pca:ComPlusApplication /Component /Include The main .wxs file refers the component as follows (I am only copy pasting the sections where the file is
Re: [WiX-users] Error code lookup
Alright, I figured out the problem, and I think it is a bug in the Preprocessor. In my include files, I am using elements from the Utility extension. The Include tag has xmlns:util=:. When this file is included in my main .wxs, by using ?include ?, the Include element is stripped out. This removes the xmlns:util attribute from the top of the included section. Because my .wxs file does not use any elements in the util namespace, the root element in that file does not contain the xmlns attribute. This causes an XML exception, because the elements in the Included section have util: prefixes, which is not declared in the concatenated xml. I'm going to work on a fix, which I'll submit Monday or Tuesday. As a workaround, I just added the xmlns:util attribute to my .wxs files, so the total xml, after including the include files, is valid XML. I am also going to submit a change to the error message for this error, and note that it is caused by malformed XML, rather than a .NET 1.1 SP1 bugfix. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cullen Waters Sent: Wednesday, November 22, 2006 3:05 PM To: [EMAIL PROTECTED]; Wix-Users List Subject: Re: [WiX-users] Error code lookup I agree on the too aggressive bit, especially since Wix is explicitly(in the exe.config files) set to run under .net 2.0 as well as 1.1. Presumably, any bug fixes that were present in 1.1 SP1 are also present in 2.0, which means that this message is only correct if there is an error, and if the user is running under 1.1. Thanks for the heads-up, Mike, I'll check into the xml, especially how it looks after the include is processed. I will send out an email once I find the root cause, so everyone can share in the learning. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, November 22, 2006 7:38 AM To: Cullen Waters; Wix-Users List Subject: Re: [WiX-users] Error code lookup [EMAIL PROTECTED] wrote: Is there a way to lookup Wix error codes? I'm getting CNDL0124, and I'd li ke to find out more about the error, so I can start debugging it. As Rob says, look in messages.xml. IIRC in v3 all the Message elements carry a Number attribute so you can simply search for Number=124. I've looked into this problem before and I think that you've actually got malformed XML, or after performing the include step the XML is malformed. I noted last time that the Component element is not valid under Include in the WiX v2 schema. The catch block in Preprocessor.cs reports SP1ProbablyNotInstalled if *any* XmlException occurs, which seems too aggressive to me. No doubt some exception is erroneously thrown if SP1 isn't installed and you try to load an XmlDocument from a StringReader, but can we not tell the difference between this and an actual malformed document? -- Mike Dimmick - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Another strange error message
According to the MS article in the error message, Win2k3 comes with .NET1.1 SP1. The build number of .NET 1.1 on my machine is 1.1.4322.2300, which is the highest 1.1 build number I've seen. I ran Microsoft Update, just to make sure, and it didn't list SP1 as an available update. I've now gotten this message on three different .wxs files, and can repro every time on those files. I'm in the process of upgrading all of our installers from v2 to v3. None of the installers had errors when we were using v2 to build them. Is there something I can do to provide debugging information? This looks like a possible Wix bug to me. From: Justin Rockwood [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 21, 2006 10:59 AM To: Cullen Waters; 'Wix Group' Subject: RE: [WiX-users] Another strange error message I may be wrong, but I seem to remember that Win2003 only comes with .NET Framework 1.1 and not the service packs. Have you tried installing SP1? Justin From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cullen Waters Sent: Tuesday, November 21, 2006 9:50 AM To: 'Wix Group' Subject: [WiX-users] Another strange error message I'm getting another error message that I don't understand. When I try to build an msi from two wxs files, I get an error that says the framework 1.1 SP1 might not be installed. I'm running on W2k3 server, which has the .net framework 1.1 SP1 as part of the OS install. Can anyone provide any more information about this error? error CNDL0124 : An error has occurred that most likely indicates that the .NET Framework 1.1 Service Pack 1 has not been installed. Please see the following website for more information about the service pack and how to install it: http://support.microsoft.com/?kbid=867460 Cullen Waters SDET Office Live +1 425 706 6809 x 66809 - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Creating and populating your own MSI table in WIX
Check the CustomTable element -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brandon Tyler Sent: Friday, November 10, 2006 1:36 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Creating and populating your own MSI table in WIX I have a custom action that is looking for a certain table in MSI that my WIX is not creating right now: I need the functionality Like Add Custom Table... In Orcas. How would I do this? Thanks This e-mail transmission may contain information that is proprietary, privileged and/or confidential and is intended exclusively for the person(s) to whom it is addressed. Any use, copying, retention or disclosure by any person other than the intended recipient or the intended recipient's designees is strictly prohibited. If you are the intended recipient, you must treat the information in confidence and in accordance with all laws related to the privacy and confidentiality of such information. If you are not the intended recipient or their designee, please notify the sender immediately by return e-mail and delete all copies of this email, including all attachments. - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Check for .NET Framework 1.1 SP1 before install
The VisualStudio extension should have all the checks you need for every version of the framework that has been shipped. Did you check out those elements first? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wilson, Phil Sent: Wednesday, November 01, 2006 1:13 PM To: Jonas Abrams; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Check for .NET Framework 1.1 SP1 before install I believe this is the official registry key for SP1: http://blogs.msdn.com/astebner/archive/2004/09/14/229574.aspx I suspect an MSI file search is somewhat easier. A search for mscorlib.dll in [WindowsFolder]Microsoft.NET\Framework\v1.1.4322with a MinVersion of 1.1.4322.2299 (1.1SP1 mscorlib is 1.1.4322.2300) is more MSI-friendly, doesn't seem to be the official recommended way, but does deal with the or greater more gracefully for 1.1. If the 2.0 FW satisfies your conditions you need to add another check either way. Phil Wilson From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jonas Abrams Sent: Wednesday, November 01, 2006 11:41 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Check for .NET Framework 1.1 SP1 before install Hey everyone, I am trying to force my install to check and make sure Service Pack 1 for the .NET Framework 1.1 is installed before it is able to run. Currently I have a check for .NET Framework 1.1 (see code below) but I have not been able to figure out how to check for SP1. !-- Don't allow install to continue if .NET Framework 1.1 is not installed -- Property Id='FRAMEWORK11' RegistrySearch Id='Framework11Registry' Type='raw' Root='HKLM' Key='Software\Microsoft\.NETFramework\policy\v1.1' Name='4322' / /Property Condition Message='.NET Framework 1.1.4322 or greater is required. Please install this software first, and then rerun the setup again.'FRAMEWORK11 = 3706-4322/Condition Anyone have any ideas? Thanks in advance, Jonas - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Best Practices - Creating Databases
My suggestion is to use a single script for the initial installation. Any upgrades or patches, or subsequent versions should be broken up. On first installation, when you are creating the db, you can be reasonably certain through testing that your script will succeed. On any successive installation action, you cannot be certain that someone didnt make some change to the database in their installation that will cause your script to fail. I would separate the scripts, if for no other reason than easier debugging of setup failures, since youll be able to log each script separately, and know which script is failing. The comparison to C# or VB code isnt valid, in my opinion. Database scripts are completely different. I would certainly expect that you would keep your scripts separate in your dev tree. My gut feeling is that your msi will be smaller if you use a single file instead of thousands of file, and will execute faster. There will be fewer entries in the file table, and much less I/O. Also, you will only have to pay the overhead of connecting to your sql server once, instead of once per table/sp/etc. Just my .02 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dana Gutride Sent: Friday, October 20, 2006 6:32 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Best Practices - Creating Databases Ok, I'll take a stab. I don't know what the best practice is, but I can tell you what we are doing. We have a large database with many, many tables and even more stored procedures. We use one sql file to create the tables (that file is under 100K) and break the stored procedures up into multiple files. After much testing, we haven't ever had the table creation or the stored procedure creation fail during an MSI install. I've asked this list and other install lists before what other people are doing and it seems every person you ask does it slightly differently. Just to prepare you for what's ahead, it is slightly more difficult to pull off an upgrade successfully. We have more rollbacks on upgrade because sometimes people have changed the database for one reason or another and then we're left with the database in an unpredictable state. Dana On 10/20/06, Douglas Watts [EMAIL PROTECTED] wrote: Anyone? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Douglas Watts Sent: Thursday, October 19, 2006 1:16 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Best Practices - Creating Databases This is a best practices question. I need to create a database for my application. For example sake, let's say I have 100 tables to create along with related indexes and keys. I can easily generate one large script and use that in my WiX project. On the other hand, I could break the script down such that I have one script per table. Of course, numerous other possibilities exist as well. What is the best practice for this scenario? __ Doug Watts - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Certificates with WIX
Ive seen the same behavior with one of our installers. I think this is a bug in the implementation. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Muzammil Ahmed Sent: Friday, October 13, 2006 2:57 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Certificates with WIX Hi, I had a question about installing certificates to the personal store. I am using the certificate element as follows: Certificate Id='cert' CertificatePath=wildcaddy.pfx StoreLocation=currentUser StoreName=my/ However, I do not see my certificate within the personal store when I view them through mmc. Can any one why this is the case? Or if someone has added certificates via WIX offer some assistance? Thanks! Muz - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX XML Issue
Also, since the machines you're installing on have the .net runtime installed (or else there wouldn't be a machine.config to edit), you could write a .NET custom action (easier than c++) that runs before XMLFile, and performs your xml search on machine.config, and sets a property telling XmlFile whether it should run the appSettings creation. Does that make sense? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of david adams Sent: Wednesday, October 11, 2006 12:43 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WiX XML Issue Not sure if this helps Douglas, but could you add a custom section and section handler instead of using AppSettings? That way, you are assured that the section would not exist prior to you adding it and you are not limited to using duplicate key names since your configuration section handler could handle whatever keys you setup. Instead of: ... AppSettings add key= value= / add key= value= / ... /AppSettings Something like: ... customSection key1 name= value= / key2 name= value= / ... /customSection (assuming you reference your customSection in the configSection naming it and declaring the SectionHandler to use with it) David Adams MSN MessengerID: [EMAIL PROTECTED] From: Douglas Watts [EMAIL PROTECTED] To: Cullen Waters [EMAIL PROTECTED],wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WiX XML Issue Date: Wed, 11 Oct 2006 14:36:25 -0400 MIME-Version: 1.0 Received: from lists-outbound.sourceforge.net ([66.35.250.225]) by bay0-mc10-f18.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Wed, 11 Oct 2006 11:37:49 -0700 Received: from sc8-sf-list1-new.sourceforge.net (unknown [10.3.1.93])by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTPid 1171113215; Wed, 11 Oct 2006 11:37:48 -0700 (PDT) Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]helo=mail.sourceforge.net)by sc8-sf-list1-new.sourceforge.net with esmtp (Exim 4.43)id 1GXiwZ-0007Bt-KPfor wix-users@lists.sourceforge.net; Wed, 11 Oct 2006 11:36:39 -0700 Received: from 66-194-149-212.static.twtelecom.net ([66.194.149.212]helo=EXCHANGE-01.advectis.office)by mail.sourceforge.net with esmtp (Exim 4.44) id 1GXiwY-0002or-K2for wix-users@lists.sourceforge.net; Wed, 11 Oct 2006 11:36:39 -0700 X-Message-Info: LsUYwwHHNt0vmw3QJwjTGr8Fuyvmpg1UHuvq2Ec6GMY= Content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.5 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: [WiX-users] WiX XML Issue Thread-Index: Acbr5h2j/zA5AD/0S+Wra8+ZTjRIiwACKVsgAFOHd4AAB9zDEAABxbBw X-Spam-Score: 1.0 (+) X-Spam-Report: Spam Filtering performed by sourceforge.net.See http://spamassassin.org/tag/ for more details.Report problems tohttp://sf.net/tracker/?func=addgroup_id=1atid=211.0 FORGED_RCVD_HELO Received: contains a forged HELO0.0 HTML_MESSAGE BODY: HTML included in message X-BeenThere: wix-users@lists.sourceforge.net X-Mailman-Version: 2.1.8 Precedence: list List-Id: General discussion for Windows Installer XML toolset.wix-users.lists.sourceforge.net List-Unsubscribe: https://lists.sourceforge.net/lists/listinfo/wix-users,mailto:[EMAIL PROTECTED] List-Archive: http://sourceforge.net/mailarchive/forum.php?forum=wix-users List-Post: mailto:wix-users@lists.sourceforge.net List-Help: mailto:[EMAIL PROTECTED] List-Subscribe: https://lists.sourceforge.net/lists/listinfo/wix-users,mailto:[EMAIL PROTECTED] Errors-To: [EMAIL PROTECTED] Return-Path: [EMAIL PROTECTED] X-OriginalArrivalTime: 11 Oct 2006 18:37:50.0092 (UTC) FILETIME=[5AB45CC0:01C6ED64] I tried that but I get an error basically saying that the appSettings node could not be found. The problem gets more complicated in that if the appSettings element already exists and contains child elements (add elements) then I risk overwriting them. Apparently WiX (at least 2.0.4415) does not support the XPath last() function. So I have two problems: 1) I cannot query to see if the appSettings node already exists 2) I cannot create my add attributes for the last element (I assume the one I just created would be appended and not prepended) Anyone got any ideas? __ Doug Watts From: Cullen Waters [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 11, 2006 1:41 PM To: Douglas Watts; wix-users@lists.sourceforge.net Subject: RE: Re: [WiX-users] WiX XML Issue I don't have a definite solution, Doug, but I have a suggestion. Have you tried just creating your add elements, without specifying the appSettings element, in a machine.config that doesn't contain the appSettings? Maybe the XmlFile element is smart enough to create the path if your XPath doesn't exist. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Douglas Watts Sent: Wednesday, October 11, 2006 6:58 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WiX XML Issue Does anyone know how to check for the existence
Re: [WiX-users] WiX XML Issue
I'm not really sure about sending properties back from managed code. Worst case, you could do all your machine.config changes in the mgd code CA. I think you'll hear some complaints from this alias if you use vbscript to create a custom action. The problem is that supporting reinstall and rollback and uninstall from vbscript is pretty hard. It's a lot easier from a managed CA. -Original Message- From: Douglas Watts [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 11, 2006 1:25 PM To: Cullen Waters; david adams; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] WiX XML Issue Thanks guys. David: The application is already written (it's been in production for a couple of years). So changing the way it uses machine.config is not an immediate option. Your suggestion would actually be my preferred way. Cullen: I'm actually looking into writing a VB script to run as a custom action to modify the machine.config. Do you guys think this would work? As for a managed code CA, I thought managed code CAs could not set properties back in the installer. I thought they could only receive properties. I'm not sure about this. ___ Doug Watts -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cullen Waters Sent: Wednesday, October 11, 2006 3:55 PM To: david adams; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WiX XML Issue Also, since the machines you're installing on have the .net runtime installed (or else there wouldn't be a machine.config to edit), you could write a .NET custom action (easier than c++) that runs before XMLFile, and performs your xml search on machine.config, and sets a property telling XmlFile whether it should run the appSettings creation. Does that make sense? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of david adams Sent: Wednesday, October 11, 2006 12:43 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WiX XML Issue Not sure if this helps Douglas, but could you add a custom section and section handler instead of using AppSettings? That way, you are assured that the section would not exist prior to you adding it and you are not limited to using duplicate key names since your configuration section handler could handle whatever keys you setup. Instead of: ... AppSettings add key= value= / add key= value= / ... /AppSettings Something like: ... customSection key1 name= value= / key2 name= value= / ... /customSection (assuming you reference your customSection in the configSection naming it and declaring the SectionHandler to use with it) David Adams MSN MessengerID: [EMAIL PROTECTED] From: Douglas Watts [EMAIL PROTECTED] To: Cullen Waters [EMAIL PROTECTED],wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WiX XML Issue Date: Wed, 11 Oct 2006 14:36:25 -0400 MIME-Version: 1.0 Received: from lists-outbound.sourceforge.net ([66.35.250.225]) by bay0-mc10-f18.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Wed, 11 Oct 2006 11:37:49 -0700 Received: from sc8-sf-list1-new.sourceforge.net (unknown [10.3.1.93])by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTPid 1171113215; Wed, 11 Oct 2006 11:37:48 -0700 (PDT) Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92]helo=mail.sourceforge.net)by sc8-sf-list1-new.sourceforge.net with esmtp (Exim 4.43)id 1GXiwZ-0007Bt-KPfor wix-users@lists.sourceforge.net; Wed, 11 Oct 2006 11:36:39 -0700 Received: from 66-194-149-212.static.twtelecom.net ([66.194.149.212]helo=EXCHANGE-01.advectis.office)by mail.sourceforge.net with esmtp (Exim 4.44) id 1GXiwY-0002or-K2for wix-users@lists.sourceforge.net; Wed, 11 Oct 2006 11:36:39 -0700 X-Message-Info: LsUYwwHHNt0vmw3QJwjTGr8Fuyvmpg1UHuvq2Ec6GMY= Content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.5 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: [WiX-users] WiX XML Issue Thread-Index: Acbr5h2j/zA5AD/0S+Wra8+ZTjRIiwACKVsgAFOHd4AAB9zDEAABxbBw X-Spam-Score: 1.0 (+) X-Spam-Report: Spam Filtering performed by sourceforge.net.See http://spamassassin.org/tag/ for more details.Report problems tohttp://sf.net/tracker/?func=addgroup_id=1atid=211.0 FORGED_RCVD_HELO Received: contains a forged HELO0.0 HTML_MESSAGE BODY: HTML included in message X-BeenThere: wix-users@lists.sourceforge.net X-Mailman-Version: 2.1.8 Precedence: list List-Id: General discussion for Windows Installer XML toolset.wix-users.lists.sourceforge.net List-Unsubscribe: https://lists.sourceforge.net/lists/listinfo/wix-users,mailto:wix-us [EMAIL PROTECTED] List-Archive: http://sourceforge.net/mailarchive/forum.php?forum=wix-users List-Post: mailto:wix-users@lists.sourceforge.net List-Help: mailto:[EMAIL PROTECTED] List-Subscribe: https://lists.sourceforge.net/lists/listinfo/wix-users,mailto:wix-us [EMAIL PROTECTED] Errors-To: [EMAIL PROTECTED] Return-Path: [EMAIL PROTECTED] X-OriginalArrivalTime: 11 Oct 2006 18:37:50.0092 (UTC
Re: [WiX-users] WiX XML Issue
Two ways. One is to create a console application, and use wix's custom tag to call it during execution, passing flags as necessary. Two is to inherit from the Installer class. I'm not sure how you get that code hooked up using Wix, though. Sorry I can't be more help here. -Original Message- From: John Vottero [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 11, 2006 2:43 PM To: Cullen Waters; david adams; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] WiX XML Issue Also, since the machines you're installing on have the .net runtime installed (or else there wouldn't be a machine.config to edit), you could write a .NET custom action (easier than c++) that runs before XMLFile, and performs your xml search on machine.config, and sets a property telling XmlFile whether it should run the appSettings creation. How do you write a .NET custom action? - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Modifying Machine.Config Under 2 Different Features
My first thought would be to create a third feature, which the user has to install, which then does the modification of machine.config. Then, you could put your xml modification in a new component, which gets installed with the must install feature. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Douglas Watts Sent: Monday, October 09, 2006 10:57 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Modifying Machine.Config Under 2 Different Features WIX Version: 2.0.4415.0 My installer will install two different products (companion products). While the user would normally install one on one machine and the other on another machine, they could install both on the same machine. I need to modify the MACHINE.CONFIG regardless of which feature gets installed. I am assuming that I will have a component that will use WiXs XML support to make the modifications. What is the best way to structure this so that the component gets installed regardless of which feature the user selects? They may select both features. Also, each feature is marked ConfigurableDirectory which means that they could be different directory trees. __ Doug Watts - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Release v3
If you downloaded the v3, youll also have an exe called wixcop in the distribution. Run wixcop on your existing v2 .wxs files, and it will automagically update them to the latest schema. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, October 06, 2006 3:09 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Release v3 I don't know whether this is right time and place to post my questions here. We have a stable Wix v2 project that contains the installation and configuration of VS 2005 dll, exe, database, windows service, web service. This afternoon I downloaded Wix v3 and got a lot errors and warnings. The preprocessors don't work, WebVirtualDir becomes an unexpected element for component, etc. Where can I find instructions on how to upgrade from v2 to v3? Thank you very much in advance. Hesheng Bao Software Design Engineer Eaton Electrical Software Meters Business Units 150 Industry Drive Pittsburgh, PA 15275 412.494.3023 - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX3.0 - Incorporating release path into File Source attribute using Visual Studio 2005
The way we do it is using environment variables. Our build process sets an environment variable for build type(called BuildType), then we reference that in wix using $(env.BuildType) From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Abshire Sent: Monday, September 25, 2006 12:10 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] WiX3.0 - Incorporating release path into File Source attribute using Visual Studio 2005 Howdy. I am using a WiX project to build a MSI for a project I am working on in VS2005. The WiX project is part of the whole solution. I am trying to figure out how to make my WiX source file smart enough to figure out which biuld configuration I am using (release or debug) and gather the binaries up from that path. In the File element, there is a Source attribute. How do I make the path in this source attribute aware of which configuration I am building? Thanks! -Ed Abshire - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX3.0 - Incorporating release path into File Source attribute using Visual Studio 2005
I dont think that the build system we use is analogous to either of those. However, for the visual studio build, you could probably make msbuild set that environment variable, in the project file for the project youre building. Then, when candle and light are called, the variable will be set. That should also take care of your TFS build. Im not certain about the TFS build, though, since I havent ever used that. From: Ed Abshire [mailto:[EMAIL PROTECTED] Sent: Monday, September 25, 2006 1:04 PM To: Cullen Waters; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] WiX3.0 - Incorporating release path into File Source attribute using Visual Studio 2005 So out of curiosity, where did you set that inyour build process? I have two scenarios: 1) Desktop builds using the Visual Studio IDE 2) Team Foundation Server using MSBuild For scenario one, I was thinking in the compiler properties of the WiX Project, where it allows you to set a name=property In the TFS build, I'm not so sure. Thanks for the help, I've never been real strong on understanding the mechanics behind where/when properties on builds are set, kinda new to this. -Ed From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cullen Waters Sent: Monday, September 25, 2006 12:48 PM To: Ed Abshire; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WiX3.0 - Incorporating release path into File Source attribute using Visual Studio 2005 The way we do it is using environment variables. Our build process sets an environment variable for build type(called BuildType), then we reference that in wix using $(env.BuildType) From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Abshire Sent: Monday, September 25, 2006 12:10 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] WiX3.0 - Incorporating release path into File Source attribute using Visual Studio 2005 Howdy. I am using a WiX project to build a MSI for a project I am working on in VS2005. The WiX project is part of the whole solution. I am trying to figure out how to make my WiX source file smart enough to figure out which biuld configuration I am using (release or debug) and gather the binaries up from that path. In the File element, there is a Source attribute. How do I make the path in this source attribute aware of which configuration I am building? Thanks! -Ed Abshire The preceding email message and any attachment to the email message contains information that is confidential, may be legally privileged, and may constitute non-public information. It is intended to be conveyed only to the designated recipient(s). If you have received this message in error, please immediately notify the sender by return email and destroy all copies of this message. Unauthorized use, dissemination, distribution, or reproduction of this email message or any attachment is strictly prohibited and may be unlawful. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Reporting Services CA
Is there any demand for a built-in Wix custom action to install/upgrade/repair /remove Sql Reporting Services reports? Please let me know if this is something youd be interested in. Cullen Waters SDET Office Live +1 425 706 6809 x 66809 - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] New features in 3.0 vs. 2.0?
Here is a list the wix devs sent me a while back, when I asked the same question: • Improved standard UI library with much strong customization story • Wixlibs, binary wixlibs • Overridable sequencing • Standard UI support • Support for arbitrary binary columns • Support for all MSI 4.0 features (2.0 cannot support MsiPatchCertificate yet for example) • Simpler extension model for adding custom tables or other authoring constructs (both compiler and decompiler support) • Extension model for binding of files and cabinet creation (to allow for custom logic to find files and cache cabinets) • Wix variables (for creating variables that are resolved right before msm/msm files are created) • Better localization model (for localizing stuff ) • Much better support for merge module errors and warnings • Standard Nant and MSBuild tasks • ComponentGroups/FeatureGroups for creating collections of components and components/features/merges • Serialization/deserialization classes on top of the wix schema to allow for fast, type-safe creation of wix source files (used heavily by the decompiler) • Auto-generation of short file names (apparently this is a major improvement for lots of people) • Lots of smaller features which allow for the tweaking of specific compiler, linker, decompiler, etc.. behaviors (see usage info for each tool) • Lots and lots and lots of bug fixes • Heat – new tool for quickly capturing self-registration, typelib keys, assembly install info, websites, files, and directories into wix authoring • Smoke – new tool for running MSI validation • Built-in MSI validation when running light • Brand new version of Votive (soon) • Patch creation support (soon) • ClickThrough (soon to be vastly improved) • Re-written decompiler (dark) is now fully extensible for handling custom tables easily • Support localization of control sizes and positions • Multi-threaded cabinet creation (for greater performance building multi-cab setups on multi-proc machines) • DiskId optional for specifying files on Media 1 • Binary wixout files for allowing final MSI creation to occur delayed or on a different machine • Long filename support for all COM registration • Better error messages for missing references • Intellisense support for extension schemas via XsdStitch • Mutator for converting registry keys into strongly typed COM elements (great for catching COM authoring bugs) • Cleanup intermediate file formats to ensure support for future versions of Windows Installer (and prevent us from needing to touch the intermediate formats ever again) • Lots more in the works surrounding specific scenarios like making ActiveX, Office plugin, and isolated application installations a lot easier • There’s all of the new and sparkly features of Votive for v3 as well. That list is on my blog at http://blogs.msdn.com/jrock/archive/2006/07/18/670149.aspx. Even if you don’t use Votive as the UI for your development, it’s still worth noting that the .wixproj file format is MSBuild compliant now in case your team uses MSBuild to build. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: Wednesday, September 20, 2006 6:39 PM To: 'Lorne Laliberte'; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] New features in 3.0 vs. 2.0? Unfortunately, there isn't a list right now. There is actually a bug assigned to Derek saying he should document them but he left the building before doing so. I guess, we'll just have to piece it all back together ourselves. smile/ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lorne Laliberte Sent: Wednesday, September 20, 2006 13:02 To: wix-users@lists.sourceforge.net Subject: [WiX-users] New features in 3.0 vs. 2.0? Hello, Is there a list of the differences between 2.0 and 3.0 available anywhere? From quickly comparing the .chm files and searching the list archive I've come up with these new features in 3.0. Am I correct? What features have I missed? :) - Auto-generation of short file and directory names - Auto-generate components from file trees (via Heat) - MSI Validation built into light.exe - Difxapp schema (Driver Install Frameworks for Applications) - Iis Schema (Internet Information Services Extension) - Sql Schema (SQL Server Extension) - Util Schema (Utility Extension) - floating Publish elements, so you can attach control events without changing the dialogs themselves I'm sure there are other features/differences though. :) (This kind of information would be helpful in evaluating whether to wait for a stable 3.0 release or to use 2.0.) ...Lorne Laliberte - Take Surveys. Earn Cash. Influence
Re: [WiX-users] re : votive with visual c# 2005 express edition
C# express doesnt support the same add-in model as the paid versions of VS. Im pretty sure that Votive will not work on C# express. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ali-Akber Saifee Sent: Tuesday, September 12, 2006 9:56 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] re : votive with visual c# 2005 express edition Since votive is dropping support for vs2003 - i installed vc# 2005 express edition and intellisense (or any of the other votive glue...). Is there any chance that this will be supported..? I plopped the schema files into C:\Program Files\Microsoft Visual Studio 8\Xml\Schemas and intellisense came through to vc# perfectly... thanks. ./Ali - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
