May 6, 2009
visibility 8035
star star star star star
(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

error Please login to comment.
Latest blogs
Composition Over Inheritance: Why Your Content Contract Is Not a Base Class

Inside the structural conformance pattern in SaaS CMS — from server-side inheritance to pipeline governance. A contract in Optimizely SaaS CMS is...

Vipin Banka | Sep 19, 2026

Optimizely Opti ID Integration: Why the API Key Was Missing from the DXP Management Portal

While working on an Optimizely CMS 12 Opti ID integration recently, we ran into an issue that initially appeared to be related to SSO authenticatio...

Madhu | Sep 18, 2026 |

Extending a Contract: What You Can Override

Contracts share fields across content types — but not every field setting can be overridden. Push the same contract onto several components, and CM...

Chirag Khanna | Sep 18, 2026 |

Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell

What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(),...

Stanisław Szołkowski | Sep 17, 2026 |