Project won't build after upgrade

I have a solution with two projects in it, a class library and a unit test project. It builds with 1.45.0.28, but not with 1.46. I have also recently upgraded to Update #3 of Visual Studio 2012. I followed your suggestions in a similar post regarding compatibility mode and logging verbosity and nothing helped. I tried each compatibility mode setting individually and all together and I got the same results every time. Also, setting logging verbosity to detailed didn't reveal anything.

The error I am getting is this:

[10:22:17.9057-BuildTask-41] ERROR (Compilation): BackOffice.Shared.Implementation: (0): System.NullReferenceException: Object reference not set to an instance of an object.
at nCrunch.Compiler.AssemblyHashGenerator.#=qtI5WjtQ6W7jurcs0mlLGQw==(BinaryWriter #=qX376nfPjMT8xjiz3nE9lv8$aZvYyQFncyQvOIXTpcsg=, TypeDefinition #=qujMjBraqFfuBl45sHneolA==)
at nCrunch.Compiler.AssemblyHashGenerator.#=qtI5WjtQ6W7jurcs0mlLGQw==(BinaryWriter #=qX376nfPjMT8xjiz3nE9lv8$aZvYyQFncyQvOIXTpcsg=, TypeDefinition #=qujMjBraqFfuBl45sHneolA==)
at nCrunch.Compiler.AssemblyHashGenerator.ComputeHashForAssembly(AssemblyDefinition assembly)
at nCrunch.Compiler.StaticManipulation.BuiltAssembly.GenerateSurfaceHash()
at nCrunch.Compiler.RemoteBuildRunner.#=qj7DUZX08ktIo$6w9YGDpA_eD7Sc7EX6yRcprQDAPeDQ=(ComponentBuildParameters #=qzzXWNrdeSVhZa1PyfpksWg==, String #=qUWBtkgkJpPlEHXO$2aePHOUrf4lm2Cm_4N2auMQpXU8=, BuildOutput #=q46FEkiLbRtvybXRsg1M7VQ==, String #=qI3wPSur6wzzKPh0SFLiQGVAxL1EcO5$zfNMit9VRaV4=, String[] #=qFy14k8sndtoNd1Moov9ZjZ2OQodzqX6daoT8juD6UHE=)
at nCrunch.Compiler.RemoteBuildRunner.Build(ComponentBuildParameters parameters)

Hi,

Sorry this appears to be a regression caused by the 1.46 release which is causing NCrunch to blow up while trying to process a public NULL constant field in your project.

I'm introducing a fix at the moment and will have a new build up with a resolution very soon. Thanks for reporting this issue so promptly!


Cheers,

Remco

I've just pushed out a new revision of the 1.46 release (1.46.0.11) with a fix for this issue. If you redownload and install, the issue should be resolved. Sorry for the trouble.