Re: [WiX-users] Tallow from WiX 2.0.5112.0 is generating deprecated wxs file
The bug is opened. http://sourceforge.net/tracker/index.php?func=detailaid=1680395group_id=105970atid=642714 -- Stefan Pavlik | [EMAIL PROTECTED] Whitestein Technologies s.r.o. | www.whitestein.com Panenska 28 | 811 03 Bratislava | Slovak Republic Main +421 2 5443-5502 | Direct +421 2 5930-0735 - 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] Checkbox -- Desktop Shortcut
Hello all, I'm just trying to learn WiX so please excuse me for presenting a question which has apparently been answered on this list. I just have difficulties to understand those examples. My problem is as follows: I create a setup using VS2003. The installation has a dialog presenting a checkbox Create a desktop shortcut. This works as expected when setup.msi created by VS2003 is executed. Then I decompile this msi using dark, make some changes (translate texts), compile and link my wxs file to get a modified msi. The checkbox appears on the dialog where I put it, but it can't be checked. It is enabled I guess cause it flashes when clicked on. It appears to me that dark (?) is somehow messing with this shortcut thing, but I can't figure out what's happening? Has anybody any clue where the problem might be or does anybody know an example simple enough for a newbie to get grasp on this thing? TIA Lasse - 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] COM registration
Hi, I'm a new user of wix. I'm trying to convert a setup made with Package and Deployment Wizard of visual studio 6. This setup use some self register dll and some shared dll wich are in the system32 directory. Currently, I'm using tallow to generate registry keys of self register dll. And I just copy shared dll in the system32 directory. But I'm not sure if it's the best way to install those components. Could you help me? Thank you. - 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] Adding a merge module or is it a merge module?
Hello, I wanted to add a merge module provided within an sdk from Macrovision: Merge Id=DA8678BD-69FF-4272-9C6B-BF0471E52F46 Language=1033 src=Binary\installdir\isus.msm DiskId=1 / and also added MergeRef Id=DA8678BD-69FF-4272-9C6B-BF0471E52F46/ in a feature. But the mergemodule isn't installed. So I darked the msm: ?xml version=1.0 encoding=utf-8? Wix xmlns=http://schemas.microsoft.com/wix/2003/01/wi; Product Package Id=DA8678BD-69FF-4272-9C6B-BF0471E52F46 Keywords=MergeModule,MSI,Database Description=Macrovision Software Manager Comments=This will install the Macrovision Software Manager and register your application with it. Manufacturer=Macrovision Corporation InstallerVersion=200 Platforms=Intel Languages=1033 SummaryCodepage=1252 / Property Id=IE4FOUND This doesn't look like a merge module;), although they provide it as merge module. So how could I add this package to my product? Regards, Gerald _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ - 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] Checkbox -- Desktop Shortcut
Dark has never been a proper decompiler. It works for the most part, but it's basically in there so you can open up existing MSIs and find out what's going on as a starting point. The WiX team have always said that you shouldn't expect a dark'd MSI to compile. Rob Lasse Rantanen wrote: Hello all, I'm just trying to learn WiX so please excuse me for presenting a question which has apparently been answered on this list. I just have difficulties to understand those examples. My problem is as follows: I create a setup using VS2003. The installation has a dialog presenting a checkbox Create a desktop shortcut. This works as expected when setup.msi created by VS2003 is executed. Then I decompile this msi using dark, make some changes (translate texts), compile and link my wxs file to get a modified msi. The checkbox appears on the dialog where I put it, but it can't be checked. It is enabled I guess cause it flashes when clicked on. It appears to me that dark (?) is somehow messing with this shortcut thing, but I can't figure out what's happening? Has anybody any clue where the problem might be or does anybody know an example simple enough for a newbie to get grasp on this thing? TIA Lasse - 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 - 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] COM registration
Is the DLL shared just between your products or with other parts of the system? You're not really meant to put things in the system32 folder. Rob Jacquet Fabian wrote: Hi, I'm a new user of wix. I'm trying to convert a setup made with Package and Deployment Wizard of visual studio 6. This setup use some self register dll and some shared dll wich are in the system32 directory. Currently, I'm using tallow to generate registry keys of self register dll. And I just copy shared dll in the system32 directory. But I'm not sure if it's the best way to install those components. Could you help me? Thank you. - 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] COM registration[Scanned]
I'm guessing that Jacquet's app is written in VB6 and probably uses some DLLs that Microsoft provide. In which case, the files probably should go in system32, as they may already be installed... I'm in a similar situation - preparing to write my first WiX install, for a VB6 app. I'm guessing there's an msm out there somewhere to install the VB runtime files? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Hamflett Sent: 14 March 2007 09:40 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] COM registration[Scanned] Is the DLL shared just between your products or with other parts of the system? You're not really meant to put things in the system32 folder. Rob Jacquet Fabian wrote: Hi, I'm a new user of wix. I'm trying to convert a setup made with Package and Deployment Wizard of visual studio 6. This setup use some self register dll and some shared dll wich are in the system32 directory. Currently, I'm using tallow to generate registry keys of self register dll. And I just copy shared dll in the system32 directory. But I'm not sure if it's the best way to install those components. Could you help me? Thank you. - 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=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.phpp=sourceforgeCID=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.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Checkbox -- Desktop Shortcut
OK, Thank you Rob - everyday you learn something. So I forget this approach. Lasse - 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] RE : COM registration[Scanned]
It's exact. I have to install the VB6fr.dll which is the vb runtime. I discover I have another problem too. I have to register an activeX which is a .exe Could I do this with tallow? -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Thomas Leigh Envoyé : mercredi 14 mars 2007 11:01 À : wix-users@lists.sourceforge.net Objet : Re: [WiX-users] COM registration[Scanned] I'm guessing that Jacquet's app is written in VB6 and probably uses some DLLs that Microsoft provide. In which case, the files probably should go in system32, as they may already be installed... I'm in a similar situation - preparing to write my first WiX install, for a VB6 app. I'm guessing there's an msm out there somewhere to install the VB runtime files? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Hamflett Sent: 14 March 2007 09:40 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] COM registration[Scanned] Is the DLL shared just between your products or with other parts of the system? You're not really meant to put things in the system32 folder. Rob Jacquet Fabian wrote: Hi, I'm a new user of wix. I'm trying to convert a setup made with Package and Deployment Wizard of visual studio 6. This setup use some self register dll and some shared dll wich are in the system32 directory. Currently, I'm using tallow to generate registry keys of self register dll. And I just copy shared dll in the system32 directory. But I'm not sure if it's the best way to install those components. Could you help me? Thank you. - 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=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.phpp=sourceforgeCID=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.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] Heat. Can it not generate registry entries?
Also Is there a reason that each file is in its own fragment? That really isn't that big of deal I guess, it just seems like it would be easier to read if they were grouped together. That's the default; you can override it with -sfrag. The advantage of many fragments is that each is separately linkable. Sorry if these is are stupid questions, but if there are better ways to do things than the way I am currently, I'm quite interested in learning them. Linkable to what? If you link in the fragment do you still have to make the component reference? What is the advantage of having them separately linkable? From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Friday, March 09, 2007 11:48 AM To: Scott Sam Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Heat. Can it not generate registry entries? Scott Sam wrote: Thanks that is exactly what I was looking for. Is there somewhere I could look to find all of the various switches for heat? The ultimate documentation: src\ext\UtilExtension\wixext\UtilHeatExtension.cs.g Also Is there a reason that each file is in its own fragment? That really isn't that big of deal I guess, it just seems like it would be easier to read if they were grouped together. That's the default; you can override it with -sfrag. The advantage of many fragments is that each is separately linkable. -- 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.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat. Can it not generate registry entries?
Scott Sam wrote: Sorry if these is are stupid questions, but if there are better ways to do things than the way I am currently, I'm quite interested in learning them. Linkable to what? If you link in the fragment do you still have to make the component reference? What is the advantage of having them separately linkable? The linker (light) always links in the entire fragment of anything you reference. So if you have a fragment with 100 components and you ComponentRef one of them, the entire fragment of 100 components is linked in. If you want more control, use a small fragment. I'm not sure it makes sense as the default for heat; in fact, I added some code recently that, when the -sfrag switch is passed, creates a ComponentGroup for every component, so you don't have to ComponentRef every single component. -- 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.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat. Can it not generate registry entries?
Thanks for answering my questions. That makes sense now. Heat creating the componentgroup would be very helpful to me. What version/build is it in? From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 14, 2007 10:53 AM To: Scott Sam Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Heat. Can it not generate registry entries? Scott Sam wrote: Sorry if these is are stupid questions, but if there are better ways to do things than the way I am currently, I'm quite interested in learning them. Linkable to what? If you link in the fragment do you still have to make the component reference? What is the advantage of having them separately linkable? The linker (light) always links in the entire fragment of anything you reference. So if you have a fragment with 100 components and you ComponentRef one of them, the entire fragment of 100 components is linked in. If you want more control, use a small fragment. I'm not sure it makes sense as the default for heat; in fact, I added some code recently that, when the -sfrag switch is passed, creates a ComponentGroup for every component, so you don't have to ComponentRef every single component. -- 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.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Shared files question?
In our product, we have a bunch of features that are usually all installed on the same machine, but were designed to be able to be installed as stand alone programs on separate machines. As a result, there are a bunch of files that are shared between the different features. Currently I have all of the files for each feature installed with that feature, just in case they are installed on separate machines. This leaves me with a lot of duplicate files in the installation. I'm am getting ICE errors about it, but I am currently ignoring them. What is the best way to do this? My first thought was to put all of the common files in one feature and install them all of the time. The problem is that some files are common to two features, but not the rest. We don't want to be installing any extra files, if we don't have to. I'm using wix v3 with votive and vs2005. http://www.clearviewecm.com/ The information contained in this email is privileged and confidential and is intended solely for the addressee(s). If you are not the intended recipient, please respond to [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] then delete this email from your system. image001.png Description: image001.png - 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] Shared files question?
Put any components that can be shared into a shared folder. The just list the required components under whichever features need them. It's OK to have components under multiple features. Windows Installer will take care of it for you. Rob Scott Sam wrote: In our product, we have a bunch of features that are usually all installed on the same machine, but were designed to be able to be installed as stand alone programs on separate machines. As a result, there are a bunch of files that are shared between the different features. Currently I have all of the files for each feature installed with that feature, just in case they are installed on separate machines. This leaves me with a lot of duplicate files in the installation. I’m am getting ICE errors about it, but I am currently ignoring them. What is the best way to do this? My first thought was to put all of the common files in one feature and install them all of the time. The problem is that some files are common to two features, but not the rest. We don’t want to be installing any extra files, if we don’t have to. I’m using wix v3 with votive and vs2005. Sam_CVsig.png http://www.clearviewecm.com/ The information contained in this email is privileged and confidential and is intended solely for the addressee(s). If you are not the intended recipient, please respond to [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] then delete this email from your system. - 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] Shared files question?
Scott, If I understand you correctly, you are saying that you currently have the same source file included in multiple components. Is that right? If so, presumably there is something stopping you from putting the file(s) in as many components as you need and including a ComponentRef to it/them in your feature(s). What is that? My guess would be that the shared files have to be installed in the same folder as the application, and since the applications can be installed stand-alone (presumably each into their own folder) you may need the same file in more than one place. Am I on the right track so far? Regards, Richard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam Sent: Wednesday, March 14, 2007 11:12 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Shared files question? In our product, we have a bunch of features that are usually all installed on the same machine, but were designed to be able to be installed as stand alone programs on separate machines. As a result, there are a bunch of files that are shared between the different features. Currently I have all of the files for each feature installed with that feature, just in case they are installed on separate machines. This leaves me with a lot of duplicate files in the installation. I'm am getting ICE errors about it, but I am currently ignoring them. What is the best way to do this? My first thought was to put all of the common files in one feature and install them all of the time. The problem is that some files are common to two features, but not the rest. We don't want to be installing any extra files, if we don't have to. I'm using wix v3 with votive and vs2005. http://www.clearviewecm.com/ The information contained in this email is privileged and confidential and is intended solely for the addressee(s). If you are not the intended recipient, please respond to [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] then delete this email from your system. * C O N F I D E N T I A L I T Y N O T I C E * --- The content of this e-mail is intended solely for the use of the individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited. Peek Traffic Corporation is neither liable for the contents, nor for the proper, complete and timely transmission of (the information contained in) this communication. If you have received this communication in error, please notify the author by replying to this e-mail immediately and delete the material from any computer. attachment: image001.jpg - 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] Votive v3 and UI and a library question
Thanks Justin-something else that I just noticed was that if you're working with a library project, you can't add a reference to it in an installer: you need to reference the compiled wixlib directly. This works, but if it's possible to reference the project directly (so the linker will use the current IDE configuration's version) it might make more sense. Actually, another thing that came up when working with libraries was binary files for a GUI (bitmaps etc). Is there not a way to embed bitmaps in the wxl library? I've added a bitmap with the Binary tag and built the library, but then the Wix project that links against this library needs to contain the bitmap. I'd like to have the graphics carried with the library (ideally overrideable), the same way that strings are. Is there documentation somewhere that explains how to do this? Thanks again for the help. Chris From: Justin Rockwood [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 13, 2007 4:04 PM To: Chris Bardon; Ashman, Jared; Levi Wilson; Simon Dahlbacka Cc: wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Votive v3 and UI Good points. I don't necessarily like defaulting to en-US, just because WiX is being used quite heavily in other locales (German, Russian, and Dutch are ones that come to mind). However, defaulting to the OS culture makes a lot of sense. Let me know if you have any other suggestions as you dig more into your project. Thanks, Justin From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Bardon Sent: Tuesday, March 13, 2007 10:41 AM To: Ashman, Jared; Levi Wilson; Simon Dahlbacka Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Votive v3 and UI Ah, that did it, thanks. Probably just a bug with the settings not being saved in both cases. I know I've done the same thing more than once. As for Justin's question, the only thing I can think of off the top of my head is to at least automatically define the en-US culture when adding the reference to the UI DLL. If nothing else, this will mean that anyone who wants to compile to en-US will be able to do so without digging through properties, and others will be able to find the culture settings if they need to. Picking up the automatically included culture from the OS could also be an option, as would automatically including at least one culture in the properties, and then ignoring it if it's not needed (i.e. not compiling with the DLL). I'll see what else I come up with as I start venturing into more custom UI along the way (which I suspect will introduce a bunch of new questions). Chris From: Ashman, Jared [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 13, 2007 1:28 PM To: Chris Bardon; Levi Wilson; Simon Dahlbacka Cc: wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Votive v3 and UI Chris, If you add the en-US to the field, then open the advanced properties below that, then save, it does save the culture. The important step is the advanced properties for some reason. Jared M. Ashman [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Bardon Sent: Tuesday, March 13, 2007 11:39 AM To: Levi Wilson; Simon Dahlbacka Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Votive v3 and UI I noticed that field, but adding a culture value to it doesn't appear to do anything. I tried en-US, en-US;, and even the example en-US;ja-JP listed below the textbox, and I still got the same errors. Adding the wxs file directly seems to be the only thing that works. From: Levi Wilson [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 13, 2007 12:35 PM To: Simon Dahlbacka Cc: Chris Bardon; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Votive v3 and UI Maybe that's what it was...that it was TOO easy :-) I usually miss those. On 3/13/07, Simon Dahlbacka [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Yes, (at least semi obvious) Using votive you select project properties (right-click project - properties, select linker tab) specify e.g. en-US in the Cultures textbox, and add a reference to WixUIExtension On 3/13/07, Chris Bardon [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Thanks for the reply-I managed to get it to work by adding a copy of the .wxl to the project, but I can't find anywhere to modify the light command line in the project. Am I just missing something obvious? On a semi-related note, is there something special you have to do with Votive to customize bitmaps from one of the UI libs? I tried creating a bitmaps directory, below the wxs file, but it seems to be ignored (regardless of whether the new bitmaps are added to the project or not). Is it not possible to customize the dialogs when using the WixUIExtension DLL? I'm planning on creating my own UI lib based off of Mondo, but I'd
Re: [WiX-users] Question about FASTOEM InstallLocation
Re: FASTOEM I read the same requirement and found details on what is required for this functionality to work here: http://msdn2.microsoft.com/en-us/library/aa368576.aspx So, it could be something as simple as the package not been ran from the same volume... when it does work, it goes lightning quick, I was amazed!! Although, I can't see any use for it even though I went to the effort of creating a component to write the EstimatedSize registry value in manually on the condition of FASTOEM=1. Sorry, I didn't get any errors, but a verbose log file should help identify the cause of the failiure. In my experience, so long as the package happily installs without UI (relying on the Execute sequence alone) then the FASTOEM functionality comes for free, so long as you follow the points on taht MSDN page. Good luck, Gareth -- View this message in context: http://www.nabble.com/Question-about-FASTOEM---InstallLocation-tf2882775.html#a9477886 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
Re: [WiX-users] Condition display of dialog
I've done something similar, but while I don't have a solution to your 'double-click Next' issue, I can suggest how my validation works. On the 'Next' control button I have a pair of Punlished Events for true/false as you do, but only one is NewDialog. The REGISTRATIONCODEVALID=false case publishes a SpawnDialog event that has a string saying something like Invalid key! and an OK button control that has a published event of EndDialog. This just gives the user a pop up that they can't avoid until a valid key is entered. Works a treat. Cheers, Gareth -- View this message in context: http://www.nabble.com/Condition-display-of-dialog-tf3399345.html#a9478182 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
Re: [WiX-users] SchedXmlFile: Error 0x8007007a: failed to copy value:
What version of the WiX toolset are you using? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Duohong Xia Sent: Tuesday, March 13, 2007 5:33 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] SchedXmlFile: Error 0x8007007a: failed to copy value: When I run my msi, I get following error message. If I cut the value shorter, the msi works fine. Is an issue about buffer, and how to increase buffer size? Thank you. === Action ended 15:09:27: InstallFiles. Return value 1. Action start 15:09:27: SchedXmlFile. SchedXmlFile: Error 0x8007007a: failed to copy value: 182ec81be6b6cb82,1dce221aee8aa6a4,182ec81bde82,16888c24b8cea2d1,1dce221aee8a2e16,16888c24b8ceb6a8,182ec81beb6b,16888c24b8cec122,16888c24b8cecd1a,18eee4c8bc662cd6,182ec814abacebd8,182ec814abace62b,18eee4c8b8d4ebbd,182ec814abad14e8,182ec814abad4bdd SchedXmlFile: Error 0x8007007a: failed to read XmlFile table MSI (s) (6C!74) [15:09:27:720]: Product: Local Search Feed Input 2.12 -- Error 25530. There was a failure while configuring XML files. Error 25530. There was a failure while configuring XML files. Sucker-punch spam with award-winning protection. Try the free Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/features_spam.html - 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] Wix Coding Standards
I'm working on a mini-document that talks about CustomAction best practices that I'll eventually post on my blog (lots of stuff to cover). I haven't seen anything that talks about good ways to organize WiX source code. What do other people do? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anand Sent: Tuesday, March 13, 2007 6:08 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Wix Coding Standards Hi, Is there a coding standards document for Wix on sourceforge that recommends best practices for developing Wix XMLs and custom actions? Any help in this regard would be greatly appreciated. -- Thanks . . . Anand. - 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] Adding a merge module or is it a merge module?
The merge would have failed horribly if it wasn't a Merge Module. It looks like dark got confused and tried to decompile your Merge Module as a Product and that is why the Product element is completely blank. I expect the reason it didn't install is something to do with the install itself. You'll want to look at the verbose log file -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gerald Grininger Sent: Wednesday, March 14, 2007 2:31 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Adding a merge module or is it a merge module? Hello, I wanted to add a merge module provided within an sdk from Macrovision: Merge Id=DA8678BD-69FF-4272-9C6B-BF0471E52F46 Language=1033 src=Binary\installdir\isus.msm DiskId=1 / and also added MergeRef Id=DA8678BD-69FF-4272-9C6B-BF0471E52F46/ in a feature. But the mergemodule isn't installed. So I darked the msm: ?xml version=1.0 encoding=utf-8? Wix xmlns=http://schemas.microsoft.com/wix/2003/01/wi; Product Package Id=DA8678BD-69FF-4272-9C6B-BF0471E52F46 Keywords=MergeModule,MSI,Database Description=Macrovision Software Manager Comments=This will install the Macrovision Software Manager and register your application with it. Manufacturer=Macrovision Corporation InstallerVersion=200 Platforms=Intel Languages=1033 SummaryCodepage=1252 / Property Id=IE4FOUND This doesn't look like a merge module;), although they provide it as merge module. So how could I add this package to my product? Regards, Gerald _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ - 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] COM registration[Scanned]
You should never ever package someone else's resources in your installation package. If you do that then your install will take ownership of the resources and mess up everyone. Definitely use a Merge Module. VB6... hmm, might be hard to find stuff for that. Also, don't install your application stuff to system32. You're not part of Windows, stay out. CommonFilesFolder is where applications should put their common files. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Leigh Sent: Wednesday, March 14, 2007 2:55 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] COM registration[Scanned] I'm guessing that Jacquet's app is written in VB6 and probably uses some DLLs that Microsoft provide. In which case, the files probably should go in system32, as they may already be installed... I'm in a similar situation - preparing to write my first WiX install, for a VB6 app. I'm guessing there's an msm out there somewhere to install the VB runtime files? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Hamflett Sent: 14 March 2007 09:40 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] COM registration[Scanned] Is the DLL shared just between your products or with other parts of the system? You're not really meant to put things in the system32 folder. Rob Jacquet Fabian wrote: Hi, I'm a new user of wix. I'm trying to convert a setup made with Package and Deployment Wizard of visual studio 6. This setup use some self register dll and some shared dll wich are in the system32 directory. Currently, I'm using tallow to generate registry keys of self register dll. And I just copy shared dll in the system32 directory. But I'm not sure if it's the best way to install those components. Could you help me? Thank you. - 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=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.phpp=sourceforgeCID=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.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] Checkbox -- Desktop Shortcut
We've tried to get a bit better in WiX v3. Still may need more work, but WiX v3's dark is much better. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Hamflett Sent: Wednesday, March 14, 2007 2:39 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Checkbox -- Desktop Shortcut Dark has never been a proper decompiler. It works for the most part, but it's basically in there so you can open up existing MSIs and find out what's going on as a starting point. The WiX team have always said that you shouldn't expect a dark'd MSI to compile. Rob Lasse Rantanen wrote: Hello all, I'm just trying to learn WiX so please excuse me for presenting a question which has apparently been answered on this list. I just have difficulties to understand those examples. My problem is as follows: I create a setup using VS2003. The installation has a dialog presenting a checkbox Create a desktop shortcut. This works as expected when setup.msi created by VS2003 is executed. Then I decompile this msi using dark, make some changes (translate texts), compile and link my wxs file to get a modified msi. The checkbox appears on the dialog where I put it, but it can't be checked. It is enabled I guess cause it flashes when clicked on. It appears to me that dark (?) is somehow messing with this shortcut thing, but I can't figure out what's happening? Has anybody any clue where the problem might be or does anybody know an example simple enough for a newbie to get grasp on this thing? TIA Lasse - 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 - 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] Wix Coding Standards
Personally, I ... * Use 4-space indenting on any child * If the attributes get to unwieldly to have on a single line, I put each one on a separate line, indented 8-spaces from the tag start. * I match the indentation of the close tag with the open tag. A snippet: Julie [EMAIL PROTECTED] Message: 4 Date: Wed, 14 Mar 2007 09:45:51 -0700 From: Rob Mensching [EMAIL PROTECTED] Subject: Re: [WiX-users] Wix Coding Standards To: Anand [EMAIL PROTECTED], wix-users@lists.sourceforge.net wix-users@lists.sourceforge.net Message-ID: [EMAIL PROTECTED] MSG.exchange.corp.microsoft.com Content-Type: text/plain; charset=us-ascii I'm working on a mini-document that talks about CustomAction best practices that I'll eventually post on my blog (lots of stuff to cover). I haven't seen anything that talks about good ways to organize WiX source code. What do other people do? _ Scanned by IBM Email Security Management Services powered by MessageLabs. For more information please visit http://www.ers.ibm.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
Re: [WiX-users] Wix Coding Standards
(Continued, sorry, hit the send key accidently) Directory Id='TSBDIR' Name='Test Script Builder' Component Id='TSB' Guid='0B3BEB7B-7822-498F-A599-F4509514FE45' File Id='TestScriptBuilderEXE' Name='TestScriptBuilder.exe' Source=C:\PlatformESP\TSB\Deliverables\TestScriptBuilder.exe / File Id='TestScriptBuilderINI' Name='TestScriptBuilder.ini' Source=C:\PlatformESP\TSB\Distros\TestScriptBuilder.ini / Shortcut Id='StartMenu_Shortcut' Name='TestScriptBuilder' Directory='StartMenuFolder' Icon='TSB.exe' IconIndex='0' WorkingDirectory='TSBDIR' Advertise='yes' / Shortcut Id='PM_Shortcut' Name='TestScriptBuilder' Directory='IDProgramGroup' Icon='TSB.exe' IconIndex='0' WorkingDirectory='TSBDIR' Advertise='yes' / /Component Julie [EMAIL PROTECTED] _ Scanned by IBM Email Security Management Services powered by MessageLabs. For more information please visit http://www.ers.ibm.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
Re: [WiX-users] Wix Coding Standards
Re-arrange the code a lot :) If you want to save yourself a lot of effort, scribble down a rough idea of where the WiX files are going to be, and where they're going to get the product files from. Then work out what needs to be done in when you want to change a product file to a new version. Does a WiX file need to be edited? Does WiX pull it out of a 'release' folder? Does the Product version get hard set in the WiX file? Do you have to specify it on the command line call to 'make'? How much work is going to be required if a developer wants to add another file to something? Have a stab at a first attempt, and then talk to your developers about what they have to do to change anything. Then adapt. I know that's not exactly a white paper, but really, think about your code layout and how easy changes are going to be for everyone. I say this as someone who's gone from merge modules to fragments to merge modules AND fragments, hard set version'd directories to release directories, getting WiX fragment sources out of source control to just requiring them to be on disk, and re-arranged the WiX source several times. Rob Rob Mensching wrote: I’m working on a mini-document that talks about CustomAction best practices that I’ll eventually post on my blog (lots of stuff to cover). I haven’t seen anything that talks about good ways to organize WiX source code. What do other people do? *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *On Behalf Of *Anand *Sent:* Tuesday, March 13, 2007 6:08 PM *To:* wix-users@lists.sourceforge.net *Subject:* [WiX-users] Wix Coding Standards Hi, Is there a coding standards document for Wix on sourceforge that recommends best practices for developing Wix XMLs and custom actions? Any help in this regard would be greatly appreciated. -- Thanks . . . Anand. - 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] Regasm problem
Hello, I am trying to register a .net dll using regasm. I have used regasm to create a registry file and then used tallow to convert the registry file to a .wxs file. I am using wix version 2.0.4415.0. However it doesn't seem to create all the registry entries. Am I missing a step? Also, I have read everywhere that it is best not to create a custom action to do the regasm, but there is no clear explanation why. Does anyone know why? TIA, Shayla- 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] Can't make DiskPrompt to work
This was my suspicion, I tried with CD simulation software with the same result. Maybe I need to try with real CD. Do I have to define VolumeLabel attribute for MediaTag in this case or it's optional? Thanks a lot Igor Bob Arnson-3 wrote: Igor Maslov wrote: Error 1311. Source file not found(cabinet): C:\projects\depot\test\build\IMAGE\DISK1\Group2.cab. Verify that the file exists and that you can access it. Media prompts rely on the volume label; you won't get prompted if you're installing from a hard drive. -- 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.phpp=sourceforgeCID=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/Can%27t-make-DiskPrompt-to-work-tf3390980.html#a9479364 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
Re: [WiX-users] Shared files question?
Thanks. I didn't realize you could have the same component in different features. That should solve the problem. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, March 14, 2007 11:25 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Shared files question? Scott, If I understand you correctly, you are saying that you currently have the same source file included in multiple components. Is that right? If so, presumably there is something stopping you from putting the file(s) in as many components as you need and including a ComponentRef to it/them in your feature(s). What is that? My guess would be that the shared files have to be installed in the same folder as the application, and since the applications can be installed stand-alone (presumably each into their own folder) you may need the same file in more than one place. Am I on the right track so far? Regards, Richard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam Sent: Wednesday, March 14, 2007 11:12 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Shared files question? In our product, we have a bunch of features that are usually all installed on the same machine, but were designed to be able to be installed as stand alone programs on separate machines. As a result, there are a bunch of files that are shared between the different features. Currently I have all of the files for each feature installed with that feature, just in case they are installed on separate machines. This leaves me with a lot of duplicate files in the installation. I'm am getting ICE errors about it, but I am currently ignoring them. What is the best way to do this? My first thought was to put all of the common files in one feature and install them all of the time. The problem is that some files are common to two features, but not the rest. We don't want to be installing any extra files, if we don't have to. I'm using wix v3 with votive and vs2005. http://www.clearviewecm.com/ The information contained in this email is privileged and confidential and is intended solely for the addressee(s). If you are not the intended recipient, please respond to [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] then delete this email from your system. * C O N F I D E N T I A L I T Y N O T I C E * --- The content of this e-mail is intended solely for the use of the individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited. Peek Traffic Corporation is neither liable for the contents, nor for the proper, complete and timely transmission of (the information contained in) this communication. If you have received this communication in error, please notify the author by replying to this e-mail immediately and delete the material from any computer. attachment: image001.jpg - 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] Uninstalling
You we're right, MSI was thinking that some other client was using this product. Ive found out that those were the common reg entries generated by Tallow. The more i use Tallow, the less i like it :( So i got rid of the non-component-specific entries made by tallow, and now it works correctly Thanks for the heads up. - 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] Help with Upgrade scenarios.
In the project I'm working on, we've hit a pain point and we're not certain how to overcome it. Right now if we want to do an upgrade, the user has to uninstall before installing the new version. I am sure this has to be possible, I just need some pointers on the how to side of things. Thanks! Rory - 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 InstallShield msm files causes an error
That should work. If you have any custom actions in your msm verify that the sequencing is after the cost standard actions. Thanks, Tom -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Geoff Finger Sent: Wednesday, March 14, 2007 1:04 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Using InstallShield msm files causes an error I'm trying to include a merge module from an older project that was made when we were using InstallShield to create our installations. When I try including it in my Wix project it compiles fine but when running it I get the error: Action start 16:32:36: ResolveSource. MSI (c) (EC:E0) [16:32:36:124]: Note: 1: 2732 2: 0 DEBUG: Error 2732: Directory Manager not initialized. The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2732. The arguments are: 0, , I tried using dark to decompile the msm file and recompiled it directly into a new Wix merge module, and that seems to work fine. So if necessary I can just do that instead, but it would be preferable to get the original msm working. Is there something extra I need to do in order to get InstallShield merge modules to work with Wix? Or are the two just fundamentally incompatible? (I tried searching the list archives for any info on this but I keep getting 500 - Internal Server Error) - 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=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.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] CustomAction and Working Directory
I am trying to run an application at the end of an install. The application needs files that are installed as part of the install and they need to be in the same directory. The CustomAction line I have is: CustomAction Id='LaunchFile' FileKey='install_silent.bat' ExeCommand='' Return='asyncWait' / The above is trying to start the application in c:\windows\system32 not the application directory that it is installed in. Could somebody tell me what I am doing wrong? Also how to I run an application at uninstall? You can see my whole .wxs file below: ?xml version=1.0 encoding=utf-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Product Id=AD2D4607-2DAF-4459-AB53-A5E6733CC27F UpgradeCode=95056130-FDDB-4835-BA81-F4CBBD2EFFAC Name=UltraVNC Hook Driver Language=1033 Version=1.0.0.0 Manufacturer=UltraVNC Package Description=UltraVNC Hook Driver Comments=UltraVNC Hook Driver InstallerVersion=200 Compressed=yes / Media Id=1 Cabinet=UltraVNC.cab EmbedCab=yes / Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFilesFolder Directory Id=INSTALLLOCATION Name=UltraVNC Driver Component Id=ProductComponent Guid=35137132-23B9-45fc-BC37-8AF22A300C4E File Id='before.txt' Name='before.txt' DiskId='1' Source='ultravnc\driver\before.txt'/ File Id='install.bat' Name='install.bat' DiskId='1' Source='ultravnc\driver\install.bat'/ File Id='install_silent.bat' Name='install_silent.bat' DiskId='1' Source='ultravnc\driver\install_silent.bat'/ File Id='license.txt' Name='license.txt' DiskId='1' Source='ultravnc\driver\license.txt'/ File Id='setupdrv.exe' Name='setupdrv.exe' DiskId='1' Source='ultravnc\driver\setupdrv.exe'/ File Id='uninstall.bat' Name='uninstall.bat' DiskId='1' Source='ultravnc\driver\uninstall.bat'/ File Id='uninstall_silent.bat' Name='uninstall_silent.bat' DiskId='1' Source='ultravnc\driver\uninstall_silent.bat'/ File Id='vnccom.sys' Name='vnccom.sys' DiskId='1' Source='ultravnc\driver\vnccom.sys'/ File Id='vncdrv.dll' Name='vncdrv.dll' DiskId='1' Source='ultravnc\driver\vncdrv.dll'/ File Id='vncdrv.inf' Name='vncdrv.inf' DiskId='1' Source='ultravnc\driver\vncdrv.inf'/ File Id='vncdrv.sys' Name='vncdrv.sys' DiskId='1' Source='ultravnc\driver\vncdrv.sys'/ File Id='vnchelp.dll' Name='vnchelp.dll' DiskId='1' Source='ultravnc\driver\vnchelp.dll'/ /Component /Directory /Directory /Directory Condition Message='This application only runs on Windows XP' VersionNT = 501 /Condition InstallExecuteSequence Custom Action='LaunchFile' After='InstallFinalize'/ /InstallExecuteSequence CustomAction Id='LaunchFile' FileKey='install_silent.bat' ExeCommand='' Return='asyncWait' / Feature Id=UltraVNCFeature Title=UltraVNC Feature Level=1 ComponentRef Id=ProductComponent / /Feature /Product /Wix Thanks - 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] Help with Upgrade scenarios.
Does it complain about a different version of the product already being installed? If so, you need to install the MSI via the msiexec.exe command like this: msiexec.exe /I your_msi.msi REINSTALL=All REINSTALLMODE=vomus On 3/14/07, Rory Clark [EMAIL PROTECTED] wrote: In the project I'm working on, we've hit a pain point and we're not certain how to overcome it. Right now if we want to do an upgrade, the user has to uninstall before installing the new version. I am sure this has to be possible, I just need some pointers on the how to side of things. Thanks! Rory - 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] Help with Upgrade scenarios.
That solved the short term problem, but isn't a long term solution. Looks like I need to do a lot more research and a lot more reading. Thanks! Rory From: Levi Wilson [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 14, 2007 11:39 AM To: Rory Clark Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Help with Upgrade scenarios. Does it complain about a different version of the product already being installed? If so, you need to install the MSI via the msiexec.exe command like this: msiexec.exe /I your_msi.msi REINSTALL=All REINSTALLMODE=vomus On 3/14/07, Rory Clark [EMAIL PROTECTED] wrote: In the project I'm working on, we've hit a pain point and we're not certain how to overcome it. Right now if we want to do an upgrade, the user has to uninstall before installing the new version. I am sure this has to be possible, I just need some pointers on the how to side of things. Thanks! Rory - 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=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.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Help with Upgrade scenarios.
What are you trying to achieve? Are you trying to make it so you don't have to do that from the command-line? One thing that I think that you can do is set a property in your wxs file that is: Property Id=REINSTALLMODE Value=vomus / If you look at the MSDN documentation for the REINSTALLMODE property, you're not supposed to put the v in vomus on the initial installation, but I have never figured out why you're not supposed to do this. On 3/14/07, Rory Clark [EMAIL PROTECTED] wrote: That solved the short term problem, but isn't a long term solution. Looks like I need to do a lot more research and a lot more reading. Thanks! Rory -- *From:* Levi Wilson [mailto:[EMAIL PROTECTED] *Sent:* Wednesday, March 14, 2007 11:39 AM *To:* Rory Clark *Cc:* wix-users@lists.sourceforge.net *Subject:* Re: [WiX-users] Help with Upgrade scenarios. Does it complain about a different version of the product already being installed? If so, you need to install the MSI via the msiexec.exe command like this: msiexec.exe /I your_msi.msi REINSTALL=All REINSTALLMODE=vomus On 3/14/07, Rory Clark [EMAIL PROTECTED] wrote: In the project I'm working on, we've hit a pain point and we're not certain how to overcome it. Right now if we want to do an upgrade, the user has to uninstall before installing the new version. I am sure this has to be possible, I just need some pointers on the how to side of things. Thanks! Rory - 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] Help with Upgrade scenarios.
Rory, One thing to be aware of (which caught me, and continues to be a source of frustration from time to time) is that Windows Installer only looks at the first 3 parts of the version information. Lesson 4 in the tutorial (http://www.tramontana.co.hu/wix/lesson4.php) should offer some assistance too. The thing you need to understand is the difference between small, minor and major upgrades. Hope this helps, Regards, Richard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rory Clark Sent: Wednesday, March 14, 2007 3:10 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Help with Upgrade scenarios. That solved the short term problem, but isn't a long term solution. Looks like I need to do a lot more research and a lot more reading. Thanks! Rory * C O N F I D E N T I A L I T Y N O T I C E * --- The content of this e-mail is intended solely for the use of the individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited. Peek Traffic Corporation is neither liable for the contents, nor for the proper, complete and timely transmission of (the information contained in) this communication. If you have received this communication in error, please notify the author by replying to this e-mail immediately and delete the material from any computer. - 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] Help with Upgrade scenarios.
There is also the option of major upgrades that don't require command-line parameters at all. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Levi Wilson Sent: Wednesday, March 14, 2007 12:13 PM To: Rory Clark Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Help with Upgrade scenarios. What are you trying to achieve? Are you trying to make it so you don't have to do that from the command-line? One thing that I think that you can do is set a property in your wxs file that is: Property Id=REINSTALLMODE Value=vomus / If you look at the MSDN documentation for the REINSTALLMODE property, you're not supposed to put the v in vomus on the initial installation, but I have never figured out why you're not supposed to do this. On 3/14/07, Rory Clark [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: That solved the short term problem, but isn't a long term solution. Looks like I need to do a lot more research and a lot more reading. Thanks! Rory From: Levi Wilson [mailto:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 14, 2007 11:39 AM To: Rory Clark Cc: wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Help with Upgrade scenarios. Does it complain about a different version of the product already being installed? If so, you need to install the MSI via the msiexec.exe command like this: msiexec.exe /I your_msi.msi REINSTALL=All REINSTALLMODE=vomus On 3/14/07, Rory Clark [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: In the project I'm working on, we've hit a pain point and we're not certain how to overcome it. Right now if we want to do an upgrade, the user has to uninstall before installing the new version. I am sure this has to be possible, I just need some pointers on the how to side of things. Thanks! Rory - 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.netmailto: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.netmailto: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] Help with Upgrade scenarios.
Rob, Is there a short answer as to why you're not supposed to set the REINSTALLMODE property to vomus and just leave it like that? On 3/14/07, Rob Mensching [EMAIL PROTECTED] wrote: There is also the option of major upgrades that don't require command-line parameters at all. *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Levi Wilson *Sent:* Wednesday, March 14, 2007 12:13 PM *To:* Rory Clark *Cc:* wix-users@lists.sourceforge.net *Subject:* Re: [WiX-users] Help with Upgrade scenarios. What are you trying to achieve? Are you trying to make it so you don't have to do that from the command-line? One thing that I *think* that you can do is set a property in your wxs file that is: Property Id=REINSTALLMODE Value=vomus / If you look at the MSDN documentation for the REINSTALLMODE property, you're not supposed to put the v in vomus on the initial installation, but I have never figured out why you're not supposed to do this. On 3/14/07, *Rory Clark* [EMAIL PROTECTED] wrote: That solved the short term problem, but isn't a long term solution. Looks like I need to do a lot more research and a lot more reading. Thanks! Rory -- *From:* Levi Wilson [mailto:[EMAIL PROTECTED] *Sent:* Wednesday, March 14, 2007 11:39 AM *To:* Rory Clark *Cc:* wix-users@lists.sourceforge.net *Subject:* Re: [WiX-users] Help with Upgrade scenarios. Does it complain about a different version of the product already being installed? If so, you need to install the MSI via the msiexec.exe command like this: msiexec.exe /I your_msi.msi REINSTALL=All REINSTALLMODE=vomus On 3/14/07, *Rory Clark* [EMAIL PROTECTED] wrote: In the project I'm working on, we've hit a pain point and we're not certain how to overcome it. Right now if we want to do an upgrade, the user has to uninstall before installing the new version. I am sure this has to be possible, I just need some pointers on the how to side of things. Thanks! Rory - 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] Set All Users desktop
Can I set the desktop to point to all user? By using DesktopFolder, I can only set it to point to the per-user. Thanks, - 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] Set All Users desktop
I believe the ALLUSERS property needs to be set to 1 On 3/14/07, Bei Liu (Volt) [EMAIL PROTECTED] wrote: Can I set the desktop to point to all user? By using DesktopFolder, I can only set it to point to the per-user. Thanks, - 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] Set All Users desktop
Set the ALLUSERS property to 2. That should do it. - Brett _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bei Liu (Volt) Sent: Wednesday, March 14, 2007 2:44 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Set All Users desktop Can I set the desktop to point to all user? By using DesktopFolder, I can only set it to point to the per-user. Thanks, - 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] Help with Upgrade scenarios.
v means any time you do a repair operation with the MSI, that the original source media will be required. Users *hate* that. From: Levi Wilson [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 14, 2007 12:23 PM To: Rob Mensching Cc: Rory Clark; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Help with Upgrade scenarios. Rob, Is there a short answer as to why you're not supposed to set the REINSTALLMODE property to vomus and just leave it like that? On 3/14/07, Rob Mensching [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: There is also the option of major upgrades that don't require command-line parameters at all. From: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED]] On Behalf Of Levi Wilson Sent: Wednesday, March 14, 2007 12:13 PM To: Rory Clark Cc: wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Help with Upgrade scenarios. What are you trying to achieve? Are you trying to make it so you don't have to do that from the command-line? One thing that I think that you can do is set a property in your wxs file that is: Property Id=REINSTALLMODE Value=vomus / If you look at the MSDN documentation for the REINSTALLMODE property, you're not supposed to put the v in vomus on the initial installation, but I have never figured out why you're not supposed to do this. On 3/14/07, Rory Clark [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: That solved the short term problem, but isn't a long term solution. Looks like I need to do a lot more research and a lot more reading. Thanks! Rory From: Levi Wilson [mailto: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 14, 2007 11:39 AM To: Rory Clark Cc: wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Help with Upgrade scenarios. Does it complain about a different version of the product already being installed? If so, you need to install the MSI via the msiexec.exe command like this: msiexec.exe /I your_msi.msi REINSTALL=All REINSTALLMODE=vomus On 3/14/07, Rory Clark [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: In the project I'm working on, we've hit a pain point and we're not certain how to overcome it. Right now if we want to do an upgrade, the user has to uninstall before installing the new version. I am sure this has to be possible, I just need some pointers on the how to side of things. Thanks! Rory - 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.netmailto: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.netmailto: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] Help with Upgrade scenarios.
I thought that the v will run from the source (the msi that you're currently trying to install) and recache the local copy. When would it ask for the source media? On 3/14/07, Rob Mensching [EMAIL PROTECTED] wrote: v means any time you do a repair operation with the MSI, that the original source media will be required. Users **hate** that. *From:* Levi Wilson [mailto:[EMAIL PROTECTED] *Sent:* Wednesday, March 14, 2007 12:23 PM *To:* Rob Mensching *Cc:* Rory Clark; wix-users@lists.sourceforge.net *Subject:* Re: [WiX-users] Help with Upgrade scenarios. Rob, Is there a short answer as to why you're not supposed to set the REINSTALLMODE property to vomus and just leave it like that? On 3/14/07, *Rob Mensching* [EMAIL PROTECTED] wrote: There is also the option of major upgrades that don't require command-line parameters at all. *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Levi Wilson *Sent:* Wednesday, March 14, 2007 12:13 PM *To:* Rory Clark *Cc:* wix-users@lists.sourceforge.net *Subject:* Re: [WiX-users] Help with Upgrade scenarios. What are you trying to achieve? Are you trying to make it so you don't have to do that from the command-line? One thing that I *think* that you can do is set a property in your wxs file that is: Property Id=REINSTALLMODE Value=vomus / If you look at the MSDN documentation for the REINSTALLMODE property, you're not supposed to put the v in vomus on the initial installation, but I have never figured out why you're not supposed to do this. On 3/14/07, *Rory Clark* [EMAIL PROTECTED] wrote: That solved the short term problem, but isn't a long term solution. Looks like I need to do a lot more research and a lot more reading. Thanks! Rory -- *From:* Levi Wilson [mailto: [EMAIL PROTECTED] *Sent:* Wednesday, March 14, 2007 11:39 AM *To:* Rory Clark *Cc:* wix-users@lists.sourceforge.net *Subject:* Re: [WiX-users] Help with Upgrade scenarios. Does it complain about a different version of the product already being installed? If so, you need to install the MSI via the msiexec.exe command like this: msiexec.exe /I your_msi.msi REINSTALL=All REINSTALLMODE=vomus On 3/14/07, *Rory Clark* [EMAIL PROTECTED] wrote: In the project I'm working on, we've hit a pain point and we're not certain how to overcome it. Right now if we want to do an upgrade, the user has to uninstall before installing the new version. I am sure this has to be possible, I just need some pointers on the how to side of things. Thanks! Rory - 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] Install only on XP SP2 or better
I'm trying to make some code that installs only on Windows: XP SP2 or better, 2003 SP1 or better, or Vista or better. I'm using the code below, and my application happily installs itself on Win2000. What am I doing wrong? Property Id=WIN2KSP4EXISTS![CDATA[VersionNT = 500 AND ServicePackLevel =4]]/Property Property Id=WINXPSP2EXISTS![CDATA[VersionNT = 501 AND ServicePackLevel =2]]/Property Property Id=WIN2K3SP1EXISTS![CDATA[VersionNT = 502 AND ServicePackLevel =1]]/Property Property Id=WINVISTAORBETTEREXISTS![CDATA[VersionNT 502]]/Property Condition Message=This setup requires Windows XP with Service Pack 2.![CDATA[WINXPSP2EXISTS OR WIN2K3SP1EXISTS OR WINVISTAORBETTEREXISTS]]/Condition - 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] Install only on XP SP2 or better
I don't believe you can set properties like that. Instead, use your VersionNT=... conditions inside the Condition / element. That should work. On 3/14/07, Nick [EMAIL PROTECTED] wrote: I'm trying to make some code that installs only on Windows: XP SP2 or better, 2003 SP1 or better, or Vista or better. I'm using the code below, and my application happily installs itself on Win2000. What am I doing wrong? Property Id=WIN2KSP4EXISTS![CDATA[VersionNT = 500 AND ServicePackLevel =4]]/Property Property Id=WINXPSP2EXISTS![CDATA[VersionNT = 501 AND ServicePackLevel =2]]/Property Property Id=WIN2K3SP1EXISTS![CDATA[VersionNT = 502 AND ServicePackLevel =1]]/Property Property Id=WINVISTAORBETTEREXISTS![CDATA[VersionNT 502]]/Property Condition Message=This setup requires Windows XP with Service Pack 2.![CDATA[WINXPSP2EXISTS OR WIN2K3SP1EXISTS OR WINVISTAORBETTEREXISTS]]/Condition - 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] Help with Upgrade scenarios.
You could be right. I haven't played with setting v all of the time, so I'd have to create a few MSI files and do that. Now that I finally did all the work to show why COM advertisement is bad and why ICE33 can be ignored (http://robmensching.com/blog/archive/2007/03/12/RobMens-Recommendation-Do-not-advertise-COM-information-in-MSI.aspx) maybe I'll try this one... next week. From: Levi Wilson [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 14, 2007 12:58 PM To: Rob Mensching Cc: Rory Clark; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Help with Upgrade scenarios. I thought that the v will run from the source (the msi that you're currently trying to install) and recache the local copy. When would it ask for the source media? On 3/14/07, Rob Mensching [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: v means any time you do a repair operation with the MSI, that the original source media will be required. Users *hate* that. From: Levi Wilson [mailto:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 14, 2007 12:23 PM To: Rob Mensching Cc: Rory Clark; wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Help with Upgrade scenarios. Rob, Is there a short answer as to why you're not supposed to set the REINSTALLMODE property to vomus and just leave it like that? On 3/14/07, Rob Mensching [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: There is also the option of major upgrades that don't require command-line parameters at all. From: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]mailto:[EMAIL PROTECTED]] On Behalf Of Levi Wilson Sent: Wednesday, March 14, 2007 12:13 PM To: Rory Clark Cc: wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Help with Upgrade scenarios. What are you trying to achieve? Are you trying to make it so you don't have to do that from the command-line? One thing that I think that you can do is set a property in your wxs file that is: Property Id=REINSTALLMODE Value=vomus / If you look at the MSDN documentation for the REINSTALLMODE property, you're not supposed to put the v in vomus on the initial installation, but I have never figured out why you're not supposed to do this. On 3/14/07, Rory Clark [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: That solved the short term problem, but isn't a long term solution. Looks like I need to do a lot more research and a lot more reading. Thanks! Rory From: Levi Wilson [mailto: [EMAIL PROTECTED]mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 14, 2007 11:39 AM To: Rory Clark Cc: wix-users@lists.sourceforge.netmailto:wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Help with Upgrade scenarios. Does it complain about a different version of the product already being installed? If so, you need to install the MSI via the msiexec.exe command like this: msiexec.exe /I your_msi.msi REINSTALL=All REINSTALLMODE=vomus On 3/14/07, Rory Clark [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: In the project I'm working on, we've hit a pain point and we're not certain how to overcome it. Right now if we want to do an upgrade, the user has to uninstall before installing the new version. I am sure this has to be possible, I just need some pointers on the how to side of things. Thanks! Rory - 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.netmailto: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.netmailto: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
Re: [WiX-users] Creating SqlDatabase with/without Windows Authentification
I'd be interested in seeing your solution, Peter. Can you post your solution on the Wix-users list for future reference? I feel this shouldn't be hard, but if you already have it, then why reinvent the wheel! Thanks in advance. On 3/13/07, pobox77 [EMAIL PROTECTED] wrote: Thanks Dana, I've just found the same solution about an hour ago. Just a note for people having similar problem: The property used by the radio button and in the condition must be a global property (e.g. the name of it should only have capitals) otherwise it doesn't work. Peter Dana Gutride wrote: This is not possible within the sql database tag right now. There is a bug/feature request in for this exact functionality, but as far as I can tell, it hasn't been added yet. The only way to do this is to have two sqldatabase tags in separate components and then add conditions for the components based on the radio button's property. Dana On 3/13/07, pobox77 [EMAIL PROTECTED] wrote: Sorry, the snippet was wrong formatted. pobox77 wrote: Hi, I would like to create a SqlDatabase either with Username+Password or with Windows authentification. I am using a radio button in a customize dialog. If not Windows auth. is selected, the user can enter a username and a password. How should I set the SqlDatabase component to do it? I mean, if Windows auth. the User=SQLUser should not be used. Snippet: Component Id=CreateDB DiskId=1 Guid=---- sql:SqlDatabase Id=MyDb Server=[SQLSERVER] Database=[SQLDBNAME] CreateOnInstall=yes ConfirmOverwrite=yes DropOnReinstall=no DropOnUninstall=no User=SQLUser sql:SqlScript Id=CreateTablesSqlScript ContinueOnError=no ExecuteOnInstall=yes ExecuteOnReinstall=no Sequence=002 BinaryKey=CreateTablesBin User=SQLUser / /sql:SqlDatabase /Component Feature Id=SqlDb Title=Create Database Description=Installing database. Please ensure that the SQL Server is running on the target server. AllowAdvertise=yes TypicalDefault=install Display=expand Level=1 ComponentRef Id=CreateDB / /Feature Thanks in advance, Peter -- View this message in context: http://www.nabble.com/Creating-SqlDatabase-with-without-Windows-Authentification-tf3394305.html#a9449474 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 -- View this message in context: http://www.nabble.com/Creating-SqlDatabase-with-without-Windows-Authentification-tf3394305.html#a9453722 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
Re: [WiX-users] Set All Users desktop
It looks like that Directory element doesn't have an attribute called ALLUSERS. Directory Id=DesktopFolder Name=Desktop AllUSERS=1/ Is there any other way do set it? Thanks, From: Levi Wilson [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 14, 2007 12:51 PM To: Bei Liu (Volt) Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Set All Users desktop I believe the ALLUSERS property needs to be set to 1 On 3/14/07, Bei Liu (Volt) [EMAIL PROTECTED]mailto:[EMAIL PROTECTED] wrote: Can I set the desktop to point to all user? By using DesktopFolder, I can only set it to point to the per-user. Thanks, - 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.netmailto: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] Set All Users desktop
ALLUSERS is an installation level property. (I.e. you can run the installation for the current user - ALLUSERS = 0, or for all users - ALLUSERS = 1). It is not associated with the directory. Beware - the property is a public one, and therefore needs to be all uppercase. You really don't want to go messing with an all users folder on a per-user installation. System administrators everywhere will say all sorts of rude things if you do. Regards, Richard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bei Liu (Volt) Sent: Wednesday, March 14, 2007 4:12 PM To: Levi Wilson Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Set All Users desktop It looks like that Directory element doesn't have an attribute called ALLUSERS. Directory Id=DesktopFolder Name=Desktop AllUSERS=1/ Is there any other way do set it? Thanks, * C O N F I D E N T I A L I T Y N O T I C E * --- The content of this e-mail is intended solely for the use of the individual or entity to whom it is addressed. If you have received this communication in error, be aware that forwarding it, copying it, or in any way disclosing its content to any other person, is strictly prohibited. Peek Traffic Corporation is neither liable for the contents, nor for the proper, complete and timely transmission of (the information contained in) this communication. If you have received this communication in error, please notify the author by replying to this e-mail immediately and delete the material from any computer. - 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] Install only on XP SP2 or better
Those properties won't be evaluated at runtime. Instead, they'll be set to the specified text. The expression in the Condition element will then be evaluated as VersionNT = 501 AND ServicePackLevel =2 OR VersionNT = 502 AND ServicePackLevel =1 OR VersionNT 502 The condition evaluation treats any non-empty string as being TRUE, so the condition evaluates to TRUE and the install proceeds. You'll either have to specify the condition completely within the Condition element, or you need to use Custom Action Type 51, which enables you to set a property to the _evaluated_ result of an expression. They look like this: CustomAction Id=TestWin2kSP4 Property=WIN2KSP4EXISTS Value=[VersionNT] = 500 AND [ServicePackLevel] = 4/ (I may have the brackets placed wrong, I've not tested this.) You should be able to schedule these before the LaunchConditions action. -- Mike Dimmick -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nick Sent: 14 March 2007 20:01 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Install only on XP SP2 or better I'm trying to make some code that installs only on Windows: XP SP2 or better, 2003 SP1 or better, or Vista or better. I'm using the code below, and my application happily installs itself on Win2000. What am I doing wrong? Property Id=WIN2KSP4EXISTS![CDATA[VersionNT = 500 AND ServicePackLevel =4]]/Property Property Id=WINXPSP2EXISTS![CDATA[VersionNT = 501 AND ServicePackLevel =2]]/Property Property Id=WIN2K3SP1EXISTS![CDATA[VersionNT = 502 AND ServicePackLevel =1]]/Property Property Id=WINVISTAORBETTEREXISTS![CDATA[VersionNT 502]]/Property Condition Message=This setup requires Windows XP with Service Pack 2.![CDATA[WINXPSP2EXISTS OR WIN2K3SP1EXISTS OR WINVISTAORBETTEREXISTS]]/Condition - 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] WIX MSBuild task
Is there a WIX MSBuild task? I have the Wix target file and assembly (version 2), however the only example I can find imports the wix target file and immediately builds, and doesn't do anything else I have specified in my build script. Is there a WIX task I can call from within an MSBuild target? Or a way to do this? For example: Target name=AfterCompile WIX ... /WIX /Target Thanks, Shane - The information contained in this message is confidential proprietary property of Nelnet, Inc. and its affiliated companies (Nelnet) and is intended for the recipient only. Any reproduction, forwarding, or copying without the express permission of Nelnet is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to this e-mail. - 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] Windows Installer 4.0 msi schema
Hello, I'm not sure if I'm phrasing this correctly but I'll throw it out there anyway... Is there any way with Wix to pick up new tables in the Windows Installer 4.0 msi schema? I'm particularly interested in the MSIPatchCertificate table. Thanks, Tom - 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 InstallShield msm files causes an error
Yeah, changing the sequence of ResolveSource from 525 to 1025 fixed it, thanks! Is there a way to override the sequence of an item in a Merge Module when you reference it, or am I going to have to run Orca and fix it manually every time I recompile? On 3/14/07, Thomas Svare [EMAIL PROTECTED] wrote: That should work. If you have any custom actions in your msm verify that the sequencing is after the cost standard actions. Thanks, Tom -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Geoff Finger Sent: Wednesday, March 14, 2007 1:04 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Using InstallShield msm files causes an error I'm trying to include a merge module from an older project that was made when we were using InstallShield to create our installations. When I try including it in my Wix project it compiles fine but when running it I get the error: Action start 16:32:36: ResolveSource. MSI (c) (EC:E0) [16:32:36:124]: Note: 1: 2732 2: 0 DEBUG: Error 2732: Directory Manager not initialized. The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2732. The arguments are: 0, , I tried using dark to decompile the msm file and recompiled it directly into a new Wix merge module, and that seems to work fine. So if necessary I can just do that instead, but it would be preferable to get the original msm working. Is there something extra I need to do in order to get InstallShield merge modules to work with Wix? Or are the two just fundamentally incompatible? (I tried searching the list archives for any info on this but I keep getting 500 - Internal Server Error) - 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] Costom feature selection control
I would like to know if there is a way to make a custom feature selecion control. Or at least, how to put and checkbox and enable or disable a particular feature. I browse wix code but find anything. Thanks, Brian J. Cardiff - 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 InstallShield msm files causes an error
You should be able to set the sequence of the offending custom action from the msm in main WiX project I think. Thanks, Tom -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Geoff Finger Sent: Wednesday, March 14, 2007 4:21 PM To: wix-users@lists.sourceforge.net Cc: Thomas Svare Subject: Re: [WiX-users] Using InstallShield msm files causes an error Yeah, changing the sequence of ResolveSource from 525 to 1025 fixed it, thanks! Is there a way to override the sequence of an item in a Merge Module when you reference it, or am I going to have to run Orca and fix it manually every time I recompile? On 3/14/07, Thomas Svare [EMAIL PROTECTED] wrote: That should work. If you have any custom actions in your msm verify that the sequencing is after the cost standard actions. Thanks, Tom -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Geoff Finger Sent: Wednesday, March 14, 2007 1:04 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Using InstallShield msm files causes an error I'm trying to include a merge module from an older project that was made when we were using InstallShield to create our installations. When I try including it in my Wix project it compiles fine but when running it I get the error: Action start 16:32:36: ResolveSource. MSI (c) (EC:E0) [16:32:36:124]: Note: 1: 2732 2: 0 DEBUG: Error 2732: Directory Manager not initialized. The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2732. The arguments are: 0, , I tried using dark to decompile the msm file and recompiled it directly into a new Wix merge module, and that seems to work fine. So if necessary I can just do that instead, but it would be preferable to get the original msm working. Is there something extra I need to do in order to get InstallShield merge modules to work with Wix? Or are the two just fundamentally incompatible? (I tried searching the list archives for any info on this but I keep getting 500 - Internal Server Error) - 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=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.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] COM registration[Scanned]
Visual Studio 6.0 SP6 merge modules are downloadable from http://www.microsoft.com/downloads/details.aspx?familyid=f9d19334-61ec-48cf- bb4e-3aec65edd50bdisplaylang=en. Note the bugs listed at http://www.installsite.org/pages/en/bugs_msi.htm#wimsm (scroll down past the extremely well documented bugs in the withdrawn MSDE merge modules) and fix them with Orca. That said, the VB 6.0 runtime is under Windows File Protection on Windows 2000, Windows XP, Windows Server 2003 and I believe also on Windows Vista, so if you're only targetting those systems you can omit it. You should always use a merge module if one is available to ensure that you have the same definition of the components owning specific resources. If you don't, you can end up breaking the component rules - see Rob's blog post Component Rules 101 for things that can happen if you do. You can just about get away with breaking the rules for your private components, if your upgrade removes the old version of your product, but you really can't for shared ones. -- Mike Dimmick -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Leigh Sent: 14 March 2007 09:55 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] COM registration[Scanned] I'm guessing that Jacquet's app is written in VB6 and probably uses some DLLs that Microsoft provide. In which case, the files probably should go in system32, as they may already be installed... I'm in a similar situation - preparing to write my first WiX install, for a VB6 app. I'm guessing there's an msm out there somewhere to install the VB runtime files? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Hamflett Sent: 14 March 2007 09:40 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] COM registration[Scanned] Is the DLL shared just between your products or with other parts of the system? You're not really meant to put things in the system32 folder. Rob Jacquet Fabian wrote: Hi, I'm a new user of wix. I'm trying to convert a setup made with Package and Deployment Wizard of visual studio 6. This setup use some self register dll and some shared dll wich are in the system32 directory. Currently, I'm using tallow to generate registry keys of self register dll. And I just copy shared dll in the system32 directory. But I'm not sure if it's the best way to install those components. Could you help me? Thank you. - 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=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.phpp=sourceforgeCID=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.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] Set All Users desktop
I guess I just thought that 2 was more appropriate as a general setting because it doesn't cause an error during installation if the user is not running as an admin. If sending the shortcut to the all-users desktop is critical to the installation, than ALLUSERS=1 would indeed be better. I guess I should have made my answer more specific. - Brett _ From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 14, 2007 2:55 PM To: Brett Kapilik; wix-users@lists.sourceforge.net Subject: RE: Re: [WiX-users] Set All Users desktop 2? Why not 1? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brett Kapilik Sent: Wednesday, March 14, 2007 12:50 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Set All Users desktop Set the ALLUSERS property to 2. That should do it. - Brett _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bei Liu (Volt) Sent: Wednesday, March 14, 2007 2:44 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Set All Users desktop Can I set the desktop to point to all user? By using DesktopFolder, I can only set it to point to the per-user. Thanks, - 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 InstallShield msm files causes an error
There is no mechanism provided by the mergemod.dll to resequence CustomAction order. ResolveSource is one of those CustomActions that can live in many places... it sounds like the Merge Module isn't respecting that. You best bet is to not have it in the MSM at all. ResolveSource can cause some really unfortunate source prompts if not used carefully. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Svare Sent: Wednesday, March 14, 2007 2:30 PM To: Geoff Finger; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Using InstallShield msm files causes an error You should be able to set the sequence of the offending custom action from the msm in main WiX project I think. Thanks, Tom -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Geoff Finger Sent: Wednesday, March 14, 2007 4:21 PM To: wix-users@lists.sourceforge.net Cc: Thomas Svare Subject: Re: [WiX-users] Using InstallShield msm files causes an error Yeah, changing the sequence of ResolveSource from 525 to 1025 fixed it, thanks! Is there a way to override the sequence of an item in a Merge Module when you reference it, or am I going to have to run Orca and fix it manually every time I recompile? On 3/14/07, Thomas Svare [EMAIL PROTECTED] wrote: That should work. If you have any custom actions in your msm verify that the sequencing is after the cost standard actions. Thanks, Tom -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Geoff Finger Sent: Wednesday, March 14, 2007 1:04 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Using InstallShield msm files causes an error I'm trying to include a merge module from an older project that was made when we were using InstallShield to create our installations. When I try including it in my Wix project it compiles fine but when running it I get the error: Action start 16:32:36: ResolveSource. MSI (c) (EC:E0) [16:32:36:124]: Note: 1: 2732 2: 0 DEBUG: Error 2732: Directory Manager not initialized. The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2732. The arguments are: 0, , I tried using dark to decompile the msm file and recompiled it directly into a new Wix merge module, and that seems to work fine. So if necessary I can just do that instead, but it would be preferable to get the original msm working. Is there something extra I need to do in order to get InstallShield merge modules to work with Wix? Or are the two just fundamentally incompatible? (I tried searching the list archives for any info on this but I keep getting 500 - Internal Server Error) - 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=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.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] Intercepting SQL errors and displaying custom error
Is there a way to intercept SQL install errors and display my own custom error(s)? - 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] Custom Bitmaps
In v2 you used to be able to add custom bitmaps to the Dialogs. Has that changed in v3 or am I doing something wrong. I created a Sub-Directory called [Bitmaps] and added my own files for bannrbmp.bmp and dlgbmp.bmp. But when I compile the solution it doesn't override the bitmaps. Ryan PerlmanApplications Developer | +1(425) 703-8659 office | +1(206) 354-0838 mobile | IISBLK\5285 [cid:image001.png@01C765D5.82095E80]http://www.microsoft.com/windowsvista/default.mspx - 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] Custom Bitmaps
Follow the rules recently discussed for the license. The variables are: WixUIBannerBmp WixUIDialogBmp WixUIExclamationIco WixUIInfoIco WixUINewIco WixUIUpIco -- Mike Dimmick _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ryan Perlman Sent: 14 March 2007 22:41 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Custom Bitmaps In v2 you used to be able to add custom bitmaps to the Dialogs. Has that changed in v3 or am I doing something wrong. I created a Sub-Directory called [Bitmaps] and added my own files for bannrbmp.bmp and dlgbmp.bmp. But when I compile the solution it doesn't override the bitmaps. Ryan PerlmanApplications Developer | +1(425) 703-8659 office | +1(206) 354-0838 mobile | IISBLK\5285 http://www.microsoft.com/windowsvista/default.mspx vista attachment: image002.jpg - 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] Registry Value / Preprocessor issue
How would I set a registry value to: $(hClientWnd) $(Node) $(DBUserID) $(ConnectionString) $(Product) PackageReport ChangeDoc [EMAIL PROTECTED] If I use this: $(hClientWnd) $(Node) $(DBUserID) $(ConnectionString) $(Product) PackageReport ChangeDoc [EMAIL PROTECTED] Candle returns this error whether I escape the $ characters or not: error CNDL0149 : Ill-formed preprocessor variable 'hClientWnd'. Variables must have a prefix (like 'var.', 'env.', or 'sys.') and a name at least 1 character long. If I escape the first parenthesis, like this: $\(hClientWnd) $\(Node) $\(DBUserID) $\(ConnectionString) $\(Product) PackageReport ChangeDoc [EMAIL PROTECTED] It compiles fine, however, the string is inserted as the value exactly as typed, which is incorrect. So how can I set this registry value using WiX? - 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] Intercepting SQL errors and displaying custom error
Yes. Provide a .wxl file for the localization identifiers defined the .wixlib. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Don Tasanasanta Sent: Wednesday, March 14, 2007 3:34 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Intercepting SQL errors and displaying custom error Is there a way to intercept SQL install errors and display my own custom error(s)? - 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] Windows Installer 4.0 msi schema
Mike, Rob, Thank you both. I should have thought of v3.0 but I just can't stop using v2.0 for quick test purposes. Thanks, Tom From: Rob Mensching [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 14, 2007 5:09 PM To: Mike Dimmick; Thomas Svare; wix-users@lists.sourceforge.net Subject: RE: [WiX-users] Windows Installer 4.0 msi schema Although, if it is a standard MSI table you shouldn't need CustomTable at all (if you do, it's a bug in the WiX toolset smile/). From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Dimmick Sent: Wednesday, March 14, 2007 2:48 PM To: 'Thomas Svare'; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Windows Installer 4.0 msi schema The PatchCertificates element is supported in WiX v3.0, which generates MsiPatchCertificate table entries. If you need a table that isn't supported by WiX, you can use the CustomTable element. -- Mike Dimmick From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Svare Sent: 14 March 2007 21:18 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Windows Installer 4.0 msi schema Hello, I'm not sure if I'm phrasing this correctly but I'll throw it out there anyway... Is there any way with Wix to pick up new tables in the Windows Installer 4.0 msi schema? I'm particularly interested in the MSIPatchCertificate table. Thanks, Tom - 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] CustomAction and Working Directory
You need a Custom Action Type 34 to run an exe with a working directory. Try this: CustomAction Id='LaunchFile' Directory='INSTALLDIR' ExeCommand='[INSTALLDIR]install_silent.bat' Return='asyncNoWait' / K-ballo.- Charlie Grosvenor escribió: I am trying to run an application at the end of an install. The application needs files that are installed as part of the install and they need to be in the same directory. The CustomAction line I have is: CustomAction Id='LaunchFile' FileKey='install_silent.bat' ExeCommand='' Return='asyncWait' / The above is trying to start the application in “c:\windows\system32” not the application directory that it is installed in. Could somebody tell me what I am doing wrong? Also how to I run an application at uninstall? You can see my whole .wxs file below: ?xml version=1.0 encoding=utf-8? Wix xmlns=http://schemas.microsoft.com/wix/2006/wi; Product Id=AD2D4607-2DAF-4459-AB53-A5E6733CC27F UpgradeCode=95056130-FDDB-4835-BA81-F4CBBD2EFFAC Name=UltraVNC Hook Driver Language=1033 Version=1.0.0.0 Manufacturer=UltraVNC Package Description=UltraVNC Hook Driver Comments=UltraVNC Hook Driver InstallerVersion=200 Compressed=yes / Media Id=1 Cabinet=UltraVNC.cab EmbedCab=yes / Directory Id=TARGETDIR Name=SourceDir Directory Id=ProgramFilesFolder Directory Id=INSTALLLOCATION Name=UltraVNC Driver Component Id=ProductComponent Guid=35137132-23B9-45fc-BC37-8AF22A300C4E File Id='before.txt' Name='before.txt' DiskId='1' Source='ultravnc\driver\before.txt'/ File Id='install.bat' Name='install.bat' DiskId='1' Source='ultravnc\driver\install.bat'/ File Id='install_silent.bat' Name='install_silent.bat' DiskId='1' Source='ultravnc\driver\install_silent.bat'/ File Id='license.txt' Name='license.txt' DiskId='1' Source='ultravnc\driver\license.txt'/ File Id='setupdrv.exe' Name='setupdrv.exe' DiskId='1' Source='ultravnc\driver\setupdrv.exe'/ File Id='uninstall.bat' Name='uninstall.bat' DiskId='1' Source='ultravnc\driver\uninstall.bat'/ File Id='uninstall_silent.bat' Name='uninstall_silent.bat' DiskId='1' Source='ultravnc\driver\uninstall_silent.bat'/ File Id='vnccom.sys' Name='vnccom.sys' DiskId='1' Source='ultravnc\driver\vnccom.sys'/ File Id='vncdrv.dll' Name='vncdrv.dll' DiskId='1' Source='ultravnc\driver\vncdrv.dll'/ File Id='vncdrv.inf' Name='vncdrv.inf' DiskId='1' Source='ultravnc\driver\vncdrv.inf'/ File Id='vncdrv.sys' Name='vncdrv.sys' DiskId='1' Source='ultravnc\driver\vncdrv.sys'/ File Id='vnchelp.dll' Name='vnchelp.dll' DiskId='1' Source='ultravnc\driver\vnchelp.dll'/ /Component /Directory /Directory /Directory Condition Message='This application only runs on Windows XP' VersionNT = 501 /Condition InstallExecuteSequence Custom Action='LaunchFile' After='InstallFinalize'/ /InstallExecuteSequence CustomAction Id='LaunchFile' FileKey='install_silent.bat' ExeCommand='' Return='asyncWait' / Feature Id=UltraVNCFeature Title=UltraVNC Feature Level=1 ComponentRef Id=ProductComponent / /Feature /Product /Wix Thanks - 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] Can't make DiskPrompt to work
Igor Maslov wrote: Do I have to define VolumeLabel attribute for MediaTag in this case or it's optional? It's required -- see the MSI doc on the Media table, VolumeLabel column. -- 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.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Set All Users desktop
Brett Kapilik wrote: I guess I just thought that 2 was more appropriate as a general setting because it doesn't cause an error during installation if the user is not running as an admin. If sending the shortcut to the all-users desktop is critical to the installation, than ALLUSERS=1 would indeed be better. I guess I should have made my answer more specific. It takes a great deal of extra logic to properly support falling back to a true per-user setup. Non-admins can't install to Program Files, for example. It's more than just the profile directories. -- 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.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Costom feature selection control
Brian Cardiff wrote: I would like to know if there is a way to make a custom feature selecion control. Or at least, how to put and checkbox and enable or disable a particular feature. MSI doesn't support custom controls but you can make a custom dialog with checkboxes and use AddLocal and Remove control events to control which features are selected. -- 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.phpp=sourceforgeCID=DEVDEV ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom Bitmaps
Ryan Perlman wrote: Has that changed in v3 or am I doing something wrong. Yes, it changed. See WiX.chm topic Using the WixUI dialog library for details. -- 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.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Custom Bitmaps
Thank, for the previous pointer by Mike Dimmick For anyone else that may come across this issue: If you are compiling via the command line you can use the syntax, -dWixUIBannerBmp=path-to-banner-bmp If you are using this with your MSBuild environments or through the Visual Studio *.wixproj you can add the following to your *.wxs file. Say for instance you wanted to change the dlgbmp, bannrbmp and the License.rtf to match your particular brand and agreements. WixVariable Id=WixUIBannerBmp Overridable=yes Value=path-to-bannrbmp.bmp/ WixVariable Id=WixUIDialogBmp Overridable=yes Value=path-to-dlgbmp.bmp/ WixVariable Id=WixUILicenseRtf Overridable=yes Value= path-to-License.rtf/ Again thanks to Bob and Mike Message from Mike Dimmick Follow the rules recently discussed for the license. The variables are: WixUIBannerBmp WixUIDialogBmp WixUIExclamationIco WixUIInfoIco WixUINewIco WixUIUpIco Ryan PerlmanApplications Developer | +1(425) 703-8659 office | +1(206) 354-0838 mobile | IISBLK\5285 [cid:image001.png@01C7668E.EA366110]http://www.microsoft.com/windowsvista/default.mspx From: Bob Arnson [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 14, 2007 8:03 PM To: Ryan Perlman Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Custom Bitmaps Ryan Perlman wrote: Has that changed in v3 or am I doing something wrong. Yes, it changed. See WiX.chm topic Using the WixUI dialog library for details. -- 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.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
