https://bugs.winehq.org/show_bug.cgi?id=54825
Bug ID: 54825 Summary: Visual Studio C++ Build Tools fails to install with 'Could not find Windows Runtime type' Product: Wine-staging Version: 8.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: lupino8211@gmail.com CC: leslie_alistair@hotmail.com, z.figura12@gmail.com Distribution: ---
Created attachment 74328 --> https://bugs.winehq.org/attachment.cgi?id=74328 full_install.log
I'm trying to install MSVC toolchain in wine in docker, but didn't succeed. I'm installing tools in following order: - dotnet48 - winecfg /v win10 - Visual Studio C++ Build Tools
Installation ends in the following error (from logs which can be found in wine user's Temp directory):
[025c:000a][2023-04-13T20:48:57] Error 0x80131522: Rethrowing the exception from the engine: Could not find Windows Runtime type 'Windows.Networking.Connectivity.NetworkCostType'.
but how I can inspect, these DLL's exist in the following paths: /root/.wine/drive_c/windows/system32/windows.networking.connectivity /root/.wine/drive_c/windows/syswow64/windows.networking.connectivity and should contain mentioned type.
How to reproduce:
Download vs_BulidTools.exe from https://download.visualstudio.microsoft.com/download/pr/d24d0627-f1e2-4a69-a...
Install it via: wine cmd /c start /wait vs_BuildTools.exe --quiet --add "Microsoft.VisualStudio.Workload.VCTools;includeRecommended" --add "Microsoft.VisualStudio.Workload.MSBuildTools;includeRecommended" --add "Microsoft.VisualStudio.Workload.ManagedDesktopBuildTools;includeRecommended" --add "Microsoft.VisualStudio.Component.VC.Tools.x86.x64;includeRecommended"
https://bugs.winehq.org/show_bug.cgi?id=54825
Lorenzo Ferrillo lorenzofer@live.it changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |lorenzofer@live.it
--- Comment #1 from Lorenzo Ferrillo lorenzofer@live.it --- Seems this require a full availability of the WinMD manifests in the system and a compliant implementation of RoResolveNamespace