I'm guessing this is due to changes in VS2012 loading builds out of proc to
easy memory pressure. I'd say you were getting lucky before. If you have a
dependency, you should keep it near you.
Also, the WiX toolset isn't designed to be installed in the GAC so I would
not recommend that route. We do
Hey all,
I have a custom Heat task, aka. a class derived from HeatTask. It works fine
under Wix3.5 and Wix3.6 in Visual Studio 2008.
A problem arises is under Wix3.6 and VS2012. When building in VS2012, the
WixTasks.dll dependency can't be found.
It would appear (from using ProcMon) that in VS
2 matches
Mail list logo
