StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>As per the <a href="http://wix.sourceforge.net/manual-wix3/daily_builds.htm" rel="nofollow">page</a> provided by you, the path entered in the lines of code will help the MSBuild script to identify the WIX binaries.</p> <pre><code><PropertyGroup> <WixToolPath>$(SourceCodeControlRoot)\wix\3.6.3220.0\</WixToolPath> <WixTargetsPath>$(WixToolPath)Wix.targets</WixTargetsPath> <WixTasksPath>$(WixToolPath)wixtasks.dll</WixTasksPath> </PropertyGroup> </code></pre> <p>The important quote here goes like:</p> <blockquote> <p>WixTargetsPath property value must be relative to the .wixproj project file that uses it. The WixTasksPath property is used inside wix.targets to load WixTasks.dll</p> </blockquote> <p>The paths should be specified properly according to the folders where you unzipped your files. Otherwise there is a chance for this error to happen. Then also the project will be running fine from VS2010 since that is reffering the WIX binaries from the installed location of WIX. But, MSBuild will refer the values you provide in the above lines of code.</p> <p>So, can you please provide values you are giving for <code>WixToolPath</code>, <code>WixTargetsPath</code> and <code>WixTasksPath</code>. As well the path to where you are unzipping the <strong>wix36-binaries.zip</strong> or <strong>wix37-binaries.zip</strong>.</p> <p>These information may help in solving this issue and accordingly I will correct this answer as well.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload