Click here to Skip to main content
15,897,518 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
how to deal with this problem.
Error 1 Could not load type 'Microsoft.Expression.DesignModel.Core.ISharedInstanceBuilder' from assembly 'Microsoft.Expression.DesignModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. F:\C#程序\WpfApplication2\WpfApplication2\MainWindow.xaml 1

the Design of Wpf cannot use
Posted
Comments
[no name] 4-Oct-12 11:20am    
http://social.msdn.microsoft.com/Forums/en-US/vswpfdesigner/thread/2c1f3fcb-bb42-48ba-a18a-108686bc04df
Kenneth Haugland 4-Oct-12 11:20am    
looks like a missing Blend dll?

1 solution

Could not load type 'Microsoft.Expression.DesignModel.Core.ISharedInstanceBuilder' from assembly 'Microsoft.Expression.DesignModel, Version=4.0.0.0
Refer: VS 2010 XAML Design View Load always fail with a Type Load Exception[^]

It says:
Looking at this error, we suspect a bad copy of this assembly somehow got into the GAC and is supplanting Visual Studio's version of the Microsoft.Expression.DesignModel assembly (the Visual Studio designer uses portions of Blend). You can prove this by attaching a debugger or using file monitor to check the path this assembly is being loaded from. It should be loaded from %programfiles%\microsoft visual studio 10.0\common7\ide\privateassemblies.

The copy of the assembly in PrivateAssemblies has the required interface and is required to make the Visual Studio designer work.

To remedy:

1. Quit all copies of Visual Studio, then fire up an elevated Visual Studio command prompt (you should see "Visual Studio Command Prompt (2010)" under the Visual Studio folder on your start menu - right click and run it as administrator assuming you're on a Windows 7 or Windows Vista PC.

2. In the command prompt you just started, run “gacutil /l Microsoft.Expression.DesignModel” to see if the assembly is in the GAC

3. If it is, then run “gacutil /u Microsoft.Expression.DesignModel” to remove it from the GAC - it should NOT be there.

4. Now try running Visual Studio again and try the action that showed the problem - it should be OK now.
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900