XAML Designer can not find any files in my local namespace!

Question

1.00/5 (1 vote)

See more:

I know this question has been asked multiple times, and I've gone through them all. Hopefully I didn't just miss something in the previous answers, but I'm stumped.

My application was working fine yesterday, but today I booted it up and now none of my file references, including ViewModels or DependencyProperties which I have defined in external files, can be found. I'm coding in VB (as you'll see), I've tried changing / adding Namespaces and nothing!

If someone has some insight into this issue I'm all ears!

Solution Structure

Image Of Solution

XAML Code

XML

<Window
xmlns:l="clr-namespace:PrairieWestIceCreamWPF"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"    
x:Class="WeeklyOutlookView" Title="WeeklyOutlookView" Name="WeeklyOutlookView"    Height="463.5" Width="1280" l:WindowBehavior.WindowClosing="{Binding WindowClosingCommand}">


<Window.DataContext>
    <l:WeeklyOutlookViewModel />
</Window.DataContext>

Errors

The Name "WindowBehavior" does not exist in the namespace "clr-namespace:PrairieWestIceCreamWPF"

The Name "WeeklyOutlookViewModel" does not exist in the namespace "clr-namespace:PrairieWestIceCreamWPF"

Posted 19-Mar-14 6:25am

Justin Shepertycki

Updated 19-Mar-14 6:31am

v5

Add a Solution

2 solutions

Solution 2

Please see my comment to your "Solution 1". This is not a solution at all. Actually, referencing the types defined in the same project is not a problem at all. It is not easy, it is very easy.

To start, start adding the xmlns attribute to your top XAML element by typing "xmlns:". The intellisense will show you the variants of local namespaces you can reference. Choose an appropriate one; and you will be done. Sorry if Intellisense is not working on some settings. I never faced this bug and can assure you that it is generally working. What you can do? Find out a single case of valid syntax for namespace value and learn it, enter manually.

—SA

Posted 19-Mar-14 6:57am

Sergey Alexandrovich Kryukov

Updated 19-Mar-14 7:00am

v2

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

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

Justin Shepertycki · Accepted Answer · 2014-03-19T06:51:00

Solution 1

Finally found the culprit!!

At my work, our desktops are hosted on a network share. I had brought two applications I was working on from home and dropped the application files temporarily on the desktop to make some quick minor changes. Turns out there is a bug in the WPF Designer where the application will not be able to resolve assembly references if the application is being run from a share. As soon as I moved it to my local D drive, everything work perfectly.

Found answer here ->
http://social.msdn.microsoft.com/Forums/vstudio/en-US/75c4cc8d-9a81-4bda-84f0-f619f7493b3b/vs2010-xaml-namespace-intellisense-not-working?forum=vswpfdesigner

Posted 19-Mar-14 6:51am

Justin Shepertycki

Comments

Sergey Alexandrovich Kryukov 19-Mar-14 12:55pm

Moving to your local D drive? Gibberish. And what if you did not have this drive? And you totally broke the integrity of your project; move it onto another computer and it won't compile. All file references should be relative.

Forget about this solution, you did not find it. Your original XAML code is just ridiculous. You did not even try to add a proper namespace to bind with your project types. If you do nothing, you will have nothing.

—SA

Justin Shepertycki 20-Mar-14 13:47pm

You have some anger issues. Look, I'm very new to WPF. I hope to god you're not some sort of instructor cause with that attitude you'd have to pay me to be in that class. I ended up getting a personal response from the MSDN guys and he said that my XAML was correct, and that opening a project on a LAN Share has been an issue in the WPF designer for a long time now. So before you start on another one of your temper tantrums, try some constructive criticism, not an all out verbal beating.

Sergey Alexandrovich Kryukov 20-Mar-14 14:09pm

Be it your way. After all, you have this problem, not me. No one forces you to get a solution. Probably you don't want to accept any help (did you even notice I suggested some answer, good or bad?) just because you don't like criticism. So, how is going to loose then?
--SA

Justin Shepertycki 20-Mar-14 14:16pm

I enjoy constructive criticism. It's the best way to learn in my opinion. Maybe it's a language barrier thing, and if it is I apologize. Clearly I was willing to accept help considering I got help from the MSDN team, so your comment on that is moot. And you may have offered a valid solution, but you present your solutions like a jerk, as if you think your better than everyone else. Which in the end, has clearly caused more problems than they have solved. I appreciate your knowledge, that does not mean I appreciate you. Good day.

Sergey Alexandrovich Kryukov 20-Mar-14 14:27pm

My criticism is constructive, you just failed to notice it. If it happened because I did not express myself clearly, I apologize.

Now, a big note: I readily accept even non-constructive criticism, and would advise you to do the same. Non-constructive criticism can be very useful, too. To give you an example: supposed I found some solution and proven that it is correct, but my proof was wrong due to some mistake. Suppose you found my mistake, point it out, and told me "I don't know the solution, by yours is wrong, by this and this reason". You disprove the solution and did not put forward any. Should we all be thankful for that. Of course! You prevented wrong solution and found the mistake.

Can you see my point?

Cheers,
--SA

Justin Shepertycki 20-Mar-14 14:37pm

I do see and 100% agree with your point. Honestly it truly was the way that it was expressed. I'm widely open to others disproving any solution I may present. I'd much rather someone tell me I'm wrong with good reason, then let it slide and I continue to repeat my mistakes. As long as it is disproved in a respectful and professional manner, I will offer the same respect and gratitude in return. I say we mark this disagreement as a misunderstanding of each other, and maybe we can both take something away from this discussion.

Sergey Alexandrovich Kryukov 20-Mar-14 15:46pm

Great. Okay, do you understand the flaw in using having the solution which fixes by moving to D:? The solution is supossed to be portable to any location, any suitable computer, and should be in one piece. (Actually, it is of course possible that I did not get your point...) Did you see my answer? Does the Intellisense work for you in any of the settings? You see, when Intellisense failed, it does not mean anything important; the solution itself can be valid. But Intellisense can be used to just find out this "clr-namespace:*" syntax, or whatvever. So, you you have the solution right now, something which can work at any location? Or do you still have a problem?
—SA

Justin Shepertycki 20-Mar-14 16:33pm

The reason why moving the solution to the local D Drive worked was because when I put the application folder on my desktop, I had forgotten that our desktop is stored on our network share so our environment is consistent; no matter which computer we use to log in within our network. Because it was not on my local machine and actually on the server, the WPF designer could not resolve the dependency. That is the error that Microsoft is aware of apparently, and they have been aware of it for some time now, the just haven't patched it yet. That is what I was told by the MSDN representative.

Everything in the solution is relative. It is portable to any location. I could have put it on a USB drive and it would have worked just fine. I was just unaware of the issue involving LAN Shares and WPF Solutions.

Sergey Alexandrovich Kryukov 20-Mar-14 16:40pm

Using desktop is a bad idea, but, technically, desktop is still a folder, so the solution should work. You did not explain this problem is your post. So, as I understand, now you can put your solution in any "real" directory, and it will compile and work, is that right? Then, everything is all right...

Sorry for some misunderstanding, but you have to admit that, before this explanation, your post was just misleading...

—SA

Justin Shepertycki 20-Mar-14 16:44pm

You're right, my question was too vague. I did mention that the application was trying to run from a Share in my solution, but again I could have been more clear. Appreciate your input!

Sergey Alexandrovich Kryukov 20-Mar-14 16:49pm

Good luck, call again.
—SA