Desktop Bridge VCLib package links deprecated with no clear way forward

[riverar]

The Desktop Bridge VCLib package links (e.g., for Microsoft.VCLibs.arm64.14.00.Desktop.appx) appear to be deprecated according to Microsoft documentation at https://learn.microsoft.com/en-us/troubleshoot/developer/visualstudio/cpp/libraries/c-runtime-packages-desktop-bridge. However, there is no clear migration path provided for applications that currently depend on these links through .appinstaller and other means.

Our .appinstaller distribution channel currently relies on these deprecated VCLib package links:

<Dependencies>
    <Package
        Name="Microsoft.VCLibs.140.00.UWPDesktop"
        Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"
        Version="14.0.30704.0"
        ProcessorArchitecture="x86"
        Uri="https://aka.ms/Microsoft.VCLibs.x86.14.00.Desktop.appx"
    />
    <Package Name="Microsoft.VCLibs.140.00.UWPDesktop"
        Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"
        Version="14.0.30704.0"
        ProcessorArchitecture="x64"
        Uri="https://aka.ms/Microsoft.VCLibs.x64.14.00.Desktop.appx"
    />
    <Package Name="Microsoft.VCLibs.140.00.UWPDesktop"
        Publisher="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"
        Version="14.0.30704.0"
        ProcessorArchitecture="arm64"
        Uri="https://aka.ms/Microsoft.VCLibs.arm64.14.00.Desktop.appx"
    />
</Dependencies>

What is the recommended replacement for these deprecated VCLib package links? When do I need to move off these links? Will Microsoft provide similar new links?

[DarranRowe]

My reading is the download links are deprecated.

"The following package download links are now deprecated, and may no longer work in the future. Make sure to use the method described above to obtain the framework packages."

I believe it is saying that the only guaranteed way to obtain these packages is through a Visual Studio installation.

[riverar]

Yes, that's why this issue exists. I'll edit that above and make it more clear, sorry for any confusion.

[ssparach]

Thanks for reporting this! We are currently investigating.

[MahmoudGSaleh]

The appx links were originally provided for limited scenarios (sandboxed/offline). However, with newer compliance requirements, we can no longer provide that as an option. Instead, users can install Visual Studio 2019, 2022, or 2026, selecting the Universal Applications development option. Once installed, the appx files can be found under C:\Program Files (x86)\Microsoft SDKs\Windows Kits\10\ExtensionSDKs.

[riverar]

@MahmoudGSaleh There is no Universal Applications workload and no MSIX files in the location you suggested. Want to try again? 😆

[riverar]

Oh, I see. C:\Program Files (x86)\Microsoft SDKs\Windows Kits\10\ExtensionSDKs\Microsoft.VCLibs.Desktop\14.0\Appx\[Debug|Retail]\[x86|x64|arm64]

~~Are application developers legally able to redistribute/host these somewhere to light up the appinstaller dependency scenario above? 🤔~~

Note to self: Redistribution (with your app only) is allowed per terms https://learn.microsoft.com/visualstudio/releases/2022/redistribution#universal-windows-apps-and-windows-store-apps

So sounds like Microsoft is giving up on hosting these files and we're stuck hosting them ourselves / bearing that cost, great. Sigh.