XamlParseException when using the XAML Designer - xaml

Important: Consider every tag in the .xaml codes below closed
I've searched everywhere for the answer but none of the questions in this website (or the MSDN website) solved it. Everytime I create a new Windows Phone 8.1 project I get the XamlParseException, even when I choose the Blank App project. I will list everything I tried.
Reinstall VS 2015
Reinstall VS 2015 without the SDK and then download it later with the emulators
Enable Developer Mode on Windows
Disable Project Code
Open the .xaml files with the Automatic Editor Selector and XAML Designer
Enable XAML Designer in the Options, of course
Update Windows 10 (note: I couldn't upgrade to 1809, I'm stuck with 1803)
Enable Hypervisor on the BIOS
Reboot computer
Adding the 'ThemeResources.xaml' manually on the project
Build, Rebuild and Clean the solution
Using different .NET Framework versions
Here is my App.xaml code:
<Application
x:Class="App2.App"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:local="using:App2">
Here is my MainPage.xaml code:
<Page
x:Class="App2.MainPage"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:local="using:App2"
xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
mc:Ignorable="d"
Background="{ThemeResource ApplicationPageBackgroundThemeBrush}">
<Grid>
</Grid>

I got it to work just by updating to Windows 10 1089, don't forget to enable Developer Mode once you upgrade, since "Sideload Apps" isn't enough.

Related

No XAML Hot Reload for WinUI projects in either VS2019 or VS2022

I've tried with both Visual Studio 2019 (16.11.5) and Visual Studio 2022 (17.0.0 P5), but am unable to get XAML Hot Reload working for WinUI projects (both UWP and Desktop types).
WPF project's are unaffected and XAML Hot Reload continues to work.
Can anyone offer any suggestions?
I'm running Windows 10 20H2 and have the extension Windows App SDK (Experimental) 1.0.0.50489432 installed, with Hot Reload enabled across all frameworks:

Xamarin XAML Intellisense not working VS 2015

I have tried to get intellisense working but no success.
Visual studio community edition 2015 update 2
Xamarin 4.0.4.4
Xamarin.Forms 2.2.0.45
Enable XAML Language for Xamarin.Forms 1.1
No Resharper installed
I have tried suggestions on previous threads. No success.
Any suggestions? Many thanks
Try build project containing xaml file. The InteliSense should then work.
For writing Xaml you can also install any Extension: In menu Tools/Extensions and updates... click on-line node and type xaml xamarin to the Search input.

MainPage.xaml from Windows phone 8.0 app

I can't find MainPage.xaml from Windows phone 8.0 app.
I have only App.xaml. I'm using Visual Studio 2013 Ultimate.
Is it code generated from Visual Studio?
Since this project wasn't original yours. I will assume that the owner set the default page to another .XAML file. Check the app manifest setting to make sure. See screenshot.
WMAppManifest.xml
As you can see my default page is set to a PanormaPage1.xaml

Weird behavior of Visual Studio 2013 RC3 XAML Designer

I'm having lots of problems with the Visual Studio designer, for a couple of days in a Windows 8.1 .net 4.5.1 project. I did not change anything in my source code. A heavy XAML loaded page doesn't load but neither for simplest empty page; This is the XAML for the simple page:
<Page
x:Class="MyTrip.BlankPage2"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:local="using:MyTrip"
xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
mc:Ignorable="d">
<Grid Background="{ThemeResource ApplicationPageBackgroundThemeBrush}">
</Grid>
Since I have been working with visual studio I had similar projects, and I debugged the XDescProc.exe in order to guess what was happening. Nothing worked on this one, this error is shown:
An exception happened as always with the designer. This exception isn't related to my code, and I will show you why; I'm developing also a Windows Phone 8.1 app, and since I have an Universal Project I made a test. I droped the XAML related to the view (the heavy page) giving me that exception to the Universal Project. I double-clicked and... It works both for the heavy page and the simple page.
So in the Windows 8.1 project breaks, and in the universal project works... Why? Since the universal project is just a reference in Windows 8.1 project, what would make the designer break under the Windows project? Any help on this? I have to make the designer work on WIndows 8.1 project.
You can try clearing the contents of the following folders under your Windows user profile:
AppData\Local\Microsoft\VisualStudio\12.0\Designer\ShadowCache
AppData\Local\Microsoft\VisualStudio\12.0\Blend\ShadowCache
You do need to have all instances of Visual Studio 2013 and Blend for Visual Studio 2013 closed before deleting the contents of those two folders.

Change to Xaml code not reflected in Design View in Visual Studio 2012 on Windows 8 PC

I am taking an online tutorial (Lynda.com, "Creating a Windows Store App with Visual Studio 2012").
The tutorial shows that changing the XAML code from this:
<Grid Background="{StaticResource ApplicationPageBackgroundThemeBrush}">
To this:
<Grid Background="Orange">
Changes the background to orange in the IDE. This makes sense. It's easy. It works in the tutorial, but not for me. When I run the program (a hello world program without the hello world), the screen color is the default of blue. Other changes in the XAML code don't find there way into the design view or the runtime view. Weird. Something is wrong somewhere. What could be wrong?
Microsoft's tecnnical support solved this problem for me with an assist from the Dell Computer Corporation.
The problem was caused because an older version of a device driver for an Intel(R) HD graphics card was on my PC. Acquiring and installing the latest version of the device driver solved the problem.