[WiX-users] What happened to Error and Warning details in VS 2005 Output window?

Hello, After upgrading from 3.0.2925.0 to 3.0.4401.0 I noticed that while building in Visual Studio 2005 the error and warning detail info no longer appears in the Output window. Is there a setting somewhere to turn this back on? I've tried enabling Verbose output in the project properties. T

Re: [WiX-users] Installing different version of file depending on OS

on OS You might consider putting the conditions in the Component and marking the Component/@Transitive="yes" so that the right file gets repaired if the user upgrades their OS. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Schuett, Michael Sent:

[WiX-users] Installing different version of file depending on OS

Hello, I need to install a different version of a file depending on the OS. The installed file needs to have the same name. Here's my code that works if the VersionNT=500 Versio

Re: [WiX-users] Accented character in Shortcut Name causes Error LGHT0204: ICE03: Invalid Filename

: [WiX-users] Accented character in Shortcut Name causes Error LGHT0204: ICE03: Invalid Filename Schuett, Michael wrote: > Hello, > > If I use an accented character in a Shortcut Name, the following error > results... > > D:\WiX\ClientInstall\Application.wxs(39,0): Error LGHT0204

[WiX-users] Accented character in Shortcut Name causes Error LGHT0204: ICE03: Invalid Filename

Hello, If I use an accented character in a Shortcut Name, the following error results... D:\WiX\ClientInstall\Application.wxs(39,0): Error LGHT0204: ICE03: Invalid Filename; Table: Shortcut, Column: Name, Key(s): TrayAppShortcut Here's the section from Application.wxs. If I remove the

[WiX-users] Building a patch in Visual Studio

Is it possible to build a patch inside VS2005? All I've been able to generate is a useless MSI. Thanks, Mike - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Sear

[WiX-users] LGHT0102 errors on localized builds

Hello, I'm having problems with dozens of LGHT0102 errors when I perform a localized build. (I'm using 3.0.2925.0 and VS2005.) The project builds fine when the culture is en-us, but fails when I use a different culture. I've tried de-de, es-es, fr-fr and it-it. The LGHT0102 errors are all on lo

[WiX-users] Conditional Statement Problem

Hello, I'm reading a DWORD value from the registry using RegistrySearch. (WiX 3.0.2925.0) I understand DA_VER is an empty string if "Version" isn't found. If it is found, DA_VER will start with '#' followed by the value of Version. I want to bail out of the install if the DWORD value d