Visual Studio 2012 Not Recognizing Xaml Files, Design View Broken

4
votes

Design View for Xaml on Visual Studio Professional RC 2012 used to work for me. But suddenly stopped for no reason I can figure.

  • Visual Studio 11 No longer Recognizes Xaml Files.
  • In properties, it treats XAML files like XML.
  • In solution Explorer it recognizes it as a xaml file
  • Right Click -> Design View opens a new Xaml code page
  • Controls Toolbox shows nothing
  • My OS is Windows 7 x64.
  • I have applied all updates up to July 2012 to VS11
  • I have tried Repairing Visual Studio & Resetting Settings but to no avail.
  • There is nothing in search or stackoverflow I could find to remedy this.
  • I have not tried un/reinstalling

Visual Studio 2012 RC designer does not recognize xaml for a Windows Metro app looks identical to my case but my problem suggests the issue is more general than his title.

Reinstalling fixed his issue but does not shed light on this frustrating problem.

Can someone help?

EDIT - Reinstalling nearly resolved the issue. Design view works, toolbox is populated, auto complete is back, XAML is available under tool-> options->text... and control element properties can be viewed.

Everything is normal except for the passing strange fact that XAML Code View no longer does syntax highlighting. This is not suprising since unlike what http://msdn.microsoft.com/en-us/library/bb907395(v=vs.90).aspx expects, there are no XAML prefixed items in the displayed items.

Perhaps relatively minor in the scheme of things but also a very annoying loss.

5
visual-studioxamlvisual-studio-2012xaml-designer
You say that reinstalling resolved the issue. Do you still have a machine in the broken state, or can you repro the broken state? – James McNellis
The person linked above stated re-installing fixed things. I am only now trying that since I can't think of anything else. Will edit in the result. I don't know how to reproduce it since I can't say for certain when this was triggered. – cranesbane
We've seen the "no syntax highlighting" issue before but have not been able to repro it. If you're willing to help us debug the issue, would you drop me an e-mail at [email protected]? I'd like to get some information about your configuration to see if we can figure out why this happens. Thanks! – James McNellis
/resetuserdata fixed it for me. I don't know how I can help since I can't even say when this started. My config was only office tools installed extra, F# profile default, and registry tweak to change all caps issue. One strange thing is after fix, it's now using vs 2012 instead of VS11 for project folders. Perhaps a latent bug in settings carried over from beta. Still doesn't answer why so long to show up though. – cranesbane

5 Answers

6
votes

Suggestion 4 in this link worked for me: devenv /resetuserdata in Command Prompt.

So at least in my case, re-installing and then the above command cleared all issues. It is possible that resetting user data could have made it unnecessary to re-install but I can't know that now.

I still can't say what caused this but it seems a pretty long tail issue that occurs sporadically and looks to have precursors in older versions.

3
votes

Check the following:

  1. Tools -> Options
  2. Expand Text Editor -> XAML -> Miscellaneous
  3. Make sure that "Always open documents in full XAML view" is not checked

Or perhaps the default program for opening .xaml files has changed:

  1. Right-click your .xaml file in Solution Explorer
  2. Click Open With...
  3. Select XAML UI Designer
  4. Click Set as Default button
  5. Click OK

EDIT

This does appear to be a known bug with an earlier version of VS11.

0
votes

If anybody is interested. I had the failure: Could not open XAML and config files in Visual Studio 2012. Now I detected the cause: the Solutions suo files were corrupted after a System Crash. So I (was not sure) rebuilt the sln file in a different Folder and copied the sln and suo files (they are hidden!) to the old Folder. That definitely brought me back the lost functionality. Maybe it is only necessary to delete the old suo files. Juergen

0
votes

I had the same issue in Vs 2012 express edition. Solved by running vs2012 command prompt and executing the code

WDExpress/ResetSettings

0
votes

In Visual Studio 2013 I had a similar issue - I change my build action & from BundleResource to AndroidResource and I was able to get it working.

enter image description here