[wix-users] ETA for WiX 3.11 release?

Christopher Painter chrpai at iswix.com
Thu Jan 5 03:50:17 PST 2017

Yes.  I found the thread you talked about, Heath's blog and the nuget package that has the wrapper to do it.

It didn't work... blew up with exceptions.  I left a comment on Heaths blog as such.   I also left a comment regarding the WIP.   I'm not currently using Burn.   I simply use the propertyrefs  and CopyFile elements that cause a copy to happen if the property has a value.   But this is static... say 2008,10,12,13,15.    It's not dynamic for multiple instances.   So it'd also be interesting to consider temp records to register with all found instances.

I guess where I'm left is....

Good news:  If I manually copy all my WiX and IsWiX components in place it all still seems to work!  Whew.

Bad news: what you said.  You made a comment like you were waiting for someone to do the work but from reading the tea leaves I'm not sure you guys approve of the custom action and COM object called for in the WIP.  I don't blame you... I'm guessing this is one of those we don't have much choice.  I'd love to help but I don't have the C++ chops to be honest.  I only do C#/DTF CAs these days.

Going forward:  I'm just going to have to follow your lead.  Whatever WiX does to burn and the .net extensions to support all of this is just what I'll have to go with.  I'm not going to hack something together myself ahead of a WiX release. It's just too ugly this time.

My final though is that this is further evidence of why I keep my application code and installer code in two different solutions.    This way a developer can jump to the bleeding edge in the solution they really care about.

From: wix-users <wix-users-bounces at lists.wixtoolset.org> on behalf of Rob Mensching <rob at firegiant.com>
Sent: Wednesday, January 4, 2017 10:41 PM
To: WiX Toolset Users Mailing List
Subject: Re: [wix-users] ETA for WiX 3.11 release?

Finding this path: "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild" is the problem.

 Short replies here. Complete answers over there: http://www.firegiant.com/
WiX Support | WiX Experts and Resources from FireGiant<http://www.firegiant.com/>
WiX Support | Installation, Development, Deployment | WiX Experts and Resources from FireGiant

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Christopher Painter
Sent: Wednesday, January 4, 2017 6:30 PM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] ETA for WiX 3.11 release?

I've been able to easily (manually)  get WiX v3.10.3 to work on VS 2017 CE.    I now have enough to take a snapshot and work on getting IsWiX to install on top of VS/WIX.

Here are my notes:

Starting Point:

Server 2016  with only .NET 4.6 preinstalled and VS 2017 Community Edition RC.


Using WiX 3.10.3 bits from my development machine, I followed the procedures that I outlined back in 2013 changing the directory names (easy to find) and version number to 17.0



Launched VS and the WiX project templates appeared.  However, I got an error when I tried to create a setup project saying that the wix.targets wasn't in VS 2017 CE's private MSBuild directory.

(The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\WiX\v3.x\Wix.Targets" was not found.

step 2: copy targets to private msbuild directory inside visual studio 2017


I was able to create the setup project but I got an error when I attempted to build it.

C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\WiX\v3.x\wix2010.targets(1988,5): error MSB4062: The "GenerateCompileWithObjectPath" task could not be loaded from the assembly C:\Program Files (x86)\WiX Toolset v3.10\bin\\WixTasks.dll. Could not load file or assembly 'Microsoft.Build.Utilities, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.
Done building project "SetupProject2.wixproj" -- FAILED.

step 3:  Install .NET 2.0/3.5 windows component

result:  successfully built setup project

WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

More information about the wix-users mailing list