May 6, 2009
  7877
(0 votes)

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

 

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.

May 06, 2009

Comments

Sep 21, 2010 10:32 AM

Solving The Issue :Failed to load some types from "EPiServer.Blog_Accessor”
Oru blog vachu erikunnuuu.... poyi padichu pani edukadaaaaaaaa
/ Nishar

Please login to comment.
Latest blogs
Optimizely CMS 13: Why Search & Navigation Now Means Graph Migration

Optimizely CMS 13 makes Graph a required part of the platform. Here is what that means in practice for teams moving from Search & Navigation, with ...

Wojciech Seweryn | Apr 8, 2026 |

Jhoose Security Module V3.0.0 – Site-Level Security Configuration for Optimizely

Jhoose Security Module updated for Optimizely CMS 13, introducing separate packages for CMS 12 and 13 with ongoing support and enhancements.

Andrew Markham | Apr 6, 2026 |

Searchable settings page

In my current project which has been actively developed for quite some time we have a big classic settings page. Unfortunately the placement and...

Per Nergård (MVP) | Apr 6, 2026

Using Azure Devops Pipelines in Optimizely SAAS (Configured) Commerce

Introduction When working with SAAS Commerce build service v2 your currently need to use a github repo with configured branches to start deployment...

Mark Hall | Apr 4, 2026 |