Home Dashboard Directory Help

Usercontrol is not supported in Windows 8 app error message (XAML) by HJRP


 as Duplicate Help for as Duplicate

Sign in
to vote
Type: Bug
ID: 808159
Opened: 11/9/2013 5:33:28 AM
Access Restriction: Public
User(s) can reproduce this bug



i have windows store app that worked fine in vs 2012. now I try to use vs 2013 and get the error message:
"Usercontrol is not supported in Windows 8 app" in the xaml editor.
same for image, grid, style xaml tags.
the project compiles though without errors??
Please advice how to proceed.

Sign in to post a comment.
Posted by MS-Moderator09 on 12/27/2013 at 12:22 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. Upon review of this issue , we have identified it as a duplicate Connect bug. We have closed this bug as a duplicate, and added a vote to the original # <http://connect.microsoft.com/VisualStudio/feedback/details/812340/xaml-editor-not-displaying-intellisense-in-windows-store-c-project>. Please check the original feedback item for any updates or resolutions.
Posted by Hansjörg Reister on 11/12/2013 at 1:42 AM
i uninstalled VS 2012 and now the error is gone. There are definitely Problems installing two Versions of VS on one machine!

You can Close the call. I helped myself (again).

Posted by Microsoft on 11/12/2013 at 1:17 AM
Hello again. We wanted to give you a quick reminder that to efficiently investigate and reproduce your issue, we need you submit the additional information we requested.
Posted by Microsoft on 11/10/2013 at 11:10 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?

We look forward to hearing from you with this information.
Posted by Microsoft on 11/9/2013 at 5:51 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)
Sign in to post a workaround.