The bulk of the “DirectX” headers are already in the modern Windows SDK, so you do not need the legacy DirectX SDK at all for these components: DirectX componentĭ2D1.h, D2D1Helper.h, D2DBaseTypes.h, D2Derr.h, d2d1.libĭ3D11.h, D3D11SDKLayers.h, D3D11Shader.h, d3d11.libĭ3D10.h, D3D10effect.h, d3d10misc.h, d3d10sdklayers.h, D3D10shader.h, d3d10.libĭ3d9.h, d3d9caps.h, d3d9types.h, d3d9.libĭXGI.h, DXGIFormat.h, DXGIType.h, dxgi.libĭDraw.h. Impact for existing developersĪs has been the case the past decade, the strong recommendation is to no longer rely on the legacy DirectX SDK or it’s legacy DirectSetup redist solution. cab files you ship to control overall download/media sizes remains a useful option per Microsoft Docs.įor legacy DirectX SDK-built games using Desktop Bridge, you can still make use of the of the “DirectX Framework Package” 86 / Microsoft.DirectX.圆4 which remain available as the appx is signed with SHA-256. Following the legacy recommendations of cutting down the number of. See this blog post.įor games that included the DirectX SDK REDIST folder in their installation, there is no impact as that continues to work. These components are strictly serviced as part of the Operating System.
it doesn’t change Direct3D, DirectDraw, DirectSound, DirectInput, etc.) at all. Impact for existing gamesĪs I’ve communicated numerous times, this legacy installer never installs DirectX (i.e.
The payload DLLs are still using SHA-1, and there are known security issues, so it is highly recommended you move to the replacements mentioned in this post. As of February 20, 2021, these three downloads have been republished using SHA-256 signing for the ‘outer’ containers–there’s been no change to the contents or binaries. In January 2021 they were removed from the Microsoft Download Center. This impacted the legacy DirectX SDK, the DirectX End-User Runtime, and the DirectX End-User Runtime Web Installer. The original timeline was stretched out a bit due to COVID-19, but as of January 2021 this content is no longer hosted by Microsoft servers. Microsoft announced last year that it was retiring all SHA-1 signed content from Microsoft Downloads in this blog post since the SHA-1 algorithm is no longer considered secure.
0 kommentar(er)
