I have just downloaded the 14 CTP version of Visual Studio and created a blank app for Windows Phone. I tried to open the MainPage.xaml
and the designer shows u
It does not work for me. Just created new local account with Administrator type (Window 8.1, VS 2013 update 4). Login by the new local account. Open and see it is solved.
Check your x:class property in your page
Ensure the class name on your XAML matches the class name in your code-behind. I've run into this a few times while refactoring.
XAML Opening Tag:
<UserControl
x:Class="Namespace.Foo"
... />
Code Behind:
public sealed partial class Bar : UserControl
{
public Bar()
{
// This will become the error specified (does not contain definition)
this.InitializeComponent();
}
...
}
So Namespace.Foo would need to be Namespace.Bar here to get rid of the error. This should have the same behavior if using Page
instead of UserControl
.
the same started to happen to me today; to reproduce the issue, I just open Visual Studio 2013 Update 4, create a blank Windows Phone 8.1 and double click on MainPage.xaml.
I solved by performing the following (a mix of what I've read around the web):
open a command prompt with admin rights and execute the following commands:
pushd %VS110COMNTOOLS%
icacls ..\IDE /grant *S-1-15-2-1:(OI)(F)
icacls ..\IDE /grant *S-1-15-2-1:(CI)(F)
icacls ..\IDE\PrivateAssemblies /grant *S-1-15-2-1:(OI)(F)
icacls ..\IDE\PrivateAssemblies /grant *S-1-15-2-1:(CI)(F)
icacls ..\IDE\PublicAssemblies /grant *S-1-15-2-1:(OI)(F)
icacls ..\IDE\PublicAssemblies /grant *S-1-15-2-1:(CI)(F)
finally, reboot. worked on Windows 8.1 64-bit.
Ran into same problem today, Fixed it by killing all instances and opening it up again.