Just installed 1.48 and got a "Unable to find assembly Gallio"

Just installed the 1.48.0.5 for VS2013 and NCrunch, after loading all projects, gives me the error System.Runtime.Serialization.SerializationException: Unable to find assembly 'Gallio, Version=0.0.0.0, Culture=neutral, PublicKeyToken=eb9cfa67ee6ab36e'. for all projects

Here's the full stack
at System.Runtime.Serialization.Formatters.Binary.BinaryAssemblyInfo.GetAssembly()
at System.Runtime.Serialization.Formatters.Binary.ObjectReader.GetType(BinaryAssemblyInfo assemblyInfo, String name)
at System.Runtime.Serialization.Formatters.Binary.ObjectMap..ctor(String objectName, String[] memberNames, BinaryTypeEnum[] binaryTypeEnumA, Object[] typeInformationA, Int32[] memberAssemIds, ObjectReader objectReader, Int32 objectId, BinaryAssemblyInfo assemblyInfo, SizedArray assemIdToAssemblyTable)
at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadObjectWithMapTyped(BinaryObjectWithMapTyped record)
at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadObjectWithMapTyped(BinaryHeaderEnum binaryHeaderEnum)
at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run()
at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
at System.Runtime.Remoting.Channels.CoreChannel.DeserializeBinaryResponseMessage(Stream inputStream, IMethodCallMessage reqMsg, Boolean bStrictBinding)
at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at nCrunch.TestExecution.Frameworks.IFrameworkDescriptionResolver.GetDescriptionForEachFramework()
at nCrunch.Core.TestManagement.TestFrameworkDescriptionManager.EnsureDescriptionsAreLoaded()
at nCrunch.Core.ComponentLoader.SnapshotComponentFactory.CreateSnapshotComponentFromXml(String projectFilePath, String projectXml, String solutionFilePath, String[] additionalFilesToIncludeAtSolutionLevel, Boolean isLoadedFromFile)


It works fine on VS2012.

Solved the problem.

There was a duplicated folder on NCrunch for Visual Studio 2013\Xunit with the xunit binaries, probably my fault, that the installed did not clean up.

Just upgraded from VS 2012 to VS 2013 and installed NCrunch 1.48.0.5 for VS 2013 and I've got the same problem.
Deleting either the XUnit/Latest or the XUnit/v1.6.1 directories does not solve the problem.

The exception comes when NCrunch tries to compile a project in the details view of the project.
NCrunch fails to build for all projects with the same exception.

Update: The tests are using NUnit instead of XUnit.

Hi, thanks for sharing this issue.

Can you try uninstalling the product and reinstalling it manually? This is usually a symptom of a corrupt installation. You can download the ZIP from here and the manual installation instructions are here.

I recommend you avoid deleting any of the installed files (including the Xunit directories) as they'll be needed by NCrunch when it loads the test framework descriptions.


Cheers,

Remco

Hi,

thanks for the fast reply.
The call to devenv.exe with the two setup parameters fails with "The operation could not be completed".

Still I've got NCrunch in my Visual Studio, when I run it, but it has the same problem.
I guess that during setup the call to devenv.exe will be issued too and silently fails?

Since I have no "unblock"-option in the properties of the extracted files, I guess they are not blocked.
I also tried removing the readonly-flag on the entire directory...

Regards,
Markus

Hi Markus -

Make sure that the files you've installed don't have any security restrictions that would prevent Visual Studio from reading them.

The 'devenv.exe /setup' call is used by all packages to load themselves into Visual Studio. If this call doesn't work, it's possible that there is another package causing problems or some kind of underlying issue with your VS configuration. Make sure that you perform this call as an administrator - the easiest way is to open up a command prompt as administrator, browse to your VS directory, then try running it from there.