WPF Designer no longer recognizes x:Type and x:Static - by Sudo John Smith

Status : 


Sign in
to vote
ID 758739 Comments
Status Active Workarounds
Type Bug Repros 12
Opened 8/20/2012 5:57:43 AM
Access Restriction Public


When creating WPF applications targeting .NET 3.5 in VS2012, the WPF designer considers the perfectly valid x:Type and x:Static blocks to be errors.  This also causes the Intellisense on Setter Properties to no longer function.

This item was marked as fixed, but we would like to know when to expect a fix for this issue.  Thanks.
Sign in to post a comment.
Posted by Harikrishna Menon on 8/26/2013 at 1:31 PM
Thanks for the feedback. I verified this on the latest internal builds of VS 2013 and this looks to be fixed. The fix should be available in the next public release of Visual Studio 2013. Can you please send me a small standalone repro to verify, would like to make sure that your repro is fixed. You can reach me at harikm@microsoft.com.
Harikrishna Menon
Program Manager
Posted by Fryburger on 8/24/2013 at 1:04 AM
It works in .Net 3.5 as well as in 4.5. But the problem still seem to REMAIN in .NET 4.0!
Posted by Sudo John Smith on 3/14/2013 at 7:13 AM
This was fixed, but they replaced it with another bug.

See this one: http://connect.microsoft.com/VisualStudio/feedback/details/778210/ambiguous-type-reference-with-x-type-x-static
Posted by kainhart on 2/15/2013 at 10:25 PM
Now that Update 2 CTP 3 has been released has anybody been able to run and verify that this issue has been fixed? This is a major issue for us who are still on .NET 3.5.
Posted by Sudo John Smith on 11/19/2012 at 8:35 AM
Thanks for the information. Feel free to reset the issue as resolved.
Posted by Microsoft on 11/13/2012 at 8:13 AM
Hi John,
         Thanks for reporting this issue. This has been fixed in the for the February(2013) update of Visual Studio 2012. The CTP should be available in late December.
Harikrishna Menon
Program Manager
Posted by zpittman on 11/9/2012 at 11:58 AM
I am seeing the same problem in Microsoft Visual Studio Premium 2012 Version 11.0.50727.1 RTMREL

We are targeting 3.5 framework (sp1 installed) and if the designer is open the build fails. Our workaround currently is to close any designer window and then build.

Why is this so?
Posted by Tolga Balci on 11/2/2012 at 7:03 AM
I just had the same exact issue with using x:Type. This bug is not Fixed, why is it closed as Fixed?
Posted by Sudo John Smith on 10/30/2012 at 8:45 AM
This doesn't appear to be resolved in Visual Studio 2012 Update 1 CTP 4. When will it be fixed?
Posted by Kaya3 on 9/24/2012 at 4:55 AM
I have the exact same issue. Thsi renders VS2012 not usable for me. I have lots of projects with this in and I need the designer. Back to 2010 then. What a waste of time and money.
Posted by Alexander Shakurin on 9/21/2012 at 6:16 AM
I have the same error when opening existing solution targeting .NET 3.5 in Visual Studio 2012.
Posted by Sudo John Smith on 9/19/2012 at 2:36 PM
It's been a month and no feedback has been returned. Has there been any progress?
Posted by Microsoft on 8/20/2012 at 11:07 PM
Thank you for submitting feedback on Visual Studio 11 and .NET Framework. Your issue has been routed to the appropriate VS development team for review. We will contact you if we require any additional information.
Posted by Microsoft on 8/20/2012 at 6:53 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)