Re: [WiX-users] Where to start? V2 or V3?
Thanks Rob and Matt, I think that gives me a better idea of where to go next - I'll probably start with V2, build a simple project, and then take a look at WixCop... with a view to moving to V3 as soon as we get a 'stable' build... I suspect that for this release, anything I do will be V2 based. Regards, Adam. Matthew Janulewicz-2 wrote: > > In my experience (and who's experience other than mine would I have?) v3 > is stable enough to do most tasks that the average installer needs to > do. Granted, most of our installers (currently in test/demo phase) copy > files around, register stuff in the GAC, create a web page or a virtual > directory or two. We've had good luck with it. > > One thing I personally like about Votive3 is support for msbuild, as > well as SCC support for source control (in VS2005.) > > One thing I don't like is that my favorite GUI (WixEdit) doesn't yet > support Wix3 extensions (though they are working on it.) Although the > Intellisense you get with Wix3 is pretty cool, too. Depends on how you > like to work. > > If I were making that decision right now, I'd write some quick installs > in Wix2 using a gui (again, like Wixedit), then use WixCop to convert it > to v3 and play with it in Visual Studio (or wherever.) > > > -Matt > > > -Original Message- > From: Adam D [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 03, 2006 9:37 AM > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Where to start? V2 or V3? > > > Hello, > > I'm about to get started with WiX as a possible replacement for > InstallShield. I would like to get a view on what I should start with - > V2 > or V3? I want to use Votive, and I quite like the idea of a MSBuild > compliant project file, but I don't want to jump in using V3 if it has > any > fundamental stability issues. > > I've read > http://www.nabble.com/What-use%2C-WiX-2-or-WiX-3---tf1978732.html#a54293 > 91 > this post - but I have no feel for where WiX is at right now. I plan > to > release in the last breath of this year. > > So - what's the concensus of opinion? Start with V2 or V3? > > Thanks for your time. > > Adam. > -- > View this message in context: > http://www.nabble.com/Where-to-start--V2-or-V3--tf2377306.html#a6623942 > 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.php&p=sourceforge&CID=DEVDE > V > ___ > 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.php&p=sourceforge&CID=DEVDEV > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- View this message in context: http://www.nabble.com/Where-to-start--V2-or-V3--tf2377306.html#a6624750 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.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Where to start? V2 or V3?
In my experience (and who's experience other than mine would I have?) v3 is stable enough to do most tasks that the average installer needs to do. Granted, most of our installers (currently in test/demo phase) copy files around, register stuff in the GAC, create a web page or a virtual directory or two. We've had good luck with it. One thing I personally like about Votive3 is support for msbuild, as well as SCC support for source control (in VS2005.) One thing I don't like is that my favorite GUI (WixEdit) doesn't yet support Wix3 extensions (though they are working on it.) Although the Intellisense you get with Wix3 is pretty cool, too. Depends on how you like to work. If I were making that decision right now, I'd write some quick installs in Wix2 using a gui (again, like Wixedit), then use WixCop to convert it to v3 and play with it in Visual Studio (or wherever.) -Matt -Original Message- From: Adam D [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 03, 2006 9:37 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Where to start? V2 or V3? Hello, I'm about to get started with WiX as a possible replacement for InstallShield. I would like to get a view on what I should start with - V2 or V3? I want to use Votive, and I quite like the idea of a MSBuild compliant project file, but I don't want to jump in using V3 if it has any fundamental stability issues. I've read http://www.nabble.com/What-use%2C-WiX-2-or-WiX-3---tf1978732.html#a54293 91 this post - but I have no feel for where WiX is at right now. I plan to release in the last breath of this year. So - what's the concensus of opinion? Start with V2 or V3? Thanks for your time. Adam. -- View this message in context: http://www.nabble.com/Where-to-start--V2-or-V3--tf2377306.html#a6623942 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.php&p=sourceforge&CID=DEVDE V ___ 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.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Where to start? V2 or V3?
This year? Stick to v2. I'm expecting there will be another bump or two in the next few months in v3 that I would not want you to go through. WiX v2 isn't as "cool" as WiX v3 but it will behave consistently... which is probably the most important thing for you in the next few months. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adam D Sent: Tuesday, October 03, 2006 9:37 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Where to start? V2 or V3? Hello, I'm about to get started with WiX as a possible replacement for InstallShield. I would like to get a view on what I should start with - V2 or V3? I want to use Votive, and I quite like the idea of a MSBuild compliant project file, but I don't want to jump in using V3 if it has any fundamental stability issues. I've read http://www.nabble.com/What-use%2C-WiX-2-or-WiX-3---tf1978732.html#a5429391 this post - but I have no feel for where WiX is at right now. I plan to release in the last breath of this year. So - what's the concensus of opinion? Start with V2 or V3? Thanks for your time. Adam. -- View this message in context: http://www.nabble.com/Where-to-start--V2-or-V3--tf2377306.html#a6623942 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.php&p=sourceforge&CID=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.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Where to start? V2 or V3?
Hello, I'm about to get started with WiX as a possible replacement for InstallShield. I would like to get a view on what I should start with - V2 or V3? I want to use Votive, and I quite like the idea of a MSBuild compliant project file, but I don't want to jump in using V3 if it has any fundamental stability issues. I've read http://www.nabble.com/What-use%2C-WiX-2-or-WiX-3---tf1978732.html#a5429391 this post - but I have no feel for where WiX is at right now. I plan to release in the last breath of this year. So - what's the concensus of opinion? Start with V2 or V3? Thanks for your time. Adam. -- View this message in context: http://www.nabble.com/Where-to-start--V2-or-V3--tf2377306.html#a6623942 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.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Upgrade and remove
Hi Bob, I have discovered a few hours ago that SetInstallLevel to 1 in an upgrade will actually refresh the Features and install only the features that I want. Your suggestion would help if the setup type had 3 options: Typical, Full, Custom. This setup has more levels and tuning INSTALLLEVEL will not help. From this point of view it would help if INSTALLLEVEL would install the features that are the exact level only and not those that are below (I guess this is a feature request for Windows Installer team, which is not that important - the feature not the team!). I think I will create a small upgrade sample and fill it in as a bug. Best regards, Calin Bob Arnson wrote: > Calin Iaru wrote: >> It should be only Administration because the setup resets the >> level of all other features to 0 when "Typical" is selected like this: >> > AllowAdvertise="no"> >> >> > That's not going to work. MSI evaluates feature conditions only once, > during CostFinalize. UI comes after that, so it won't affect feature > scheduling. Take a look at the INSTALLLEVEL property documentation; > you can use it and Feature/@Level to make typical and full feature sets. > > I'd suggest starting your upgrade work with a simpler case of a full > install. Once that works, you can get into feature states. > - 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.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] getting an error with the upgrade tag
Scott Sam wrote: > And I schedule RemoveExistingProducts with this > > > > I'm still getting the unresolved reference to symbol > CustomAction:RemoveExistingProducts in section Product. > RemoveExistingProducts is a standard action, not a custom action. So you should schedule it like this: -- sig://boB http://bobs.org - 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.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Upgrade and remove
Calin Iaru wrote: > It should be only Administration because the setup resets the level > of all other features to 0 when "Typical" is selected like this: >AllowAdvertise="no"> > > That's not going to work. MSI evaluates feature conditions only once, during CostFinalize. UI comes after that, so it won't affect feature scheduling. Take a look at the INSTALLLEVEL property documentation; you can use it and Feature/@Level to make typical and full feature sets. I'd suggest starting your upgrade work with a simpler case of a full install. Once that works, you can get into feature states. -- sig://boB http://bobs.org - 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.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using a generated (by tallow.exe) fragment file in acomponent
Jarl Friis wrote: > appropriate element). I have expected to be able to avoid > that for the standard reasons: > It's time consuming. > It does not require intelligence. > It's error prone; In half-a-year, when I actually do make an > Problem is: It does require intelligence. See, for example: http://blogs.msdn.com/robmen/archive/2003/10/18/56497.aspx. -- sig://boB http://bobs.org - 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.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error 1702
Hi I know how to do it. I just need to use the FroceReboot standard action. Anyway is there any way to find out what error messasage (error code) is used (trigered) by which action? (some kind of list...) Thanks Stefan Stefan Pavlik wrote: > Hi list > > I went through the Windows Installer error texts and found out that > some Errors are quite usefull. > My question is: What should I do to rise such error? > I know that I can create Custom Action type 19 but it will just > display the text and exit the installation. > > For example: > I need (some nasty request) to check some condition and rise dialog > with text (and behaviour) similar to error 1702. > (The installer must restart your system before configuration of [2] > can continue. Click Yes to restart now or No if you plan to > manually restart later.) > > Is all this possible? > > Thanks > > Stefan > > > -- Stefan Pavlik | [EMAIL PROTECTED] Whitestein Technologies | www.whitestein.com Panenska 28 | SK-81103 Bratislava | Slovak Republic Tel +421(2)5930-0735 | Fax +421(2)5443-5512 - 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.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] getting an error with the upgrade tag
I added this upgrade tag, And I schedule RemoveExistingProducts with this I'm still getting the unresolved reference to symbol CustomAction:RemoveExistingProducts in section Product. What else am I missing? - 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.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing machine-specific license files
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Sigurd Stenersen > Sent: Monday, October 02, 2006 6:22 PM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Installing machine-specific license files > > Arnette, Bill wrote: > > the [...] system will package the .msi up > > in a self-extracting zip file for the user to download. > > Why ? > Why what? Why do I need to have the user download license files? It's a DirectShow based-app with custom filters. Each and the application filter is individually licensed and is signed with a key generated derived from the machine-specific hash. There some 60 licensed components and each one has its own license file. Why the MSI? It's a simple way to package everything up, find where the product is installed, and copy the license files to the product directory. Why a SE zip file? Single file download/installer. - 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.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] syncing many autogenerated files with wxs file
[EMAIL PROTECTED] writes: > Hello, > > > > My project generates documentation with doxygen and docflex for its library, > which consists of a number of classes, resulting in a large number of HTML > files, spread over a directory structure. > Could you use the itteration feature in the preprocessor: http://wix.sourceforge.net/manual-wix2/preprocessor.htm Jarl -- Jarl Friis Softace ApS Omøgade 8, 2.sal 2100 København Ø. Denmark Phone: +45 26 13 20 90 E-mail: [EMAIL PROTECTED] LinkedIn: https://www.linkedin.com/in/jarlfriis - 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.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Error 1702
Hi list I went through the Windows Installer error texts and found out that some Errors are quite usefull. My question is: What should I do to rise such error? I know that I can create Custom Action type 19 but it will just display the text and exit the installation. For example: I need (some nasty request) to check some condition and rise dialog with text (and behaviour) similar to error 1702. (The installer must restart your system before configuration of [2] can continue. Click Yes to restart now or No if you plan to manually restart later.) Is all this possible? Thanks Stefan -- Stefan Pavlik | [EMAIL PROTECTED] Whitestein Technologies | www.whitestein.com Panenska 28 | SK-81103 Bratislava | Slovak Republic Tel +421(2)5930-0735 | Fax +421(2)5443-5512 - 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.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Problem creating shortcut
Hi, Thanks for your answer. Changing to [PROWCINI_PATH] didn't work at first glance, so after deeper investigations, I found the value returned by RegistrySearch wasn't correct. Changing attribute Type to "raw" (and removing $ sign before PROWCINI_PATH ! ) gives me a correct result. So I now have a working solution, but is it normal that using attribute Type="file" gives me an incorrect result (I get parent directory instead of file name) ? Best regards Gilles QUERRET -Message d'origine- De : Mike Dimmick [mailto:[EMAIL PROTECTED] Envoyé : mardi 3 octobre 2006 11:28 À : Gilles Querret; wix-users@lists.sourceforge.net Objet : RE: [WiX-users] Problem creating shortcut The $ symbol is used in the Target attribute to find a component's path. You need to evaluate the value of the property, so your Target should be [PROWCINI_PATH]. References: Shortcut table: http://msdn.microsoft.com/library/en-us/msi/setup/shortcut_table.asp Shortcut data type: http://msdn.microsoft.com/library/en-us/msi/setup/shortcut.asp Formatted data type: http://msdn.microsoft.com/library/en-us/msi/setup/formatted.asp -- Mike Dimmick -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gilles Querret Sent: 03 October 2006 08:06 To: 'wix-users@lists.sourceforge.net' Subject: [WiX-users] Problem creating shortcut [2nd try, first one never appeared on mailing list] Hi, I have a problem in my installer with creating shortcuts : basically, I need to create a shortcut where the executable isn't part of my installer and I just need to provide parameters. I retrieve the executable path using : And I add icon using : http://localhost/foo/bar>"/> Problem is that when running the installer, I get my icon created in desktop folder, but executable path isn't the value of PROWCINI_PATH, but to its parent directory. WiX help says for target attribute that the value will be defaulted to the parent File when nested under a File element. So how is it possible to create a shortcut using the correct executable path ? Best regards -- Gilles QUERRET - 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.php&p=sourceforge&CID=DEVDE V ___ 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.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] syncing many autogenerated files with wxs file
The tool Mallow should be able to help you (http://www.infozoom.de/download/Mallow.zip). This isn't part of WiX but you should be able to find the documentation and source for it with a bit of Googling. Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: 03 October 2006 11:29 To: wix-users@lists.sourceforge.net Subject: [WiX-users] syncing many autogenerated files with wxs file Hello, My project generates documentation with doxygen and docflex for its library, which consists of a number of classes, resulting in a large number of HTML files, spread over a directory structure. As I don't want to add each file individually to the installer by hand, I wonder if there is a way of automatically adding and maintaining these files HTML files and their related component GUIDs (because they might change rather quickly when I add/remove methods/classes etc.) Trouble is, the installer wxs file needs to be in sync with the automatically generated documentation HTML files) I thought of an automatically maintaned database of file/guid pairs for the documentation directories, but I'm not sure if that's the way to go. Does anyone have suggestions, or maybe even ready made solutions available for this? Cheers, Uwe -- Protect yourself from spam, use http://sneakemail.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.php&p=sourceforge&CID=DEVDE V ___ 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.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using a generated (by tallow.exe) fragment file in acomponent
Hi Mike. Thanks for the detailed answer (though it seems to drift off-topic). "Mike Dimmick" <[EMAIL PROTECTED]> writes: > Copy and paste into a .wxs file that describes your component, > underneath the appropriate element. Tallow is not > intended for use in automated build processes. :-( > You need to keep your GUIDs stable, so that you don't need to keep > generating the .reg file. You can do this either using the [Guid] > attribute on each class and interface, or the [ComCompatibleVersion] > attribute on the assembly. I planned to use Guid, however I find [ComCompatibleVersion] much more attractive. Any way it means, that whenver I make a new uncompatible version, I am forced to do manual brainless work (copy paste it into the appropriate element). I have expected to be able to avoid that for the standard reasons: It's time consuming. It does not require intelligence. It's error prone; In half-a-year, when I actually do make an uncompatible version; there is 90% chance that I forget the tallow.exe+copy/paste step and spend a full day, figuring out why the installation package is not working probably. > .NET, by default, computes the GUIDs to use from a hash of the > assembly identity (assembly name, version, culture, public key > token) and the class name. This means that when the version number > changes, the GUIDs also change. [ComCompatibleVersion] tells the > Framework to use a different version number in the hash calculation. When you write .NET, you probably mean: regasm.exe/tlbexp.exe, right? Jarl -- Jarl Friis Softace ApS Omøgade 8, 2.sal 2100 København Ø. Denmark Phone: +45 26 13 20 90 E-mail: [EMAIL PROTECTED] LinkedIn: https://www.linkedin.com/in/jarlfriis - 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.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] syncing many autogenerated files with wxs file
Hello, My project generates documentation with doxygen and docflex for its library, which consists of a number of classes, resulting in a large number of HTML files, spread over a directory structure. As I don't want to add each file individually to the installer by hand, I wonder if there is a way of automatically adding and maintaining these files HTML files and their related component GUIDs (because they might change rather quickly when I add/remove methods/classes etc.) Trouble is, the installer wxs file needs to be in sync with the automatically generated documentation HTML files) I thought of an automatically maintaned database of file/guid pairs for the documentation directories, but I'm not sure if that's the way to go. Does anyone have suggestions, or maybe even ready made solutions available for this? Cheers, Uwe -- Protect yourself from spam, use http://sneakemail.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.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix V3 UI image substitution
Right now, I don't think so. Look for "!(wix." in the .wxs files under src\ext\UIExtension\wixlib for other tunable variables in the UI. For 3.0.2015.0 this gives: Searching for: !(wix.Common.wxs(15): Common.wxs(16): Common.wxs(17): Common.wxs(18): Common.wxs(19): Common.wxs(20): LicenseAgreementDlg.wxs(29): WelcomeEulaDlg.wxs(35): Found 8 occurrence(s) in 3 file(s) -- Mike Dimmick From: Graham D. Ambrose [mailto:[EMAIL PROTECTED] Sent: 03 October 2006 09:51To: Mike Dimmick; wix-users@lists.sourceforge.netSubject: RE: [WiX-users] Wix V3 UI image substitution Thanks for the help Mike. I have a very pretty looking installer now. Is there any way to inspect what variables can be set with out looking through the source code? Graham From: Mike Dimmick [mailto:[EMAIL PROTECTED] Sent: 29 September 2006 17:33To: Mike Dimmick; Graham D. Ambrose; wix-users@lists.sourceforge.netSubject: RE: [WiX-users] Wix V3 UI image substitution Having downloaded the latest weekly (3.0.2128.0), I can confirm that this seems to work - setting -dWixUILicenseRtf=License.rtf caused it to be picked up and used in the MSI. -- Mike Dimmick From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike DimmickSent: 29 September 2006 17:26To: Graham D. Ambrose; wix-users@lists.sourceforge.netSubject: Re: [WiX-users] Wix V3 UI image substitution It looks like you need to add -dWixUILicenseRtf= to the light command line to change this variable. Right now I can't validate this as I have the 3.0.2015.0 version installed and I can't build the SampleUI tutorial (gets LGHT0132 errors complaining that nothing's a valid assembly, even though the Assembly attribute isn't specified, which appears to be a problem in the latest stable unstable version if that makes sense!) I worked this out by reading LicenseAgreementDlg.wxs in the source (in src\ext\UIExtension\wixlib) and working out how light actually processes these variables (it's in WixVariableResolver.ResolveVariables). Changing the bitmaps is more circuitous; the bitmaps use a from the (compiled) .wxl file that's embedded in the UIExtension. This sets each bitmap (marked 'overridable') to WixUI_Bmp_Banner. In Common.wxs (same folder as LicenseAgreementDlg.wxs) this is also set via a variable, to WixUIBannerBmp. Again, supply this on the command line to light, e.g. -dWixUIBannerBmp= As I say, this is guesswork. I hope it unsticks you. -- Mike Dimmick From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Graham D. AmbroseSent: 29 September 2006 09:23To: wix-users@lists.sourceforge.netSubject: [WiX-users] Wix V3 UI image substitution I am trying to customise the standard Wix UI by including our own licence file and branded backgrounds. I can not seem to be able to work out where to put my files in order to get them picked up. I am using Wix version 3 and are happily building using the WixUIExtension. But all the examples of replacing the images etc that I have found are using Wix V2 and the wixui.wixlib file and the paths they suggest do not seem to work. Can anyone explain how to achieve the substitution of the image files in WixUI Many Thanks, Graham - 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.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Problem creating shortcut
The $ symbol is used in the Target attribute to find a component's path. You need to evaluate the value of the property, so your Target should be [PROWCINI_PATH]. References: Shortcut table: http://msdn.microsoft.com/library/en-us/msi/setup/shortcut_table.asp Shortcut data type: http://msdn.microsoft.com/library/en-us/msi/setup/shortcut.asp Formatted data type: http://msdn.microsoft.com/library/en-us/msi/setup/formatted.asp -- Mike Dimmick -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gilles Querret Sent: 03 October 2006 08:06 To: 'wix-users@lists.sourceforge.net' Subject: [WiX-users] Problem creating shortcut [2nd try, first one never appeared on mailing list] Hi, I have a problem in my installer with creating shortcuts : basically, I need to create a shortcut where the executable isn't part of my installer and I just need to provide parameters. I retrieve the executable path using : And I add icon using : http://localhost/foo/bar>"/> Problem is that when running the installer, I get my icon created in desktop folder, but executable path isn't the value of PROWCINI_PATH, but to its parent directory. WiX help says for target attribute that the value will be defaulted to the parent File when nested under a File element. So how is it possible to create a shortcut using the correct executable path ? Best regards -- Gilles QUERRET - 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.php&p=sourceforge&CID=DEVDE V ___ 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.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Incorrect link on web
All the links down the right-hand side are broken when you're browsing the Manual section. On the Manual index page itself, http://wix.sourceforge.net/manual-wix2/wix_index.htm, all the links to other sites (WiX on SourceForge, Bug and Feature trackers, Rob and Justin's blogs) attempt to use relative URL syntax followed by a full HTTP URL. It looks like a global addition of '../' was done. I'm finding in IE7 RC1 that on pages under the manual section, the text for the links down the right-hand side appears, but they don't act as links. I'm not sure why this is since the relative links (to other pages on wix.sourceforge.net) on manual-wix2/wix_index.htm work correctly, and I can't see any differences in this section of the HTML using a diff tool. -- Mike Dimmick -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jarl Friis Sent: 03 October 2006 07:45 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Incorrect link on web On http://wix.sourceforge.net/manual-wix2/tools.htm The link to "WiX on sourceForge" is incorrect (it does not work). The fix is obvious. Jarl -- Jarl Friis Softace ApS Omøgade 8, 2.sal 2100 København Ø. Denmark Phone: +45 26 13 20 90 E-mail: [EMAIL PROTECTED] LinkedIn: https://www.linkedin.com/in/jarlfriis - 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.php&p=sourceforge&CID=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.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Using a generated (by tallow.exe) fragment file in acomponent
Copy and paste into a .wxs file that describes your component, underneath the appropriate element. Tallow is not intended for use in automated build processes. You need to keep your GUIDs stable, so that you don't need to keep generating the .reg file. You can do this either using the [Guid] attribute on each class and interface, or the [ComCompatibleVersion] attribute on the assembly. .NET, by default, computes the GUIDs to use from a hash of the assembly identity (assembly name, version, culture, public key token) and the class name. This means that when the version number changes, the GUIDs also change. [ComCompatibleVersion] tells the Framework to use a different version number in the hash calculation. -- Mike Dimmick -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jarl Friis Sent: 03 October 2006 08:24 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Using a generated (by tallow.exe) fragment file in acomponent Hi. I have started a versy small project (very close to SampleFirst.ZIP). However The build procedure is this: regasme.exe /regfile MyAssembly.dll generates a MyAssembly.reg file. The regfile is then processed by tallow.exe to produce a MyAssemblyRegistry.wxs file. I would like the registry entries in MyAssemblyRegistry.wxs to be part of a specific component in the MyProject.wxs file, namely the (COM TLB) component generated by a tlbexp.exe command. I don't see how the content of the generated MyAssemblyRegistry.wxs can be stuffed into a specific component of another wxs file. Jarl -- Jarl Friis Softace ApS Omøgade 8, 2.sal 2100 København Ø. Denmark Phone: +45 26 13 20 90 E-mail: [EMAIL PROTECTED] LinkedIn: https://www.linkedin.com/in/jarlfriis - 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.php&p=sourceforge&CID=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.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Upgrade and remove
Hi Bob, the package runs from the User Temp directory. The package code is changed. I think there are two problems: one - ADDLOCAL is not looking as expected when doing a typical install because it's set to everything. But the typical setup will actually install what I want. Maybe it's again some property update which takes place after a certain action. Please clarify this. Here is the log on a typical install: Action start 10:00:19: ExecuteAction. MSI (c) (F8:20) [10:00:19:859]: PROPERTY CHANGE: Adding SECONDSEQUENCE property. Its value is '1'. MSI (c) (F8:20) [10:00:19:859]: Grabbed execution mutex. MSI (c) (F8:20) [10:00:19:859]: Incrementing counter to disable shutdown. Counter after increment: 0 MSI (c) (F8:20) [10:00:19:859]: Switching to server: CLIENTUILEVEL="0" CLIENTPROCESSID="3576" SOURCEDIR="K:\DIS\adm\bin\Win_pkgs\rtm\src\bin\3.1.7\" ACTION="INSTALL" EXECUTEACTION="INSTALL" SETUPTYPE="Typical" ROOTDRIVE="E:\" INSTALLLEVEL="1" SECONDSEQUENCE="1" ADDLOCAL=Administration,Demos,Utilities It should be only Administration because the setup resets the level of all other features to 0 when "Typical" is selected like this: The second is that this ADDLOCAL property is stored somewhere (don't think it's in the registry because RegMon does not show anything) and when the update comes in, it will run with ADDLOCAL=Administration,Demos,Utilities. I tried to change ADDLOCAL after MigrateFeatureStates with a custom action, but it remains "Administration,Demos,Utilities" when ExecuteAction is called. Best regards, Calin Bob Arnson wrote: > Please keep /wix-users/ on the thread. > > Calin Iaru wrote: >>you're right. Now I need to find what is the cause of this >> problem. I always change the version and product code >> but somehow I get this message: >> MSI (s) (14:48) [17:39:13:796]: Skipping RemoveExistingProducts >> action: current configuration is maintenance mode or an uninstall > Do you also change package code? Elsewhere in the log, MSI reports > which .msi package is actually running; if it's under > %windir%\Installer, it's using an already-installed package. > > -- > sig://boB > http://bobs.org - 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.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix V3 UI image substitution
Thanks for the help Mike. I have a very pretty looking installer now. Is there any way to inspect what variables can be set with out looking through the source code? Graham From: Mike Dimmick [mailto:[EMAIL PROTECTED] Sent: 29 September 2006 17:33 To: Mike Dimmick; Graham D. Ambrose; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Wix V3 UI image substitution Having downloaded the latest weekly (3.0.2128.0), I can confirm that this seems to work - setting -dWixUILicenseRtf=License.rtf caused it to be picked up and used in the MSI. -- Mike Dimmick From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Dimmick Sent: 29 September 2006 17:26 To: Graham D. Ambrose; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Wix V3 UI image substitution It looks like you need to add -dWixUILicenseRtf= to the light command line to change this variable. Right now I can't validate this as I have the 3.0.2015.0 version installed and I can't build the SampleUI tutorial (gets LGHT0132 errors complaining that nothing's a valid assembly, even though the Assembly attribute isn't specified, which appears to be a problem in the latest stable unstable version if that makes sense!) I worked this out by reading LicenseAgreementDlg.wxs in the source (in src\ext\UIExtension\wixlib) and working out how light actually processes these variables (it's in WixVariableResolver.ResolveVariables). Changing the bitmaps is more circuitous; the bitmaps use a from the (compiled) .wxl file that's embedded in the UIExtension. This sets each bitmap (marked 'overridable') to WixUI_Bmp_Banner. In Common.wxs (same folder as LicenseAgreementDlg.wxs) this is also set via a variable, to WixUIBannerBmp. Again, supply this on the command line to light, e.g. -dWixUIBannerBmp= As I say, this is guesswork. I hope it unsticks you. -- Mike Dimmick From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Graham D. Ambrose Sent: 29 September 2006 09:23 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Wix V3 UI image substitution I am trying to customise the standard Wix UI by including our own licence file and branded backgrounds. I can not seem to be able to work out where to put my files in order to get them picked up. I am using Wix version 3 and are happily building using the WixUIExtension. But all the examples of replacing the images etc that I have found are using Wix V2 and the wixui.wixlib file and the paths they suggest do not seem to work. Can anyone explain how to achieve the substitution of the image files in WixUI Many Thanks, Graham - 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.php&p=sourceforge&CID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Using a generated (by tallow.exe) fragment file in a component
Hi. I have started a versy small project (very close to SampleFirst.ZIP). However The build procedure is this: regasme.exe /regfile MyAssembly.dll generates a MyAssembly.reg file. The regfile is then processed by tallow.exe to produce a MyAssemblyRegistry.wxs file. I would like the registry entries in MyAssemblyRegistry.wxs to be part of a specific component in the MyProject.wxs file, namely the (COM TLB) component generated by a tlbexp.exe command. I don't see how the content of the generated MyAssemblyRegistry.wxs can be stuffed into a specific component of another wxs file. Jarl -- Jarl Friis Softace ApS Omøgade 8, 2.sal 2100 København Ø. Denmark Phone: +45 26 13 20 90 E-mail: [EMAIL PROTECTED] LinkedIn: https://www.linkedin.com/in/jarlfriis - 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.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Problem creating shortcut
[2nd try, first one never appeared on mailing list] Hi, I have a problem in my installer with creating shortcuts : basically, I need to create a shortcut where the executable isn't part of my installer and I just need to provide parameters. I retrieve the executable path using : And I add icon using : http://localhost/foo/bar>"/> Problem is that when running the installer, I get my icon created in desktop folder, but executable path isn't the value of PROWCINI_PATH, but to its parent directory. WiX help says for target attribute that the value will be defaulted to the parent File when nested under a File element. So how is it possible to create a shortcut using the correct executable path ? Best regards -- Gilles QUERRET - 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.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Tool for converting reg file to WiX content.
Bob Arnson <[EMAIL PROTECTED]> writes: > Jarl Friis wrote: >> Maybe, but it is not installed when installing the Wix3.msi (latest >> weekly build). Is that intentional? >> > Tallow is a WiX v2 > tool. Its replacement is > Heat in WiX v3 but it > doesn't currently > support .reg translation. Thank you very much. Jarl -- Jarl Friis Softace ApS Omøgade 8, 2.sal 2100 København Ø. Denmark Phone: +45 26 13 20 90 E-mail: [EMAIL PROTECTED] LinkedIn: https://www.linkedin.com/in/jarlfriis - 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.php&p=sourceforge&CID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
