Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding?
Thanks for the advice. I didn't actually mean to say commercial, I was more meaning that I've downloaded msi's from various sources - some commercial, some open source, ... and the vast majority of them haven't required me to either use msiexec or uninstall the previous version. I'm just trying to keep things as simple as possible. In the case of this installer, it's relatively unlikely that any individual developers will create a private build of the installer and install it, and the way I've got it set up at the moment it would end up with a version number 0.0.0.0. I'll have a think about it at the moment, but I think we should be ok using a wildcard. The only other thing that I can think of at the moment is having the build process generate the guid, but I'm avoiding that for the moment. Thanks for the advice. Adam -Original Message- From: Ian Elliott (Excell Data Corporation) [mailto:[EMAIL PROTECTED] Sent: 09 October 2008 19:24 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding? There is one side effect that I can think of (and have experienced) during daily development. Say your build version number changes once per day. Everything will work fine if you only attempt to install today's version over yesterday's version. Now, if you are developing and build multiple private builds during the day, there can be a problem. If you use the wix wildcard to auto generate productID's you will have those id's changing and the version number doesn't change. When people blindly try to install one private build over another you get weird things happening. It's been awhile and I can't remember exactly what the deal was but I do remember going to many machines to fix things. >From earlier in the thread, "Otherwise it forces the user to uninstall the previous version before installing the new version - something that I've never had to do with any serious commercial package." Most serious commercial packages that I can think of actually use some kind of setup.exe bootstrapper. I have never purchased any boxed software, for example, and launched an msi directly. The setup.exe can detect if a minor upgrade needs to be launched and adjust the command line accordingly. -Original Message- From: Adam Connelly [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2008 5:46 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding? I'm keen to avoid doing that since it means creating the bootstrapper. It just doesn't seem quite right to me to have to do that. Thanks for the suggestion, but I think for now I'll stick to changing the product Id. Do you know if there's any undesirable side effects to doing this? Cheers, Adam -Original Message- From: John Hall [mailto:[EMAIL PROTECTED] Sent: 08 October 2008 18:22 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding? > The only way I've got this to work at the moment is by > manually changing the Product Id and checking it in before > doing a publish to avoid the annoying "another version of > this product is already installed..." message. Otherwise it > forces the user to uninstall the previous version before > installing the new version - something that I've never had to > do with any serious commercial package. > > Is what I'm doing wrong, and if so what alternatives do I have? You could do minor upgrades for your nightly builds - this requires passing REINSTALLMODE=vomus on the msiexec commandline, so would probably require being wrapped in a bootstrapper. Regards, John - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users
Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding?
I'm keen to avoid doing that since it means creating the bootstrapper. It just doesn't seem quite right to me to have to do that. Thanks for the suggestion, but I think for now I'll stick to changing the product Id. Do you know if there's any undesirable side effects to doing this? Cheers, Adam -Original Message- From: John Hall [mailto:[EMAIL PROTECTED] Sent: 08 October 2008 18:22 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding? > The only way I've got this to work at the moment is by > manually changing the Product Id and checking it in before > doing a publish to avoid the annoying "another version of > this product is already installed..." message. Otherwise it > forces the user to uninstall the previous version before > installing the new version - something that I've never had to > do with any serious commercial package. > > Is what I'm doing wrong, and if so what alternatives do I have? You could do minor upgrades for your nightly builds - this requires passing REINSTALLMODE=vomus on the msiexec commandline, so would probably require being wrapped in a bootstrapper. Regards, John - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding?
I thought about that, but I thought you were meant to keep track of the product Id for some reason (something I've not looked into). I might just do it though in the absence of any better way. Adam -Original Message- From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: 08 October 2008 18:04 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding? Product/@Id="*" -Original Message----- From: Adam Connelly [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 08, 2008 06:24 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding? The project I'm working on at the moment uses a build server to automatically build our installers, etc. As part of this, it provides the version number to the installer. Therefore, every publish we do (and in fact every checkin of source) is a different version of the product. This means that ideally I'd be able to take any published msi and install it, and it should have the correct install / upgrade behaviour without us having to manually alter the wxs files at all (fair enough it also means we have to distribute every file every time, but I'm not worried about that at the moment). The only way I've got this to work at the moment is by manually changing the Product Id and checking it in before doing a publish to avoid the annoying "another version of this product is already installed..." message. Otherwise it forces the user to uninstall the previous version before installing the new version - something that I've never had to do with any serious commercial package. Is what I'm doing wrong, and if so what alternatives do I have? Cheers, Adam -Original Message- From: polan [mailto:[EMAIL PROTECTED] Sent: 08 October 2008 11:39 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding? Thx for the answer Ian Elliott (Excell Data Corporation) wrote: > > For the minor upgrade and small update you don't make use of the Update > tag at all. > Ok - lets stick to minor upgrade. I don't insert the upgrade tag, I change the package guid, and version. I run the installation msiexec /i ExampleInstaller.msi REINSTALALL=ALL REINSTALLMODE=vomus And i get stuck at maintenance dialog instead of getting normal installation. What's possibly wrong? Or maybe it is just the way that minor upgrade works? (couldn't think of the good reason) The other question is - if I get through it, will the minor upgrade override the files with new versions? I enclose a file with the source (it is a very simple and short one) http://n2.nabble.com/file/n1306236/Product.wxs Product.wxs Ian Elliott (Excell Data Corporation) wrote: > > Also, you listed below that the package guid didn't change for one > scenario. You should always have a different package guid for every > package built. > My mistake of course - it was supposed to be written like you say. I did it this way, just described it wrong. -- View this message in context: http://n2.nabble.com/How-Update---Upgrade-strategy-%28small%2C-minor%2C-major%29-affect-file-overriding--tp1304357p1306236.html Sent from the wix-users mailing list archive at Nabble.com. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___
Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding?
The project I'm working on at the moment uses a build server to automatically build our installers, etc. As part of this, it provides the version number to the installer. Therefore, every publish we do (and in fact every checkin of source) is a different version of the product. This means that ideally I'd be able to take any published msi and install it, and it should have the correct install / upgrade behaviour without us having to manually alter the wxs files at all (fair enough it also means we have to distribute every file every time, but I'm not worried about that at the moment). The only way I've got this to work at the moment is by manually changing the Product Id and checking it in before doing a publish to avoid the annoying "another version of this product is already installed..." message. Otherwise it forces the user to uninstall the previous version before installing the new version - something that I've never had to do with any serious commercial package. Is what I'm doing wrong, and if so what alternatives do I have? Cheers, Adam -Original Message- From: polan [mailto:[EMAIL PROTECTED] Sent: 08 October 2008 11:39 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How Update / Upgrade strategy (small, minor, major) affect file overriding? Thx for the answer Ian Elliott (Excell Data Corporation) wrote: > > For the minor upgrade and small update you don't make use of the Update > tag at all. > Ok - lets stick to minor upgrade. I don't insert the upgrade tag, I change the package guid, and version. I run the installation msiexec /i ExampleInstaller.msi REINSTALALL=ALL REINSTALLMODE=vomus And i get stuck at maintenance dialog instead of getting normal installation. What's possibly wrong? Or maybe it is just the way that minor upgrade works? (couldn't think of the good reason) The other question is - if I get through it, will the minor upgrade override the files with new versions? I enclose a file with the source (it is a very simple and short one) http://n2.nabble.com/file/n1306236/Product.wxs Product.wxs Ian Elliott (Excell Data Corporation) wrote: > > Also, you listed below that the package guid didn't change for one > scenario. You should always have a different package guid for every > package built. > My mistake of course - it was supposed to be written like you say. I did it this way, just described it wrong. -- View this message in context: http://n2.nabble.com/How-Update---Upgrade-strategy-%28small%2C-minor%2C-major%29-affect-file-overriding--tp1304357p1306236.html Sent from the wix-users mailing list archive at Nabble.com. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Basing a dialog sequence on WixUI_Minimal
Hi, I'm building an installer and it was going good until I wanted to add a new dialog. I now want my installer to be able to install some "extensions" into a third party application directory, and therefore want to have a dialog that allows users to specify the installation directory. I'm using Votive with VS2008, and I've added two new file to my project "ChooseDirectoriesDialog.wxs" and "WixUI_MyUI.wxs". In the _MyUI one I have the following code (that's basically a copy of WixUI_Minimal): http://schemas.microsoft.com/wix/2006/wi";> 1 1 1 1 1 1 1 1 1 I'm now getting the following error when I try to build: error LGHT0204: ICE03: Not a valid foreign key; Table: ControlEvent, Column: Control_, Key(s): WelcomeEulaDlg.Next.NewDialog.ChooseDirectoriesDlg.1 I'm obviously doing something wrong, and I'm pretty certain that the code above isn't right - I just couldn't quite figure out what was going on in the minimal.wxs file (since it seems to be totally different to any examples I've seen). Cheers, Adam - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Database selection dialog
Thanks for the reply. When you talk about staying away from a scripted solution, can you elaborate on what you mean? Also, how does the windows installer UI fit into all of this? Do I make a custom action that pops up a window, or is there some way that I can embed controls into the installer UI? I should be able to use DTF stuff, but if not I don't have much problem pissing about with C++ (although I'd prefer to avoid that :P) Sorry if I'm asking obvious questions - I'm new to Wix, and I couldn't find much documentation on v3. Cheers, Adam -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Karper Sent: 18 August 2008 15:13 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Database selection dialog I see this question a lot out here, and this was actually the very first thing that brought me to this group. There is nothing built in to facilitate this, and you will need to use a CA to get it done. However, since so many people have implemented it before, you may be able to find something out on the intarwebs. I would suggest staying away from the scripted solutions. If your program already has a .NET dependency, then you can use a simple DTF CA to solve this problem (as I did). If not, then you'll want to find a native C++ CA that does the trick. I don't specifically know of anything posted online right now, but if you need any help, let me know and I'll do what I can. Chris On Mon, Aug 18, 2008 at 9:33 AM, Adam Connelly < [EMAIL PROTECTED]> wrote: > Hi, > > Just wondering if Wix has anything built in that allows a user to select an > Sql server database (with windows / sql authentication, etc). I'm sure I've > seen this in installs before (something similar to the connect dialog in > management studio). > > If not, I take it that I have to write something myself? If that's the > case, any chance someone could point me in the right direction. > > I'm using Wix v3. > > Cheers, > Adam > - > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Database selection dialog
Hi, Just wondering if Wix has anything built in that allows a user to select an Sql server database (with windows / sql authentication, etc). I'm sure I've seen this in installs before (something similar to the connect dialog in management studio). If not, I take it that I have to write something myself? If that's the case, any chance someone could point me in the right direction. I'm using Wix v3. Cheers, Adam - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Automatically setting version number
Thanks for the replies. I ended up using a wix pre-processor directive, like Neil suggested. I had to write a msbuild task to set the environment variable if it's not already set, however, since on a dev machine the variable would not normally be set (i.e. it's the build server that sets it), and this was causing the candle to squeal. Cheers, Adam -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Karper Sent: 18 July 2008 13:41 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Automatically setting version number I write an msbuild action, but I have lot's of custom activity, so I have a .targets file of my own that I include in my new projects. That makes it easier to remember, and quick to fix once I find it missing. I like your $(var) method though. Chris On Fri, Jul 18, 2008 at 6:48 AM, Neil Sleightholm <[EMAIL PROTECTED]> wrote: > 1. I think it is ok but Windows Installer will ignore the 4th part. > > 2. I pass the version in on the candle command line and use code like this > in the wxs file: > > > > > > > > > Neil > > Neil Sleightholm > X2 Systems Limited > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > > > > From: [EMAIL PROTECTED] on behalf of Adam Connelly > Sent: Fri 18/07/2008 11:30 > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Automatically setting version number > > > > Hi, > > I've got a CI setup that automatically generates a x.x.x.x style version > number. I've got all my assemblies versioned properly (with a generated > shared SolutionInfo.cs file), and I set the msi output name as > MyMSI-x.x.x.x.msi and now I want to set the Version attribute of the Product > tag. Two questions: > > > 1) Is it ok to put a four digit version number in here? > > 2) How would you recommend I set the version, bearing in mind I get my > version number from a $(build_number) environment variable? > > I was thinking of modifying the project file and shoving a msbuild task > that edits the Product.wxs in, but if possible I'd like to avoid modifying > project files since it would probably be quite easy to forget to do when > setting up new projects. > > Thanks, > Adam > - > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > - > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > ___ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Automatically setting version number
Hi, I've got a CI setup that automatically generates a x.x.x.x style version number. I've got all my assemblies versioned properly (with a generated shared SolutionInfo.cs file), and I set the msi output name as MyMSI-x.x.x.x.msi and now I want to set the Version attribute of the Product tag. Two questions: 1) Is it ok to put a four digit version number in here? 2) How would you recommend I set the version, bearing in mind I get my version number from a $(build_number) environment variable? I was thinking of modifying the project file and shoving a msbuild task that edits the Product.wxs in, but if possible I'd like to avoid modifying project files since it would probably be quite easy to forget to do when setting up new projects. Thanks, Adam - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix and MSBuild
Thanks a lot for the replies. I'm hitting myself on the head - just 5 minutes before reading both replies I had given up with the hand-editing and added a Wix project. So I now have exactly what Christopher recommended :P I created a separate Solution configuration that just builds Wix projects (i.e. the only one I have at the moment), then just use the MSBuild task in my build file to build them. Does that sound sensible or have I overcomplicated things? Anyhow, thanks again - everything's working. Adam -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Enns Sent: 17 July 2008 15:14 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wix and MSBuild Adam, WiX ships with complete MSBuild support through a set of tasks and targets, there's no need to try and hand-edit things. Do you have Visual Studio installed? If so, create a new Visual Studio project and look for a WiX node in the new project dialog. Create that, add the contents of your existing ProjA.wxs to the .wxs file that's created, and build. Voila! Neil From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Adam Connelly [EMAIL PROTECTED] Sent: Thursday, July 17, 2008 6:29 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wix and MSBuild I actually sorted the problem (a typo :(). I would still be interested to find out how others structure their projects. Adam -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adam Connelly Sent: 17 July 2008 11:19 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Wix and MSBuild Hi, I currently trying to add a task into my MSBuild file that will create the various MSI files needed for the project. I've got the following file structure: Root/ Build.xml Code/ Deploy/ ProjA ProjB Installs/ ProjA.wxs Sorry if that's not amazingly clear. Basically, all the assemblies, etc for each project are in Code/Deploy/ProjX, and the wix file is in Installs/ProjX.wxs. I want to be able to build an installer while keeping this structure if possible. The problem I'm having is that although candle.exe runs fine, light.exe can't seem to find the source files no-matter if I set the -b switch, or if I alter the Source attributes in the wxs file. I guess what I really want to know is how do other people structure their builds when there may be multiple projects needing installers built, etc. Sorry for such a broad question. Cheers, Adam - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Wix and MSBuild
I actually sorted the problem (a typo :(). I would still be interested to find out how others structure their projects. Adam -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adam Connelly Sent: 17 July 2008 11:19 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Wix and MSBuild Hi, I currently trying to add a task into my MSBuild file that will create the various MSI files needed for the project. I've got the following file structure: Root/ Build.xml Code/ Deploy/ ProjA ProjB Installs/ ProjA.wxs Sorry if that's not amazingly clear. Basically, all the assemblies, etc for each project are in Code/Deploy/ProjX, and the wix file is in Installs/ProjX.wxs. I want to be able to build an installer while keeping this structure if possible. The problem I'm having is that although candle.exe runs fine, light.exe can't seem to find the source files no-matter if I set the -b switch, or if I alter the Source attributes in the wxs file. I guess what I really want to know is how do other people structure their builds when there may be multiple projects needing installers built, etc. Sorry for such a broad question. Cheers, Adam - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Wix and MSBuild
Hi, I currently trying to add a task into my MSBuild file that will create the various MSI files needed for the project. I've got the following file structure: Root/ Build.xml Code/ Deploy/ ProjA ProjB Installs/ ProjA.wxs Sorry if that's not amazingly clear. Basically, all the assemblies, etc for each project are in Code/Deploy/ProjX, and the wix file is in Installs/ProjX.wxs. I want to be able to build an installer while keeping this structure if possible. The problem I'm having is that although candle.exe runs fine, light.exe can't seem to find the source files no-matter if I set the -b switch, or if I alter the Source attributes in the wxs file. I guess what I really want to know is how do other people structure their builds when there may be multiple projects needing installers built, etc. Sorry for such a broad question. Cheers, Adam - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
