[WiX-users] WiX 3.6 LICENSE.txt - still copyright Microsoft?

I noticed all the files in the WiX repository have been updated with "Copyright (c) 2004, Outercurve Foundation" - except LICENSE.txt. Was that deliberate, or should that have been updated too? -- Bruce Cran -- Live Sec

Re: [WiX-users] Code pages and UTF XML etc.

Follow-up on my own question. It seems that if one explicitly states the Codepage attribute in the Product element as 1252 the characters I was having trouble with do not produce any further problem. This seems to be a bug relative to the error message; we're still using WiX 3.5.2519.0 if that h

[WiX-users] vcredist_x86.exe Package DownloadUrl

I was using a DownloadUrl from Microsoft as a burn package. Today, this url no longer exists. Is there an official site Microsoft will maintain or do I need to copy this file to my server? Can I legally post it on my server? I notice some use this url: http://go.microsoft.com/fwlink/?LinkID=2106

Re: [WiX-users] DisplayInternalUI in MsiPackage Issues

> >>>First, the progress bar in the MSI UI doesn't show any progress while >>>it >is installing. It this universally >>the case? Has anyone else seen this? > > >I'm also having this issue, are there any solutions? > > >Thanks I've found a kludge that has seemed to work so far. It is bound to cause

Re: [WiX-users] WiX Suppress ICE Validation When Using MSBUILD At The Commandline

You don't need to had the element to your .wixproj first. If you do not want to suppress ICE by default then don't include the element. When you call MSBuild from the command line and specify /p:SuppressIces="..." you'll still get the behavior you want. Be aware that if you do add a element

Re: [WiX-users] Relative Path cause Light unable to find sourcefiles.

The first thing that comes to mind when relative paths are not found is that the expectation of the current working directory is incorrect. I believe that the WiX MSBuild tasks used by .wixproj use the location where the .wixproj exists as the working directory requiring that any relative paths

Re: [WiX-users] Convert reg to wxs using heat and linking the fileswith main project

Heat is used to generate source code. It's used to prepare the first version of your MSI. You then manually tweak the code. It's just a labour saving device to prevent you having to write out lots of component definitions. Any wxs files produced by heat, or by your editor, are processed by candle.

[WiX-users] Code pages and UTF XML etc.

I'm working (as usual) on our front end, InstallerBuilder. We are in a multilingual environment, and one which often involves several languages being used semi-simultaneously. The convention for one of our applications (recently upgraded and now to be installed using MSI, etc.) is to have a sho

[WiX-users] Convert reg to wxs using heat and linking the files with main project

Hi, As a WIX newbie I'm not sure on how heat, candle, light etc. all link and work together. I have looked online and the best I can find it snippets on how to link these together and I am getting more confused. Can anyone point me in the right direction to a tutorial or help me out. I have

Re: [WiX-users] How to include a configuration-dependent project output in WiX 3.6 & Visual Studio 2010

And here's candle's command prompt, when using msbuild from command line: %windir%\Microsoft.NET\Framework\v4.0.30319\MsBuild.exe /verbosity:d /t:rebuild /fileLogger /p:Configuration=Release Wix_ProjectOutput.sln In msbuild.log: C:\Program Files\WiX Toolset v3.6\bin\candle.exe -d"DevEnvDir=Unde

Re: [WiX-users] How to include a configuration-dependent project output in WiX 3.6 & Visual Studio 2010

Here's candle's command prompt from VS output window: -- Rebuild All started: Project: *MySetup, Configuration: Release* x86 -- C:\Program Files\WiX Toolset v3.6\bin\candle.exe -d"DevEnvDir=C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\\" -dSolutionDir=D:\Projects\Resea

Re: [WiX-users] WiX Suppress ICE Validation When Using MSBUILD At The Commandline

Hi, I guess you need an initial property (it will not be there untill you add it manually once) like the one below in your wixproj file: ICE82;ICE03: > Thanks, Palbinder > > That lead me to the problem. All of the settings for my wixproj were under > the Release configuration but MSBUILD was

Re: [WiX-users] Relative Path cause Light unable to findsourcefiles.

If you insert the pre-processor variable $(sys.SOURCEFILEDIR) in the front of the path, does that fix it ? That's assuming your current directory is the directory of the wxs file or wixproj. If not, you might need to insert some ..s etc. -Original Message- From: shengyixing [mailto:shengyi

Re: [WiX-users] Unable to create shortcut. MSI error 1909

You can't install to ProgramFilesFolder on XP without admin permissions so the executable will not install. The shortcut creation will be failing because the executable doesn't exist. -Original Message- From: candy.chiu...@gmail.com [mailto:candy.chiu...@gmail.com] Sent: 16 August 2012 17