Solving The Issue :Failed to load some types from "EPiServer.Blog_Accessor”

Wed, 06 May 2009 09:12:57 GMT

This post is to solve an issue in the integration of EPiServer CMS5 R2 SP1 And Visual Studio .When you create a new EPiServer project in Visual Studio 2008 and you don’t have VS Team Test installed on your machine ,you might get an error message like this as and when you run the application :-

“

Message:-

Failed to load some types from "EPiServer.Blog_Accessor": Could not load file or assembly 'Microsoft.VisualStudio.QualityTools.UnitTestFramework, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: EPiServer.PlugIn.PlugInException: Failed to load some types from "EPiServer.Blog_Accessor": Could not load file or assembly 'Microsoft.VisualStudio.QualityTools.UnitTestFramework, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

”

This one had me baffled for a while.Thanks to Mr.Allan Thræn for getting this problem solved. It is actually a problem in the EPiServer CMS5 R2 SP1 And Visual Studio Integration, where an internal test dll (EPiServer.Blog_Accessor.dll) by accident has been included. That dll requires VS Team Test and if you don't have that installed you'll see the error above.

Solution:- The solution is easy, just delete the EPiServer.Blog_Accessor from your bin folder / remove it from your project.

Blog posts by Suneesh Writes

Solving The Issue :Failed to load some types from "EPiServer.Blog_Accessor”