XAML parser doesnot see connected namespaces - by Black_Joker

Status : 


Sign in
to vote
ID 790305 Comments
Status Active Workarounds
Type Bug Repros 0
Opened 6/17/2013 3:48:39 AM
Access Restriction Public


XAML parser doesnot see connected namespaces and WPF designer does not work because of that.
Sign in to post a comment.
Posted by Microsoft on 7/8/2013 at 10:34 AM
Please feel free to reactivate this issue when you have the required information.
Harikrishna Menon
Program Manager
Posted by Microsoft on 7/2/2013 at 8:07 AM
Can you please give us explicit repro steps on how to reproduce the problem. All the pages load fine and I cannot see any errors on any of the page. Also we just released Visual Studio 2013 Preview. Can you please check if this is fixed there.
Harikrishna Menon
Program Manager
Posted by Black_Joker on 6/29/2013 at 4:30 AM

I am using VS 2012 update 3 RC2. The problem here is not in squiggles. WPF XAML parser think that there are incorrect namespaces present in page/window (I am talking about me own namespaces) if the same project open in release and debug mode. Everything is compiling correctly without errors, but WPF designer doesnot work because xaml parser think that there are some errors with incorrect namespaces. THis is not so critical, but very annoying issue especially if project is big and page or window has a lot of xaml code.

Could you please investigate described issue?
Posted by Microsoft on 6/28/2013 at 8:31 AM
    Thanks for reporting this issue. On VS 2012 Update 2 I can see that all the views are being correctly parsed in Visual Studio. The only issue I have seen is that Resources in App.xaml are not being parsed correctly (squiggles in the editor). Can you please confirm if this is the issue you are seeing and would like us to investigate?.
Posted by Microsoft on 6/21/2013 at 12:46 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Black_Joker on 6/20/2013 at 2:55 AM
I found more concrete use case:
On one PC project is in release mode, on another - in debug, so if change to release, Designer starting correctly.
But in any case parser should correctly process namespaces.
Posted by Black_Joker on 6/17/2013 at 11:24 PM
The whole project attached to the ticket.
Posted by Microsoft on 6/17/2013 at 10:36 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please give us a demo project to demonstrate this issue so that we can conduct further research?

Please submit this information to us within 4 business days. We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 6/17/2013 at 3:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)