2 DirectX 11.1 for Windows 7 SP1 and Windows Server 2008 R2 SP1 3 DirectX 11.0 for Windows Vista SP2 and Windows Server 2008 SP2 4 DirectX 9.0c for Windows XP and Windows Server 2003. DirectX is tightly integrated into the operating system when installed so you can’t simply install DirectX 10 or 11 on XP because it won’t work. Although we’re now on DirectX 11 for Windows Vista, 7 and 8, and the next Windows will probably come with DirectX 12, Windows XP is stuck on DirectX 9 which is now over 10 years old. Windows 7 includes DirectX 11, and Windows 10 includes DirectX 12. When developers are developing games, they choose the DirectX versions they want to target. For example, a game written only for DirectX 11 wouldn’t run on Windows XP, where the latest available version is DirectX 9. RELATED: How to Use the DirectX Diagnostic in Windows.

-->

Visual Studio supports multiple platform toolsets. That means it's possible to target operating systems and runtime libraries that aren't supported by the default toolset. For example, by switching the platform toolset, you can use the Visual Studio 2017 C++ compiler to create apps that target Windows XP and Windows Server 2003. You can also use older platform toolsets to maintain binary-compatible legacy code and still take advantage of the latest features of the Visual Studio IDE.

How To Install Directx 11 On Windows Xp Sp2 Download

The v142 toolset supplied in Visual Studio 2019 doesn't include support for creating code for Windows XP. Support for Windows XP development by using the Visual Studio 2017 v141_xp toolset is available as an individual component option in the Visual Studio Installer.

Install the Windows XP platform toolset

To get the Visual Studio 2017 platform toolset and components to target Windows XP and Windows Server 2003, run the Visual Studio Installer. When you initially install Visual Studio or when you modify an existing installation, make sure the Desktop development with C++ workload is selected. In the list of optional components for this workload, choose Windows XP support for C++, and then choose Install or Modify.

To get the v141_xp platform toolset and components to target Windows XP and Windows Server 2003, run the Visual Studio Installer. When you initially install Visual Studio, or when you modify an existing installation, make sure the Desktop development with C++ workload is selected. In the Individual components tab, under Compilers, build tools, and runtimes, choose C++ Windows XP Support for VS 2017 (v141) tools [Deprecated], and then choose Install or Modify.

Windows XP targeting experience

The Windows XP platform toolset that's included in Visual Studio is a version of the Windows 7 SDK, but it uses the Visual Studio 2017 C++ compiler. It also configures project properties to appropriate default values, for example, the specification of a compatible linker for down-level targeting. Only Windows desktop apps created by using a Windows XP platform toolset can run on Windows XP and Windows Server 2003. Those apps can also run on more recent Windows operating systems.

To target Windows XP

In Solution Explorer, open the shortcut menu for your project, and then choose Properties.
In the Property Pages dialog box for the project, select Configuration Properties > General. Set the Platform Toolset property to your preferred Windows XP toolset. For example, choose Visual Studio 2017 - Windows XP (v141_xp) to create code for Windows XP and Windows Server 2003 by using the Microsoft C++ compiler in Visual Studio 2017.

C++ runtime support

Along with the Windows XP platform toolset, several libraries include runtime support for Windows XP and Windows Server 2003. These libraries are: the C Runtime Library (CRT), C++ Standard Library, Active Template Library (ATL), Concurrency Runtime Library (ConCRT), Parallel Patterns Library (PPL), Microsoft Foundation Class Library (MFC), and C++ AMP (C++ Accelerated Massive Programming) library. For these operating systems, the minimum supported versions are: Windows XP Service Pack 3 (SP3) for x86, Windows XP Service Pack 2 (SP2) for x64, and Windows Server 2003 Service Pack 2 (SP2) for both x86 and x64.

These libraries are supported by the platform toolsets installed by Visual Studio, depending on the target:

Library	Default platform toolset targeting Windows desktop apps	Default platform toolset targeting Store apps	Windows XP platform toolset targeting Windows XP, Windows Server 2003
CRT	X	X	X
C++ Standard Library	X	X	X
ATL	X	X	X
ConCRT/PPL	X	X	X
MFC	X	X
C++ AMP	X	X

Note

Apps that are written in C++/CLI and target the .NET Framework 4 run on Windows XP and Windows Server 2003.

Differences between the toolsets

Because of differences in platform and library support, the development experience for apps that use a Windows XP platform toolset isn't as complete as for apps that use the default Visual Studio platform toolset.

C++ language features
Only C++ language features implemented in Visual Studio 2012 are supported in apps that use the v110_xp platform toolset. Only C++ language features implemented in Visual Studio 2013 are supported in apps that use the v120_xp platform toolset. Only C++ language features implemented in Visual Studio 2015 are supported in apps that use the v140_xp platform toolset. Only C++ language features implemented in Visual Studio 2017 are supported in apps that use the v141_xp platform toolset. Visual Studio uses the corresponding compiler when it builds using the older platform toolsets. Use the most recent Windows XP platform toolset to take advantage of additional C++ language features implemented in that version of the compiler.
Remote debugging
Remote Tools for Visual Studio doesn't support remote debugging on Windows XP or Windows Server 2003. To debug an app locally or remotely on Windows XP or Windows Server 2003, use a debugger from an older version of Visual Studio. It's similar to debugging an app on Windows Vista, which is a runtime target of the platform toolset, but not a remote debugging target.
Static analysis
The Windows XP platform toolsets don't support static analysis because the SAL annotations for the Windows 7 SDK and the runtime libraries are incompatible. You can still perform static analysis on an app that supports Windows XP or Windows Server 2003. Temporarily switch the solution to target the default platform toolset for the analysis, and then switch back to the Windows XP platform toolset to build the app.
Debugging of DirectX graphics
Because the Graphics Debugger doesn't support the Direct3D 9 API, it can't be used to debug apps that use Direct3D on Windows XP or Windows Server 2003. However, if the app implements an alternative renderer based on Direct3D 10 or Direct3D 11 APIs, you can use the Graphics Debugger to diagnose problems.
Building HLSL
The Windows XP toolset doesn't compile HLSL source code files by default. To compile HLSL files, download and install the June 2010 DirectX SDK, and then set the project's VC directories to include it. For more information, see the 'DirectX SDK Does Not Register Include/Library Paths with Visual Studio 2010' section of the June 2010 DirectX SDK download page (Archived link).

So basically because there are still some people reading my old post about pcsx2, so i guess it’s better for me to rewrite it to reflect the new changes although actually there are almost next to no changes but since most people trying to use my sample configuration directly without adjusting it first, i think it’s better to write a new post that shows you directly on which plugins you should be using (note: this is intended for general purpose)

But obviously, credits should be given to the PCSX2 Team for making such wonderful program available for free to anyone

And so, let’s begin

Requirements

– PCSX2 any version both stable or svn