Why is generated XAML spitting out namespaces that are not asked for?
Posted
by Matt Holmes
on Stack Overflow
See other posts from Stack Overflow
or by Matt Holmes
Published on 2010-04-06T16:51:13Z
Indexed on
2010/04/06
16:53 UTC
Read the original article
Hit count: 276
I have a very simple XAML form, that has one namespace definition. For some reason, when Visual Studio processes that XAML file in to it's component .g.cs, it's sticking a bunch of namespace definitions at the top that I have not asked for in the XAML, or the code behind, and they are namespaces that no longer exist in my project. Thus the project is failing to compile.
Why is Visual Studio sticking arbitrary namespace 'using' statements in my generated XAML .g.cs files? It's caused my entire project to break. Not one time did this .xaml file ever reference the namespaces in question, so it's doubly annoying.
© Stack Overflow or respective owner