patearl wrote Jan 25 at 10:16 PM

You were right on the money. Setting the tools version fixed it.

icnocop wrote Jan 25 at 7:24 AM

I noticed from your screenshot that msbuild.exe v2 is being used. I don't think it can load .net v4 assemblies unless you create a new app domain etc. I am wondering if adding ToolsVersion="4.0" to your msbuild script will resolve the issue? For example, this is the first line in an msbuild.exe v4 script file: <Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003" ToolsVersion="4.0">

icnocop wrote Jan 25 at 7:18 AM

I am wondering if you can attach a sample project that can reproduce the unexpected behavior please? Thank you.

patearl wrote Jan 23 at 6:00 PM

4.0 full

icnocop wrote Jan 20 at 11:40 PM

What version of .net does Pleasant.Build.dll target?

patearl wrote Jan 20 at 11:14 PM

The problem is with a custom task dll that depends on other dlls. We have an AssemblyResolve hook to find assemblies in the same folder, but it seems that your shell extension runs it in a different way than MSBuild does. Perhaps the .Location of the primary assembly is different.

ThomasArdal wrote Jan 20 at 5:25 AM

Could you provide us with a screenshot of the bug you are experiencing? I don't fully understand what your problem is.

patearl wrote Jan 19 at 9:19 PM

If I had to take a random stab in the dark, I'd guess that there's some sort of differences between how msbuild and your app handle working directories.

patearl wrote Jan 19 at 8:52 PM

Is there a way to obtain that information? The error output is truncated as mentioned in the other issue.

ThomasArdal wrote Jan 19 at 7:55 PM

Could you provide a stacktrace or something more, which could help us fix this?