Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 911259
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 15, 20262026-05-15T17:10:31+00:00 2026-05-15T17:10:31+00:00

I’ve been working on a WPF application. Since I design the UI in Expression

  • 0

I’ve been working on a WPF application. Since I design the UI in Expression Blend 4 and work on the code-behind part in Visual Studio 2010, I constantly switch from one tool to another.

I added some Image controls to an existing Grid and assigned some images to them. In Blend, I built the project and ran it. Worked just fine. When I switched to Visual Studio, I am getting this error:

Undefined CLR namespace. The
‘clr-namespace’ URI refers to a
namespace ‘MS.Internal.Media’ that is
not included in the
assembly. C:\Users\Dennis\Documents\Visual
Studio
2010\Projects\solutionName\projectName\MainWindow.xaml

The designer cannot be loaded with this error pending. However, the project is working in Blend and I can see it just fine there.

The declarations are the following (in the Window):

<Window
        xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
        xmlns:d="http://schemas.microsoft.com/expression/blend/2008" xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:MS_Internal_Media="clr-namespace:MS.Internal.Media;assembly=PresentationCore" mc:Ignorable="d" x:Class="projectName.MainWindow"
        Height="272" Width="359" Loaded="Window_Loaded" WindowStyle="ThreeDBorderWindow" ResizeMode="NoResize" Icon="/projectName;component/Images/main.ico"
        Title="Sample Project">

What could be causing this error?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-15T17:10:32+00:00Added an answer on May 15, 2026 at 5:10 pm

    It seems that this is a known issue (perhaps bug is too strong a word, if it is a setting or something that I am missing too then happy to stand corrected on this one, anyway….) in Visual Studio – its still happening in VS2010 too.

    If you remove the string “clr-namespace:” in the XAML, just leaving you with

    xmlns:MS_Internal_Media="MS.Internal.Media;assembly=PresentationCore"
    

    it will compile fine and you can reload the designer. If you then added the clr-namespace syntax in again it will build ok but the designer will still error. I believe this must be an issue in Visual Studio itself.

    Hope this workaround at least helps you to load the designer and get the project built.

    Having played around with this a little more I think the problem is probably the fact that that assembly has no public types. Looking at the assembly in .Net Reflector they are all internal classes. The same error that you are getting in VS is thrown for all assemblies where thare are no public types. I expect that Blends interface is either not checking for this or is handling it better.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Ask A Question

Stats

  • Questions 450k
  • Answers 450k
  • Best Answers 0
  • User 1
  • Popular
  • Answers
  • Editorial Team

    How to approach applying for a job at a company ...

    • 7 Answers
  • Editorial Team

    How to handle personal stress caused by utterly incompetent and ...

    • 5 Answers
  • Editorial Team

    What is a programmer’s life like?

    • 5 Answers
  • Editorial Team
    Editorial Team added an answer I did more reading in Android Docs -- I could… May 15, 2026 at 8:38 pm
  • Editorial Team
    Editorial Team added an answer The reason for this in your case is that the… May 15, 2026 at 8:38 pm
  • Editorial Team
    Editorial Team added an answer I had a problem like this a while back. Anyway,… May 15, 2026 at 8:38 pm

Trending Tags

analytics british company computer developers django employee employer english facebook french google interview javascript language life php programmer programs salary

Top Members

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.