7

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

    Error on Visual Studio

    Following are event viewer screens... Event Viewer

    Event Viewer

    I have checked online for other solutions and have already done the following...

    • Uninstall/Repair Visual Studio 2015 Update 1
    • Reset my Windows 10 PC 1511 update
    • Cleared the Designer/ShadowCache folder
    • Target environment has been set to x86/x64
    • Target framework set to 10240
    • Developer mode enabled
    • Updated graphic drivers
    • Have cleaned and rebuilt solution
    • Updated to VS15 Update 2

Please let me know if you have been able to find a solution to the above

Amit Philips
  • 387
  • 6
  • 17
  • Cant say its the same exception, but I get an exception frequently when viewing the XAML designer in VS2015. To resolve it I usually try 3 things: 1. Click the link to reload it. 2. Close the file, recompile, then open it again, or 3. Clean the project, then try 1 & 2 again. – Mike_G Dec 31 '15 at 16:26
  • Also, it looks like an UnAuth exception is happening, I would make sure you are running VS as an administrator. – Mike_G Dec 31 '15 at 16:29
  • @Mike_G yea I have tried the steps the way you have mentioned and I still can't get it to work. And yes VS is running in Administrator mode. The xaml designer doesn't work for me at all even if its a blank project that is compiling correctly. – Amit Philips Dec 31 '15 at 21:11
  • Was a solution ever found here? I'm experiencing the same thing on one PC. XAML Designer will crash within seconds with the above mentioned Remoting issue. On another PC I have no issue with the exact same project. I've found no solution so far but am hoping that Update 2 will be announced @ //Build in a few days and might and provide a fix. – 1iveowl Mar 30 '16 at 07:02
  • I have installed Update 2 and subsequently also cleared up my shadowcache. Unfortunately still face the exact same error ! – Amit Philips Apr 03 '16 at 06:29

5 Answers5

3

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.

peterfaraday MSFT
  • 81
  • 5
2

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

Daniel
  • 9,312
  • 3
  • 48
  • 48
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)

Community
  • 1
  • 1
Amit Philips
  • 387
  • 6
  • 17
0

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

Community
  • 1
  • 1
1iveowl
  • 1,622
  • 1
  • 18
  • 31
  • I've upgraded to VS 2015 update 2 as well and I don't have the issue any longer. Then again, I've also made a number og changes to the code since I last tried on the PC that was failing. – 1iveowl Apr 03 '16 at 08:14
  • well even creating a blank new app also results in that error for me – Amit Philips Apr 03 '16 at 12:59
-1

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

Prateek Gogia
  • 25
  • 9
  • That's already what Jasper Hedegaard Bojsen said in the other answer. When you answer, please include new information. – Artjom B. Apr 03 '16 at 13:28