XAML Designer System.Runtime.Remoting.RemotingException

Question

• I\'m encountering the following System.Runtime.Remoting.RemotingException error when I create a blank Windows 10 Universal Application...

  Following are

Answer 1

Its been a few months but I have finally been able to get the XAML Designer to work. As @peterfaraday mentioned, the XAML Designer only works if you install Visual Studio on the System Drive (C: in my case) instead of using any other drive. After uninstalling Visual Studio keep the following things in mind...

• If your system partition is small, look to increase the space as the installation can take a lot of space based on the components selected.
• If you had already installed VS on any other drive, while reinstalling you will not be able to change the default installation directory.

This is because your initial path of installation was saved as in the registry. I tried solving this issue by following these steps. In my case I had found multiple keys in the registry and hence "Reset this PC" (Windows 10) by allowing only for my personal files to remain. This cleared out all the registry keys and I was able to install VS back on the C: drive, resulting in the XAML Designer finally working (Please note that resetting your pc will remove any applications installed on your machine)

Answer 2

UWP applications fail to launch from Visual Studio if project location and Windows Store apps installation path are on a non-default drive. Also, the XAML Designer will crash if you install Visual Studio and Windows Store apps to a non-default drive

Windows 10 allows users to change the default storage location of Windows Store applications. If you select a non-default drive for your apps, and if you install Visual Studio 2015 onto this drive, the XAML designer will not start and Windows Store app projects built on this drive cannot be run from Visual Studio.

Note: the workaround below will make any Store apps installed to the secondary drive inaccessible until next restart.

The file system driver can be temporarily disabled by running the following command from an admin command prompt:

fltmc detach filecrypt :

This will enable both running apps from this drive as well as usage of the XAML designer until the machine is restarted.

For a longer term fix, move your app or Visual Studio install to your system drive, or a secondary drive that has never been the storage location for Windows Store apps.

Answer 3

I had the same problem. I started visual studio as an administrator and the designer came back.

Answer 4

I got the same problem months ago. I Cleared the cache and Rebuild the solution. I got success.

Answer 5

You might want to try to clear the XAML Designer Shadow Cache. I've fixed al sorts of ailments with this process.