0
225
ViewsLoadFromContext Occurred
I have a very simple C# problem that loads a Windows WPF window from a library. Here's the code:
public partial class App : Application
{
public App()
{
MainWindow mainWindow = new MainWindow();
mainWindow.Show();
}
}
But when I run it breaks on the mainWindow.Show(); line with the following error:
Managed Debugging Assistant 'LoadFromContext' has detected a problem in 'C:\Users.....\bin\Debug\Test.vshost.exe'.
Additional information: The assembly named 'WpfXamlDiagnosticsTap' was loaded from 'file:///C:/PROGRAM FILES (X86)/MICROSOFT VISUAL STUDIO 14.0/COMMON7/IDE/COMMONEXTENSIONS/MICROSOFT/CLIENTDIAGNOSTICS/XAMLDIAGNOSTICS/x64/WpfXamlDiagnosticsTap.dll' using the LoadFrom context.
The use of this context can result in unexpected behavior for serialization, casting and dependency resolution. In almost all cases, it is recommended that the LoadFrom context be avoided. This can be done by installing assemblies in the Global Assembly Cache or in the ApplicationBase directory and using Assembly.Load when explicitly loading assemblies.
The MainWindow class just extends from System.Windows.Window;
I'm not exactly sure what this means and how to solve. Just upgraded to Visual Studio 2015.
If I ignore the exception and continue I get this when I close the last window:
3 answers
Answer question0
I'm running into the same issue after switching from Visual Studio 2013 to 2015. Some old projects (WPF, .NET 4.5, MVVM Light) produce this error - other not. In visual Studio i can skip the exception but newly created releases stop while loading and try to open the JIT Debugger.
Until now the only solution seems to be a rollback to Visual Studio 2013.
** UPDATE **
Finally I solved it in VS 2015 by unchecking the following option:
Tools –> Options –> Debugging –> General –> Enable UI Debugging Tools for XAML
0
I all of a sudden started seeing this error in VS2015 and fixed it by opening the "Exception Settings" Window (CTRL + ALT + E) and press the "Restore Settings" Button :
0
In VS2015 I am getting two exceptions from WpfXamlDiagnosticsTap.dll
- The first one is "LoadFromContext" and it occurs when activating the first window.
- The second one is "NotMarshalable" and it occurs when closing that window.
Simply ignoring those two Exception types allows me to run the application, and use the UI Debugging tools. I haven't observed any adverse effects.