Re: [WiX-users] Does Pyro (or Torch) ignore 4-th version number?

It just goes to show how easy it is to commit gross component rules violations even after months of reading articles and blogs on component rules! However, it seems that I have also misunderstood the purpose of MSIENFORCEUPGRADECOMPONENTRULES property. I was under the impression that it would add

[WiX-users] Upgrade with new Microsoft libraries

On a project which has been upgraded from Visual Studio 2005 to 2008 running an upgrade on the MSI package not work correctly. The reason for this is that the project is dependent on the Microsoft CRT libraries. Previously the library was included in the install as follows: N

Re: [WiX-users] WebSites in ComboBox dynamically

Hello Alexei and All, I'm new to Wix. I'm trying to make a installer for website - something similar to what visual studio IDE provides. I've tried using the two scripts mentioned in the posts here to populate the combo box with the websites available on a machine as well as set the port of the

Re: [WiX-users] Call a .NET dll file in wix using custom

But still I have a problem when I try to run a html file, although DLfetcher is registered in gac, issue is as follows: DLFetcher Component is not registered[object error] Html file: try { ob1 = new ActiveXObject("DLFetcher.RetreiveDL"); alert(ob1); if(ob1!=null)

Re: [WiX-users] Upgrade with new Microsoft libraries

This is only the beginning of your pains. My recommendation is to switch to a major upgrade. http://msdn.microsoft.com/en-us/library/aa369786(VS.85).aspx http://blogs.technet.com/alexshev/archive/2008/02/15/from-msi-to-wix-par t-8-major-upgrade.aspx cheers dB. -Original Message- From: [E

[WiX-users] WindowsFolder variable is not getting picked up

Hi, I have the following Property element within my WiX source file: Its parent is the Product element for the feature installed. For some reason, the MSI gets built without error, but the installer barfs, with logs showing that the [WindowsFolder] string was never resolved into the fold

[WiX-users] Heat - Controling Component Generation

Hi, I have two questions about the functionality of Heat.exe. First, is there a to get heat.exe to generate 64-bit components? Right now it is giving me something like: And I would like something like: > And secondly, is there any way for it to output relative directory paths? Right n

Re: [WiX-users] WindowsFolder variable is not getting picked up

WiX element creates a record in the Property table (http://msdn.microsoft.com/en-us/library/aa370908(VS.85).aspx). As you can see, the type of the Value column in this table is Text (not Formatted). Also, Remarks section has the following: "Note that you cannot use the Property table to set

Re: [WiX-users] WindowsFolder variable is not getting picked up

I don't believe the element supports formatted strings, if you are using WiX v4 try using the element. Otherwise you will need to do it with a custom action. Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greg Silin Sent: 06 August 2008 16:44 To:

Re: [WiX-users] Heat - Controling Component Generation

I use the regex search and replace too. Which harvester are you using? I can take a look to see how hard it would be to add support for that, but as far as I know, these things are not currently possible, and no one is working on heat other than myself. Chris On Wed, Aug 6, 2008 at 12:01 PM,

Re: [WiX-users] WindowsFolder variable is not getting picked up

Wix v4? Did I miss something? On Wed, Aug 6, 2008 at 12:07 PM, Neil Sleightholm <[EMAIL PROTECTED]>wrote: > I don't believe the element supports formatted strings, if > you are using WiX v4 try using the element. Otherwise you > will need to do it with a custom action. > > Neil > > -Origin

Re: [WiX-users] Upgrade with new Microsoft libraries

You've probably broken the component rules be deleting components and replacing them with others. This will result in the "advertised feature" behavior and updates not being done. If you take a log of the install I think you'd see SELMGR errors. A major upgrade would be the cure, as was suggest

Re: [WiX-users] WindowsFolder variable is not getting picked up

Yes that's the version that just "knows" what we want to do and writes the code for us! As I'm sure you all guessed it meant v3. Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Karper Sent: 06 August 2008 18:24 To: General discussion for

Re: [WiX-users] Heat - Controling Component Generation

I am using the directory harvester. Thanks Chris. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Karper Sent: Wednesday, August 06, 2008 11:24 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Heat - Contr

[WiX-users] Custom Actions

I'm creating an installer that executes an embedded vbscript on install an a vbscript on uninstall. Why does it want to run both scripts on the install. And this gives me an error on the install: Not Installed Custom4 is the vbscript that removes a shortcut, but it wants to run on the inst

Re: [WiX-users] Custom Actions

Custom4 runs during the install because your condition is "Not Installed". -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jonathan Moore Sent: Wednesday, August 06, 2008 2:34 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Custom Actions I'm

[WiX-users] How to preserve INI file during major upgrade

I have a WiX installer which includes merge modules for the Visual Studio 2005 CRT. I'm moving the project to Visual Studio 2008, and now the merge modules are different (for example, Microsoft_VC90_CRT_x86.msm instead of Microsoft_VC80_CRT_x86.msm). I would like to distribute this change as a

Re: [WiX-users] How to preserve INI file during major upgrade

Where is your RemoveExistingProducts action scheduled? Ref: http://msdn.microsoft.com/en-us/library/aa371197(VS.85).aspx From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Jim Flood [EMAIL PROTECTED] Sent: Wednesday, August 06, 2008 4:26 PM To: wi

Re: [WiX-users] WindowsFolder variable is not getting picked up

Must be a typo... that's a WiX v3 feature. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Karper Sent: Wednesday, August 06, 2008 10:24 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] WindowsFolder variabl

Re: [WiX-users] Does Pyro (or Torch) ignore 4-th version number?

Just to make my life easier, now that I corrected the mistake and double-checked that I haven't committed component violation again, I am back to having exactly the same problem. Pyro doesn't find anything to put in a patch cab and running verbose log doesn't reveal anything. Even a nice tool like

[WiX-users] New wix binary delta patching doesn't work

I can confirm this now that I produced two MSIs that don't have any component rules problems. Some history of this problem can be found in posts titled 'Does Pyro (or Torch) ignore 4-th version number?'. I have 2 MSIs and 2 corresponding binary wixout files. Using new patching with wixout input pr

Re: [WiX-users] New wix binary delta patching doesn't work

Tony Juricic wrote: > I have 2 MSIs and 2 corresponding binary wixout files. Using new > patching with wixout input produced a msp file which applied > transformation to the original database (i.e. I could see that product > version was changed in ARP after patch application) but none of the > bina

Re: [WiX-users] Custom Actions

Jonathan Moore wrote: > Custom4 is the vbscript that removes a shortcut You shouldn't use VBScript custom actions. MSI automatically removes shortcuts it installs but if you need to "clean up" extra files, use the RemoveFile element.

Re: [WiX-users] WindowsFolder variable is not getting picked up

Greg Silin wrote: > Value='[WindowsFolder]\Microsoft.NET\Framework\v2.0.50727\InstallUtil.exe'/> > InstallUtil should be avoided; it's the managed-code equivalent of self-registration . You should replace its use with native MSI ele

Re: [WiX-users] Heat - Controling Component Generation

Ahearn Stevens wrote: > First, is there a to get heat.exe to generate 64-bit components? No, but unless you need to mix and match 32-bit and 64-bit components 50/50, it's easier to use the -arch switch (or the InstallerPlatform property in a .wixproj) to switch them at build time. > And secon

Re: [WiX-users] Font not correct when uninstall from control panel

The font used in the basic UI can be set using the DefaultUIFont property: http://msdn.microsoft.com/en-us/library/aa368266(VS.85).aspx -- View this message in context: http://www.nabble.com/Font-not-correct-when-uninstall-from-control-panel-tp18088307p18864176.html Sent from the wix-users mail