Re: [WiX-users] Merge Module Help

For major updates, changing the GUIDs should not matter as it does an uninstall of the old version then an install of the new version. I just won't provide a patch to make that leap. This should be acceptable because it will be infrequent. For smaller changes, a minor upgrade via patch should be

Re: [WiX-users] Merge Module Help

I can't really answer intelligently to question #1, as to question #2, I'll do my best. Heat is really built for initial import functionality, not continual maintenance. You do not want your GUIDs changing on your components with each build, it will turn upgrades into a nightmare, and will make p

[WiX-users] Merge Module Help

I'm working on a fairly large installer. It contains roughly 7000 files in 165 folders and a total of 670 MB of uncompressed data. Needless to say, I'm generating the files, components, and directories using Heat. Right now, I'm generating a merge module WXS file using Heat and then using the Me

Re: [WiX-users] Help customizing FilesInUse Dialog

Disregard my previous comment. It is dialog ID which must remain "FilesInUse", of course, everything else can be customized. In my case which requires a lot of customization I have pulled in the entire WixUI_en-us.wxl and renamed it into CustomWixUI_en-us.wxl -Original Message- From: Nei

Re: [WiX-users] Help customizing FilesInUse Dialog

I don't really need to customize it's name, I simply want to override the default FilesInUse dialog. If there was some way I could distinguish between the name that the dialog gets in the MSI and the way I reference it in my I'd be all set. -Original Message- From: [EMAIL PROTECTED]

Re: [WiX-users] Help customizing FilesInUse Dialog

