Analysis Failure on .net 4.5.1 assembly

I'm using the newest version of NCrunch in Visual Studio 2013 Preview. It is unable to load any 4.5.1 assemblies, giving a BadImageFormatException.

Is there any plans to move NCrunch to 4.5.1?

Absolutely. VS2013 is still very new, so any testing with it has so far been very light. My early tests with 4.5.1 templates showed that NCrunch was able to load assemblies, although after checking this now, it appears that NCrunch needs a new loader in order to handle this properly. I'll get to work on implementing this. Thanks for reporting the issue.

Cheers,

Remco

I've just released a fix for this. If you download the latest 1.46 revision, NCrunch should be able to work with .NET 4.5.1 projects in VS2013.

I'm downloading it now. Will give it a try. Thanks!

I am from Microsoft .NET Framework team. I tried to reproduce with problem with .NET 4.5.1 but it works correctly for me.

Hi Remco- it looks like you are able to reproduce the problem. Could you contact us on netfx45compat at Microsoft dot com with description of the issue? Thank you for your help.

Sincerely
Varun

Hi Varun -

Thanks for getting in touch. I'll follow up with you directly.


Cheers,

Remco

Thanks Remco for contacting me and clarifying that this is NOT an issue with .NET 4.5.1.

From: Remco Mulder (snipped email address)
Hi Varun –

I’m following up on a contact request posted on the NCrunch support forum around a compatibility issue between NCrunch and .NET 4.5.1:

http://forum.ncrunch.net/yaf_postsm4468_Analysis-Failure-on--net-4-5-1-assembly.aspx#post4468

After looking into the issue on the side of NCrunch, I was able to conclude that this is not a problem with the .NET framework. NCrunch was making assumptions about the ToolsVersion specified in the build script. These assumptions turned out to be incorrect under VS2013 (where the ToolsVersion was changed). The result was that it was trying to build projects with the wrong version of the .NET framework. The problem has since been resolved.

I very much appreciate the effort taken to approach me directly on this – it really shows strong commitment from the side of Microsoft towards .NET framework compability .. which I applaud!