The XAML Designer has exited unexpectedly. (Exit code: 8000808c)

nirzaf commented 4 years ago

.NET Core Version: (e.g. 3.1 LTS Version)
Windows version: (Windows 10 Version 1607 for x64 (KB4537477))
Does the bug reproduce also in WPF for .NET Framework 4.7.2?: No
using Visual Studio version 16.5 just today installed, after that only having this problem Problem description: I created a new WPF application with .NET Core 3.1 SDK Actual behavior:

gomathip02 commented 4 years ago

@chabiss - Can you pls look into this issue?

dirvo commented 4 years ago

I could not repro this when creating a fresh WPF .NET Core app in VS 16.5.4.

However, I got the same exit code: 8000808c in one of my projects where I had renamed a referenced assembly. I found the following error in the application event log (project name replaced):

Description: A .NET Core application failed.
Application: WpfSurface.exe
Path: C:\Users\xxx\AppData\Local\Microsoft\VisualStudio\16.0_a2957f95\Designer\Cache\11108045179x86DA\WpfSurface.exe
Message: Error:
  An assembly specified in the application dependencies manifest (WpfSurface.deps.json) was not found:
    package: 'MyAssembly.ProjectName', version: '1.0.0'
    path: 'MyAssembly.ProjectName.dll'

The missing assembly is referenced by the WPF project and has been renamed (and the WPF app as well). The manifest still contains the old name whereas the cache folder contains the assembly with its new name.

I could resolve this by closing VS and manually deleting all bin and obj folders (Project > Clean was not enough).

Roberto2707 commented 4 years ago

I get the same issue in vs 16.6.2

mentorfloat commented 4 years ago

I am encountering the same issue in VS Version 16.6.5, but the condition that caused it is different.

I created a new WPF project targeting .Net Core 3.1 and linked a UWP project and another UWP class to test out custom UWP controls via Xaml island. The NuGet package manager was playing up (random missing references) and it wouldn't let me clear the NuGet cache. I restarted VS and the error popped up.

I can confirm that @dirvo 's suggestion to close VS and delete all bin and obj folders worked for me.

I also deleted nuget.config in %appdata%\NuGet\ just in case.

re4dev commented 3 years ago

I could not repro this when creating a fresh WPF .NET Core app in VS 16.5.4.

However, I got the same exit code: 8000808c in one of my projects where I had renamed a referenced assembly. I found the following error in the application event log (project name replaced):
Description: A .NET Core application failed.
Application: WpfSurface.exe
Path: C:\Users\xxx\AppData\Local\Microsoft\VisualStudio\16.0_a2957f95\Designer\Cache\11108045179x86DA\WpfSurface.exe
Message: Error:
  An assembly specified in the application dependencies manifest (WpfSurface.deps.json) was not found:
    package: 'MyAssembly.ProjectName', version: '1.0.0'
    path: 'MyAssembly.ProjectName.dll'
The missing assembly is referenced by the WPF project and has been renamed (and the WPF app as well). The manifest still contains the old name whereas the cache folder contains the assembly with its new name.

I could resolve this by closing VS and manually deleting all bin and obj folders (Project > Clean was not enough).

"I could resolve this by closing VS and manually deleting all bin and obj folders (Project > Clean was not enough)." - Thats it

fatihyildizhan commented 1 year ago

I am encountering the same issue:

-- .NET 5 -- WPF -- Visual Studio 17.6.2

SOInfotech commented 1 year ago

I also get the exact same error as fatihyildizhan above with but with .NET6.

dotnet / wpf

The XAML Designer has exited unexpectedly. (Exit code: 8000808c) #2780