I was under the impression that runtime requires this dialog to have exactly FilesInUse name since it is invoked by installer, not by user. IOW, its name cannot be customized. -Original Message- From: Neil Enns [mailto:[EMAIL PROTECTED] Sent: Friday, July 18, 2008 5:03 PM To: General dis

Re: [WiX-users] Help customizing FilesInUse Dialog

Yup, I think so. Basically, we'd take the Wix UIExtension project as it stands, tweak the dialogs, and then compile that into our main installer as if it's the real Wix UIExtension. Of course, then we get into a much bigger maintenance situation. I'm not thrilled about this. -Original Me

Re: [WiX-users] Help customizing FilesInUse Dialog

Taking this approach will require literally pulling in everything, right? Including all the localization files for WiXUI_Minimal? Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Karper Sent: Friday, July 18, 2008 1:58 PM To: General dis

Re: [WiX-users] Help customizing FilesInUse Dialog

Are you using votive? And are you using the WixUIExtension? If so, I would imagine you can skip the extension, and just fully replace the FilesInUse name. Copy down all the rest of the UI wxs and just go to town. Chris On Fri, Jul 18, 2008 at 4:42 PM, Dan Giambalvo < [EMAIL PROTECTED]> wrote

[WiX-users] Help customizing FilesInUse Dialog

I'm in need of some help trying to customize the FilesInUse dialog for my app's installer. Our designers want to customize the look and feel of the entire installer, so starting with WIXUI_Minimal I've been making local copies of each dialog wxs file and then making modifications. This worked

Re: [WiX-users] A method for avoiding ICE38 error

Yes, writing ICE30 instead of ICE38 was a typo. Example with the current %userprofile% path that gets enumerated at heal time answers my question, thanks. Writing wouldn't cause key not to be written on install, as I thought. Clearly to be used as a keypath, something has to be written to the Reg

Re: [WiX-users] Automatically setting version number

Oh, thanks, how very sloppy of me. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Sleightholm Sent: Friday, July 18, 2008 11:21 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Automatically setting version number R

Re: [WiX-users] Automatically setting version number

Rob, I know I'm being picky but just in case anyone else is reading this, the syntax is "!(bind.FileVersion.)" i.e. ! not $ Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching Sent: 18 July 2008 18:22 To: General discussion for Windows Inst

Re: [WiX-users] using preprocessor variables in pre/postbuild stepsin VS2005

Steve, I am defining them in a WXI file using the preprocessor construct. They are then referenced in one or more WXS files (each WiX project are broken into multiple WXS files). Should I be using a different method? David J. Antoine -Original Message- From: [EMAIL PROTECTED]

Re: [WiX-users] Multiple Instances and Torch.exe

Ahh, got it. Yeah. Okay. Nothing in WiX v3 will show up for "instance-izing" your Components. It's a problem I'm still walking around trying to find a good solution for. Localizing Components is a similar problem and it be nice to have a good solution for both... but we're not doing feature

Re: [WiX-users] Localization filename change

While Rob wasn't part of the change, I was :) I'm looking for feedback on how to best approach tweaking this. One option that's been suggested is to not rename the MSI file, and to instead put them into subdirectories. So on a build you'd have $(TargetDir)\CultureName\$(TargetName)$(TargetExt).

Re: [WiX-users] Automatically setting version number

Correct. At this point, I tend towards "$(bind.FileVersion.)" instead of "$(bind.assemblyFileVersion.)" because FileVersion is always available. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Sleightholm Sent: Friday, July 18, 2008 09:52 To: Gen

Re: [WiX-users] Automatically setting version number

In addition I think I am correct in saying that !(bind.assemblyFileVersion.xxx) is not set unless you use the -fv option. It is a good idea though, I think I will be changing my installs. Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Mensching

Re: [WiX-users] Multiple Instances and Torch.exe

I referred to "NON file related data"...this goes back to the reference counting thread recently discussed. If I have a component that installs INI keys in the application target dir (INSTALLLOCATION); if I don't [instance-ize] that component (meaning that if I don't assign unique component gui

Re: [WiX-users] Automatically setting version number

I didn't explain the code, the idea of the is that you can build it on a dev machine without have to set the variable. Typically I set this to a number lower than the build number e.g. for build 1.2.xxx I would set it to 1.2.0. Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMA

Re: [WiX-users] Localization filename change

No need to escalate to a vote necessarily. We can have an open discussion about the change and what behavior people would like to see. Bob's comment was accurate but that doesn't mean the conversation has to end there. If you disagree about the change, let's just talk about it here and then g

Re: [WiX-users] Multiple Instances and Torch.exe

I don't understand what you mean here: "file related data (such as INI keys) for instances need to have their own component GUIDs." If the Component content is identical then you shouldn't put them in different Components. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTEC

Re: [WiX-users] Testing for existence of a Project Reference

Feel free to file a documentation bug if you think the documentation needs updating. The more detail you provide the more likely we get it fixed right. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Baker Sent: Friday, July 18, 2008 08:02 To: w

Re: [WiX-users] Automatically setting version number

Note, only the "assembly" binder variables require GAC'ing. If you use "$(bind.FileVersion.FileId)" then that will always work. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Enns Sent: Friday, July 18, 2008 08:32 To: General discussion for Windows

Re: [WiX-users] Create custom dialog for Votive & VS08 project - Radio Button to select different versions of same file

Ok, I've got the custom dialog worked out. I never found the files the WIX documentation specified, but I found some other samples online to look at. Now I'm stuck with a new problem. I'm using a radio button to specify which config file should be installed. The config file is always called con

Re: [WiX-users] Automatically setting version number

Neil, Awsome Idea! saves me a ton of work, including overriding Team Builds core target, now that I don't have to pass the version down through the msbuild stack to the wix project. Thanks for sharing it, Steve Baker From: Neil Enns <[EMAIL PROTECTED

Re: [WiX-users] WiX-users Digest, Vol 26, Issue 91

Bob Arnson <[EMAIL PROTECTED]> Subject: Re: [WiX-users] Custom UI Dialog errors To: "General discussion for Windows Installer XML toolset." Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Dane Anderson (Volt) wrote: > I am attempting to create

Re: [WiX-users] Automatically setting version number

This was my approach for a long time as well, but last week I changed to using a binder variable. The core application we install is always stamped with an assemblyversion by the build process. Instead of passing flags in via the Candle command line, or using a pre-processor variable, I now grab

Re: [WiX-users] Testing for existence of a Project Reference

Yes it does Rob, thank you. I looked at the documentation for the Preprocessor and do not see any examples of that syntax o_O Steve Baker From: Rob Mensching <[EMAIL PROTECTED]> Sent: Friday, July 18, 2008 3:25 AM To: "[EMAIL PROTECTED]" <[EMAIL PROTECTE

Re: [WiX-users] The Tooltip string is overflowed!

Hi Chris, Thanks for your reply! The problem is that I must get rid of all the warning, otherwise the central building server in my corp will reject my code :-(. And it is odd that although this warning exists, the MSI package works perfectly, that means, the tooltip string is shown completely du

Re: [WiX-users] Customizing GUI using wix3 beta 3.0.4311.0 fails

* Stephan Mueller <[EMAIL PROTECTED]> [18.07.2008]: > For me it looks like the WixUIExtension stuff in the binaries and the > wxs files from the source distribution for version 3.0.4311.0 differ. > Can anyone confirm this problem or show me how to fix this? Oomph. I am stupid. I forgot to update

Re: [WiX-users] Multiple Instances and Torch.exe

1. Nothing really is different from one component to the next, [that's my point] however non file related data (such as INI keys) for instances need to have their own component GUIDs. That means the component containing the INI keys gets duplicated for each instance. The only thing that chang

Re: [WiX-users] Executing Sql Stored Procedure from SqlString

oh ok... thanks for the reply. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Ope

Re: [WiX-users] Automatically setting version number

Thanks for the replies. I ended up using a wix pre-processor directive, like Neil suggested. I had to write a msbuild task to set the environment variable if it's not already set, however, since on a dev machine the variable would not normally be set (i.e. it's the build server that sets it),

[WiX-users] Customizing GUI using wix3 beta 3.0.4311.0 fails

Hi, I am currently trying to adjust the GUI of my msi Installation. I want to modify an existing dialog. I am following the howto from http://www.dizzymonkeydesign.com/blog/misc/adding-and-customizing-dlgs-in-wix-3/ Without changing anything and using -ext WixUIExtension everything works fine.

Re: [WiX-users] Localization filename change

Hi list, Please vote that this issue should be resolved. I guess many WiX users have scripts that are now broken by 3.0.4309.0. I have already opened a bug on sourceforge on this issue. https://sourceforge.net/tracker/?func=detail&atid=642714&aid=2020595&group_id=105970 The bug was closed with

[WiX-users] Create custom dialog for Votive & VS08 project

How can I create a custom dialog with a radiobutton group using Votive? I've found instructions for doing so at: http://wix.sourceforge.net/manual-wix2/WixUI_dialog_library.htm but it looks like they don't apply to Votive. Under the "Customizing dialog sets" section, several files are list

Re: [WiX-users] Automatically setting version number

I write an msbuild action, but I have lot's of custom activity, so I have a .targets file of my own that I include in my new projects. That makes it easier to remember, and quick to fix once I find it missing. I like your $(var) method though. Chris On Fri, Jul 18, 2008 at 6:48 AM, Neil Sleigh

Re: [WiX-users] The Tooltip string is overflowed!

Is the property formattable? If so, you could assign a property value to it. But, the fact is, that is a valid warning. Wix just puts the string into a table in the resulting .msi/.msm and that technology imposes limits on it's content. If you want to use the installer, you have to play by t

[WiX-users] Localization filename change

Hi folks, adding the culture to the output file is a nice feature, if you have more than one language to maintain. In our case this is somewhat disturbing. We use standard wix dialogs wher we change the font size with localized values. Therefore it is required to add a wxl file. This results in

Re: [WiX-users] Automatically setting version number

1. I think it is ok but Windows Installer will ignore the 4th part. 2. I pass the version in on the candle command line and use code like this in the wxs file: Neil Neil Sleightholm X2 Systems Limited [EMAIL PROTECTED]

[WiX-users] Automatically setting version number

Hi, I've got a CI setup that automatically generates a x.x.x.x style version number. I've got all my assemblies versioned properly (with a generated shared SolutionInfo.cs file), and I set the msi output name as MyMSI-x.x.x.x.msi and now I want to set the Version attribute of the Product tag.

[WiX-users] The Tooltip string is overflowed!

Hi folks, I wrote this UI code in WiX 3.0. And the compiler complained that "Warning33ICE03: String overflow (greater than length permitted in column); Table: Control, Column: Help, Key(s): NRconfigParametersDlg.NR_DBIPEd

Re: [WiX-users] Component Rules

I'm not sure where this thread is at so I'll just jump in here since it's close to the answer. The Windows Installer handles Files slightly more gently than all of the other Resources (registry keys, shortcuts, etc). In particular, the same Component can install the same File to different Dire

Re: [WiX-users] Multiple Instances and Torch.exe

2. Well, I'm glad we finally built something useful.You can thank Peter Marcu, it was his feature. 1. I don't really understand what is different from one Component to the next. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Nannenga Sent: We

Re: [WiX-users] Executing Sql Stored Procedure from SqlString

SqlString only executes as a deferred custom action and does not set properties based on results of queries. So, no... but it is a totally reasonable feature request. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of sai rahul Sent: Thursday, July 17, 200

Re: [WiX-users] Testing for existence of a Project Reference

Does the following work...? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Baker Sent: Thursday, July 17, 2008 16:12 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Testing for existence of a Project Reference Thanks bob, i missed

Re: [WiX-users] HowTo install a MSHelp2 collection into VS2005 or VS2008

Get the MS HTML Help team to release proper Merge Modules. That would go a long way. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Francois Retief Sent: Thursday, July 17, 2008 23:50 To: wix-users@lists.sourceforge.net Subject: [WiX-users] HowTo instal

Re: [WiX-users] Merge module question

I consider Merge Modules more like a .DLL than a static library even though it gets merged into the MSI. I look at it that way because there are so many boundaries between the Merge Module and the MSI (modularization of the primary keys) and the fact that Merge Modules are intended to be redist

Re: [WiX-users] creating Localized installer.

Windows Installer does not support that. You need a bootstrapper to detect and either pick the right package or apply language transform when doing install. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of bhupendra Sent: Thursday, July 17, 2008 23:38 To:

Re: [WiX-users] rollback after removing backup files

There is a COMMONDATA message sent before the rollback is being cleaned up that instructs the UI to hide the Cancel button. I suppose it is possible some installs are not respecting that message correctly. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf

Re: [WiX-users] Merge module question

> By extension, we do not need tools like WiX as we don't need > tools like compilers. We can all hack binary codes directly > to the processor and be done with it. > > BTW, .msm is like a .o to a .c I think of them more like a static library, i.e. a .lib file ... :) john

[WiX-users] rollback after removing backup files

I can't roll back when the installer/uninstaller is at removing backup files stage..MSI gracefully exits without rolling back though user clicks 'Yes" on the rollback confirmation dialog. I have noticed this behavior with many different MSI based applicaitons downloaded Is this the expected MSI be