search

wixtoolset / issues

WiX Toolset Issues Tracker
http://wixtoolset.org/
129 stars 36 forks source link

Microsoft.Build.Tasks.v4.0 not found #2505

Closed wixbot closed 8 years ago

wixbot commented 14 years ago

I have just started using Wix with CruiseControl.NET, but the build is breaking. The error is as follows:

C:\Program Files\MSBuild\Microsoft\WiX\v3.5\Wix2010.targets(883,5): error MSB4062: The "AssignProjectConfiguration" task could not be loaded from the assembly Microsoft.Build.Tasks.v4.0, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a. Could not load file or assembly 'Microsoft.Build.Tasks.v4.0, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. Confirm that the declaration is correct, and that the assembly and all its dependencies are available. Done Building Project "C:\ccnet_temp\MyProject\MyProjectInstaller\MyProjectInstaller.wixproj" (default targets) -- FAILED.

The Microsoft.Build.Tasks.v4.0.dll is in the GAC and has the correct PublicKeyToken.

Any ideas?

Originally opened by daggmano from http://sourceforge.net/p/wix/bugs/1961/

wixbot commented 12 years ago

This should be working with latest build of WiX v3.5 and RTM VS2010

wixbot commented 12 years ago

This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker).

wixbot commented 12 years ago

Does it repro with VS2010 RTM? Can you run fusion log viewer, set it to log failures, and then paste or link me to the error log?

wixbot commented 12 years ago

I should add that the project build correctly within VS2010 RC. The solution is targeting .NET v3.5 SP1.

wixbot commented 12 years ago

Further investigation: Using Dependency Walker on Microsoft.Build.Tasks v4.0, I found it was missing IEShims.dll. Adding %ProgramFiles%\Internet Explorer to the PATH variable fixed this, but I'm still stuck with missing exports in IEFrame.dll and ShLWAPI.dll. Oh, and I found that MS.Build.Tasks 4.0 wasn't in C:\Windows\assembly, but instead in C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Microsoft.Build.Tasks.v4.0\v4.0_4.0.0.0_b03...a3a. Is this an issue?