none
XAML Designer crashed on new UWP projects after Anniversary Update

    Question

  • Hi,
    Visual Studio 2015 ist not usable for UWP Projects after the Anniversary Update when using a Display Dock.
    If the dock in unplugged, the Designer works as expected.

    Configuration:
    - Win10 Enterprise with Anniversary Update (14393)
    - VS2015 Enterprise Update 3
    - DELL XPS15 with Display Dock "DELL D3100"

    UWP development is not possible in a professional environment.

    It seems that the issue is not limited to the DELL display dock:
    http://www.displaylink.org/forum/showthread.php?p=81118

    The XAML Designer shows several Exceptions:

    System.Runtime.Remoting.RemotingException
    [2584] Designer process terminated unexpectedly!

    -----------------------------------
    COMException: Error HRESULT E_FAIL has been returned from a call to a COM component.
       at Windows.UI.Xaml.DependencyObject.SetValue(DependencyProperty dp, Object value)
       at Microsoft.VisualStudio.DesignTools.WindowsXamlDesigner.InstanceBuilders.FrameworkElementInstanceBuilder.OnInitialized(IInstanceBuilderContext context, ViewNode target, Object instance)
       at Microsoft.VisualStudio.DesignTools.Platform.InstanceBuilders.ClrObjectInstanceBuilder.Initialize(IInstanceBuilderContext context, ViewNode viewNode, Boolean isNewInstance)
       at Microsoft.VisualStudio.DesignTools.Platform.InstanceBuilders.ViewNodeManager.InitializeInstance(IInstanceBuilder builder, ViewNode viewNode, Boolean isNewInstance)
    -----------------------------------
    System.Runtime.InteropServices.COMException
    Exception from HRESULT: 0x8876086C
       at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
       at Microsoft.VisualStudio.DesignTools.WindowsXamlDesigner.Views.XamlUIPresenterWrapper..ctor(PresentSiteWrapper presentSite)
       at Microsoft.VisualStudio.DesignTools.WindowsXamlDesigner.WindowsStoreXamlPlatform.ActivatePlatformContext()
       at Microsoft.VisualStudio.DesignTools.Designer.PlatformContextChanger.ShutdownAndReactivate()
       at Microsoft.VisualStudio.DesignTools.Designer.PlatformContextChanger.<UpdateForPlatformChange>b__18_0()
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
       at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
       at System.Windows.Threading.DispatcherOperation.InvokeImpl()
       at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Windows.Threading.DispatcherOperation.Invoke()
       at System.Windows.Threading.Dispatcher.ProcessQueue()
       at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
       at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
       at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
       at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
       at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
       at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
       at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
       at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
       at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
       at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
       at System.Windows.Application.RunDispatcher(Object ignore)
       at System.Windows.Application.RunInternal(Window window)
       at System.Windows.Application.Run(Window window)
       at Microsoft.VisualStudio.DesignTools.DesignerContract.Isolation.DesignerProcess.RunApplication()
       at Microsoft.VisualStudio.DesignTools.DesignerContract.Isolation.DesignerProcess.DesignProcessViewProvider.AppContainerDesignerProcessRun(String[] activationContextArgs)
       at Microsoft.VisualStudio.DesignTools.DesignerContract.Isolation.DesignerProcess.DesignProcessViewProvider.<>c__DisplayClass3_0.<applicationView_Activated>b__0()
       at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
    Monday, September 05, 2016 3:02 PM

Answers

  • Hi Weiwei,

    Thanks for your reply.
    I can reproduce the error with another Display Dock.

    I've submitted this issue to Visual Studio Connect:
    https://connect.microsoft.com/VisualStudio/feedback/details/3101540/xaml-designer-crashed-on-new-uwp-projects-after-anniversary-update

    Best regards
    netsrac

    Tuesday, September 06, 2016 8:06 AM

All replies

  • Hi netsrac,

    Since I don't have the environment to connect with Display Dock to verify this issue in my side, I suggest you troubleshoot this issue with following steps by yourself. Thanks for your understanding.

    1. On current Windows 10 machine, change another Display Dock to check whether the XAML designer also crashes.
    2. Change another machine which is not install the Anniversary Update and then using the same Display Dock.
    3. Using another version of Visual Studio and the repeat step 1 and step 2

    Above steps could help us confirm whether this issue related to the Display Dock, the Anniversary Update or Visual Studio itself.

    In addition, I found there has other communities also has this issue on StackOverflow, I suggest you submit this issue to Visual Studio Connect. I think the report team expert will verify this issue seriously.

    Best Regards,
    Weiwei


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Tuesday, September 06, 2016 5:55 AM
    Moderator
  • Hi Weiwei,

    Thanks for your reply.
    I can reproduce the error with another Display Dock.

    I've submitted this issue to Visual Studio Connect:
    https://connect.microsoft.com/VisualStudio/feedback/details/3101540/xaml-designer-crashed-on-new-uwp-projects-after-anniversary-update

    Best regards
    netsrac

    Tuesday, September 06, 2016 8:06 AM
  • Hi netsrac,

    Thanks for your feedback.

    Since this issue has been submit to Connect, I suggest you mark your connect reply as answer, which could let other communities who has the same issue to vote and add comments for your feedback. And I also will following the update of your feedback. If any updates, I will update the content here.

    Best Regards,
    Weiwei


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Tuesday, September 06, 2016 8:12 AM
    Moderator