Crash on startup
Dominiquini opened this issue · comments
- WDD Version: 5.4.0
- OS Version: Windows 10 x64
Steps to Reproduce:
- Install new version over 5.3.1
- Open the app
- Crash
Are you using the Microsoft Store version of WDD?: No
Log:
[2024-02-15 15:49:26.479] System.Resources.MissingManifestResourceException: Could not find the resource "WinDynamicDesktop.ThemeDialog.resources" among the resources "WinDynamicDesktop.g.resources", "WinDynamicDesktop.Properties.Resources.resources", "WinDynamicDesktop.locale.am.mo", "WinDynamicDesktop.locale.ar-ae.mo", "WinDynamicDesktop.locale.ar.mo", "WinDynamicDesktop.locale.az.mo", "WinDynamicDesktop.locale.bg.mo", "WinDynamicDesktop.locale.bn.mo", "WinDynamicDesktop.locale.ca.mo", "WinDynamicDesktop.locale.cs.mo", ... embedded in the assembly "WinDynamicDesktop", nor among the resources in any satellite assemblies for the specified culture. Perhaps the resources were embedded with an incorrect name.
at System.Resources.ManifestBasedResourceGroveler.HandleResourceStreamMissing(String fileName)
at System.Resources.ManifestBasedResourceGroveler.GrovelForResourceSet(CultureInfo culture, Dictionary`2 localResourceSets, Boolean tryParents, Boolean createIfNotExists)
at System.Resources.ResourceManager.InternalGetResourceSet(CultureInfo culture, Boolean createIfNotExists, Boolean tryParents)
at System.Resources.ResourceManager.GetObject(String name, CultureInfo culture, Boolean wrapUnmanagedMemStream)
at WinDynamicDesktop.ThemeDialog.InitializeComponent()
at WinDynamicDesktop.ThemeDialog..ctor()
at WinDynamicDesktop.ThemeManager.SelectTheme()
at WinDynamicDesktop.LaunchSequence.NextStep(Boolean themeReadyOverride)
at WinDynamicDesktop.AppContext..ctor(String[] args)
at WinDynamicDesktop.Program.Main(String[] args)
Log File:
Same on Windows 11 23H2
Confirmed, same here with Win11 23H2, was trying the MS Store edition, Italian:
Sorry about this, in 5.4.0 I accidentally added a dependency on a resource file missing from the Release build. Since the resource file was present locally, I didn't catch this when testing the Debug build. Publishing a patch in a few minutes, and in the future will try to test releases in a clean environment to prevent this from happening again.
same issue
Fixed in 5.4.1