[Bug 60478] New: Wine's .winmd files have "include/" in their assembly names; .NET Framework WPF apps fail with 0x80131047 (Razer installer)

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=60478

            Bug ID: 60478
           Summary: Wine's .winmd files have "include/" in their assembly
                    names; .NET Framework WPF apps fail with 0x80131047
                    (Razer installer)
           Product: Wine
           Version: 11.19
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: tools
          Assignee: [e-mail]
          Reporter: [e-mail]
  Target Milestone: ---
      Distribution: ---

Created attachment 82318
  --> http://bugs.winehq.org/attachment.cgi?id=82318
Razer installer log, XamlParseException 0x80131047

Wine installs ten .winmd files into C:\windows\system32\winmetadata, and the
assembly name inside each of them still carries the build directory:
windows.storage.winmd is named "include/windows.storage", windows.ui.winmd
"include/windows.ui", and so on for all ten. Checked on wine-11.19. Going by
the Arch packages the files first appear in 10.16 (10.15 has none) and the
names have been like this ever since.

Native .NET Framework 4.8 cannot parse such a name. Once one of the files is
loaded into a process, Assembly.FullName returns
  include\/windows.storage, Version=255.255.255.255, Culture=neutral,
  PublicKeyToken=null, ContentType=WindowsRuntime
and new AssemblyName() on that string throws FileLoadException 0x80131047.
WPF does this for every loaded assembly while it resolves BAML types, so the
next window fails to load.

I hit it with the Razer installer (RazerAxonInstaller.exe, Razer Installer
2.6.0.890, the same file as https://rzr.to/synapse-4-pc-download). Fresh
64-bit prefix, winetricks dotnet48, Windows 10: the process stays alive but
no window ever appears, and its log has XamlParseException 0x80131047 from
MainWindow.InitializeComponent (attached). Move system32\winmetadata out of
the prefix, change nothing else, and the window comes up. Same in two
separate prefixes.

Should the name simply be "Windows.Storage", without the directory?

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.