C#/XAML Compile Error – Various Errors (The name “LayoutAwarePage” does not exist”)
Not a good night. After all my progress my Visual Studio 2012 Project for Accountable has bugged out and I get the following error:
Error 5 The name “LayoutAwarePage” does not exist in the namespace “using:Accountable.Common”. G:\Coding Projects\Visual Studio 2012\SAVED\Accountable\Accountable\BasicPage1.xaml 1 1 Accountable
Weird, as all I have been doing is adding new XAML Views to the project, them bamn, Visual Studio has bugged out. So I furiously last night tried the following:
- Had a look on StackOverFlow and found post which didn’t help at all. I then logged my own here ONLY after trying the following triage on my Project:
- Deleted the SUO (Hidden) file from the Solutions folder. No luck.
- Removed my XAML Files, Classes (Models and ViewModels) and deleted the Common Classes and created a new XAML Basic Page. This causes the Project to reload the Common Classes (including LayoutAwarePage.cs). Rebuilt the Solution, no luck.
- Removed the reference Syncfusion Controls for WinRT XAML which I use for Custom DatePickers. Still the same issue.
- Repaired the Visual Studio 2012 installation using Control Panel->Program Features->Visual Studio 2012->Change. Again, nothing happened.
The (very helpful) guys over on Stack couldn’t resolve the issue as well, plus I created a new Project and this works, so i logged a call on Microsoft Connect here:
As you can see, not very helpful! So I’m now left with no option but to create the Project again, and add it bit-by-bit up from existing code. Hopefully the issue doesnt replicate BUT if it does, I might be able to isolate and provide more detail. For the time being I will keep the SO question open. If anyone else gets this issue, comment here or post on the SO question.
Related articles
Leave a Reply
My Visual Studio Achivements
- An error has occurred; the feed is probably down. Try again later.
Kellabyte
- AMQP and wire format interopability May 23, 2013
- Convergent Replicated Data Types May 20, 2013
- Configuration is bad but what about operational flexibility? May 10, 2013
- An alternative to Paxos, the RAFT consensus algorithm May 9, 2013
- Version tolerance and accidental operation complexity May 6, 2013
Martin Elsworth
- SQL – string inside a string April 20, 2012 MartFish
- Crystal Reports – Conditionally supress a Line object March 30, 2012 MartFish
- Databind an Enum to a Combobox February 21, 2012 MartFish
- Compact Framework build and deployment time. January 27, 2012 MartFish
- BindingContext – List controls that share a datasource November 8, 2011 MartFish
Shawson
- Powershell to write bunch of data from sql to the file system April 30, 2013 shawson
- Executing long running process from a web site February 10, 2013 shawson
- My 8 Week Game Entry! February 6, 2013 shawson
- How to fix CD / DVD Drive not showing up in Windows 8 January 7, 2013 shawson
- Threading in JavaScript with Web Workers January 5, 2013 shawson
Flexicoder
- Freelancing – Work Sources January 9, 2013 flexicoder
- Contract or Freelance – PROS/CONS January 2, 2013 flexicoder
- WWDC 2012 Songs June 16, 2012 flexicoder
- WWDC 2012 – Post Mortem June 16, 2012 flexicoder
- WWDC2012 – How Did My Predictions Score June 16, 2012 flexicoder
Is definitely a bug in VS/Blend. I have the same error, but i can compile and run the App without Problems. I hope MS will fix it soon.
I believe I have the same issue. I made very minor additions to my code (just added a class and a few subs) then suddenly was unable to compile and got over 100 errors that all seemed to stem from the project ‘forgetting’ the LayoutAwarePage. I too tried the same troubleshooting you did. I haven’t tried a VS repair yet, but I’m not confident.
I of course removed the changes I had made since the project last successfully worked and I double checked all my namespaces, etc. even though no changes were made to them.
I was expecting to put the finishing touches on my app today and publish it!
I might have to do a file-by-file recreation of my project. Sounds like fun.
The Visual Studio repair didn’t work for me at all. What I found was by removing a Visual Studio update, the issue has resolved itself. I’m in the process of rebuilding file by bloody file!! Good times……..:’(