CODEWITHSUNDEEP
wpf
Garth Marenghi
Garth Marenghi

Reputation: 2047

Undefined CLR namespace

I have the following:

Error! Error!

The error says The 'clr-namespace' URI refers to a namespace '{0}' that is not included in the assembly.

I've build and rebuild but nothing happens. I'm sure this must work, because a WPF demo app that I downloaded has everything the same. What's going on?

Upvotes: 16

Views: 23993

Answers (10)

user711227
user711227

Reputation: 13

I had the same problem today after I had to rename class (and file with it) in the namespace. So I was able to solve it by deleting .sln file, then run .csproj and recreate .sln file.

Upvotes: 0

Daniel
Daniel

Reputation: 8398

I had the same problem and solved it by not having my project in a path with hash-mark.

E.g D:#Temp had to be D:\Temp

I guess there's someone at Microsoft having missed an EscapedCodeBase in conjunction with the URI.

Upvotes: 3

Falk Seifert
Falk Seifert

Reputation: 19

Also verify the "BuildAction" of the .xaml files (see file properties). Should be "Page". After I moved files and renamed the namespace this setting changed somehow to "CodeAnalysisDictionary". This also leeds to this error.

Upvotes: 2

Dave
Dave

Reputation: 8471

I've had the same issue, mine was self inflicted due to copying and pasting code from another source into my project and renaming objects as I went without building first.

So, this means Visual Studio or the compiler do not pick up on incorrect references (eg, in my code I had this:

MyObect mo = new MyObect();

When I copied the code over, I corrected the spelling of MyObect to MyObject but, Visual Studio has still referencing MyObect and didn't give any warnings about this. And this was code was part of a .XAML file and as such, I was not only getting the error message you were, but also .g.cs errors too. All of them pointing to the incorrect reasons.

This was also occuring in the ResourceDictionary (within my datatemplate declarations for all my VM binding)

Upvotes: 0

Cloud9999Strife
Cloud9999Strife

Reputation: 3202

I had the same error message given to me. But the underlying problem was different. I moved my MainWindow.xaml to a different folder, and I forgot to update my App.xaml StartupUri. I then updated my StartupUri in my App.xaml and the problem was fixed.

Upvotes: 2

Eric C
Eric C

Reputation: 11

I got this after Windows 7 computer crash when I was in solution in Visual Studio 2008. It seems to have blanked out the start-up configuration. I reset this and then it could find the name-space. This is one cause - probably not the major one - but just in case you have same.

Upvotes: 1

Maciej Rogoziński
Maciej Rogoziński

Reputation: 677

I had similar problem when project's solution platform was set to x64. When I changed it to x86 problem went away.

Here is some explanation: http://social.msdn.microsoft.com/Forums/en-US/wpf/thread/6379d330-f382-4b4d-a690-e89326ab4c72

Upvotes: 9

Willem van Rumpt
Willem van Rumpt

Reputation: 6570

Assuming your ViewModel folder isn't empty (or there actually is a type with BlooblieBlablie.ViewModel as its namespace), and BlooblieBlablie is the assembly name, the following should work:

xmlns:vm="clr-namespace:BlooblieBlablie.ViewModel;assembly=BlooblieBlablie"

Upvotes: 26

Heinzi
Heinzi

Reputation: 172478

Judging from your screenshot, your ViewModel folder seems to be empty. If there are no classes in the namespace BlooblieBlablie.ViewModel, the namespace does not exist yet.

Upvotes: 1

Daniel Hilgarth
Daniel Hilgarth

Reputation: 174457

Well, as far as I can see, that namespace simply doesn't exist ;-) In your ViewModel folder is no file. And without file, there is no namespace. Namespaces are not defined by folder structure but inside source files.

Upvotes: 1

Related Questions