"The component does not have a resource identified by the uri" when starting .NET 5 app without debugger

[Skyppid]

• .NET Core Version: .NET 5 (5.0.102)
• Windows version: Windows 10 x64 (latest)
• Does the bug reproduce also in WPF for .NET Framework 4.8?: Not using .NET Framework anymore, but it does not reproduce in Core 3.1.

After initial issues with .NET 5 which I now could fix I face the problem that I cannot start our application without debugger anymore. As soon as I change all projects to TFM "net5.0-windows" (app is windows only) I get the exception:

System.Exception: Die Komponente "SomeApp.SplashScreen" verfügt nicht über eine Ressource, die vom URI "/SomeApp;V2021.0.191.22089;component/splashscreen.xaml" identifiziert wird.
at void System.Windows.Application.LoadComponent(object component, Uri resourceLocator)
at void SomeApp.SplashScreen.InitializeComponent() in F:/Arbeit/SomeApp vNext/SomeApp vNext/SomeApp GF/SplashScreen.xaml:line 1
at new SomeApp.SplashScreen() in F:/Arbeit/SomeApp vNext/SomeApp vNext/SomeApp GF/SplashScreen.xaml.cs:line 12
at void SomeApp.App.OnStartup(StartupEventArgs e)+() => { } in F:/Arbeit/SomeApp vNext/SomeApp vNext/SomeApp GF/App.xaml.cs:line 228
at void DevExpress.Xpf.Core.SplashScreenManager+ThreadContainerImpl.ShowWindow(object startupParam)
at void System.Threading.ThreadHelper.ThreadStart_Context(object state)
at void System.Threading.ThreadHelper.ThreadStart(object obj)

When I start with the debugger attached, it starts without any issues and works perfectly fine. To rule out that this is a DevExpress issue I can only tell that we're using the correct .NET Core packages and furthermore it works perfect with .Net Core 3.1. We're using latest DevExpress Core 20.2.5 packages.

Actual behavior: Instant crash when the first window (SplashScreen) is being initialized, error stack trace above.

Expected behavior: Start without any exceptions.

Minimal repro: I cannot share the project as it is company property. I simply changed all TFMs of our solution from netcoreapp3.1 to net5.0-windows. That's all. One thing has been changed though: I added <ProduceReferenceAssembly>false</ProduceReferenceAssembly> to every project since we don't need them and our plugin-system has issues when it finds assemblies twice.

[ryalanms]

Thanks, @Skyppid. Do you have a minimal repro I can look at?

[Skyppid]

@ryalanms I don't think so. Would be way too much work to trim it down and in my experience such issues then never reproduce. What I can tell is that on my colleagues computer it does work flawlessly.

I tried deleting the obj and bin folders and rebuild completely but it doesn't work. My colleague can start it without an exception, on my machine it crashes.

Can I give you any system info dump from both machines which might be helpful in finding the cause?

[chuongmep]

I have a same problem in here, please review, chuongmep/RevitAddInManager#7
I think Microsoft should acknowledge and fix this so that programmers don't spend a lot of time searching. Problem when I'm trying to use this same DLL in two different assemblies that both get loaded by another application.