I have Visual Studio 2005 and want to teach myself DirectX in my free time. I downloaded the latest Windows 7 and DirectX SDKs. According to Microsoft's website, the latest DirectX SDK is not compatible with Visual Studio 2005 (I assume they mean it's not compatible with the SDK it came with). Can I configure VS2005 to use the SDKs I downloaded instead of the SDK it came with? If so, is there anything I should be particularly careful with?
The June 2010 DirectX SDK no longer supports Visual Studio 2005. You need to download an older version of the SDK and you'll be fine.
I'd wager you can encourage June 2010 to run under 2005. You may need to modify your headers slightly to make them 2005 compatible but the DX DLLs don't care what they get dynamically linked to by ... Install the SDK set up the include and library paths to point at the DirectX sdk ... compile and see what errors you get.
Related
I want develop Win32 and DirectX in Visual Studio Code.
I already installed gcc, mingw.
OS is windows10.
How do I setting it?
See Microsoft Docs for details on developing C++ code with VS Code.
The latest DirectX headers and link libraries are found in the Windows 10 SDK. Using the Visual C++ or clang/LLVM for Windows toolsets are the best options for consuming the latest Windows 10 SDK.
You may find the DirectX Tool Kit a useful starting point, although my tutorials focus on the Visual Studio MSBuild build environment. I also reference using CMake. You can use MSBuild through Visual Studio Community, and you can use CMake through either VS Community or VS Code.
I'm new to graphic programming with DirectX-11 and many tutorials reference to the DirectX SDK and the samples included in it. But I can't find my DirectX SDK folder on my desktop even though I can run DirectX programs over Visual Studio.
So where is the DirectX SDK normally stored on my PC. I'm using Windows 8, so DirectX was already included without me having to install it.
Thank you in advance.
The "DirectX Runtime" is part of the OS, not the "DirectX SDK". For a very long time, the DirectX SDK was what you downloaded and installed so a developer could get the headers, libraries and tools to write DirectX apps. That all changed in late 2010 when the DirectX SDK was deprecated and the core headers, libraries, and tools were integrated into the Windows SDK version 8.
See Where is the DirectX SDK? and Not So DirectSetup.
Unfortunately, most of the DirectX 11 tutorials and books were written for the old DirectX SDK and never updated for the Windows SDK. They often make use of D3DX11 which is now deprecated (see Living without D3DX for a list of replacements) and either D3DXMath or XNAMath which have both been replaced by DirectXMath.
The best way to get started with DirectX 11 development today is to install Visual Studio 2015 Community, Professional, or a higher edition. For C++ development, you need to add C++ via the custom install which will also add the Windows 8.1 SDK. Then, go check out the DirectX Tool Kit and it's tutorials. Once you have the basics down, you can go revisit those older tutorials and should be able to follow along using newer tech.
Alternatively, you can install the legacy DirectX SDK and set VS 2012/2013/2015 to use it, but there are a few caveats. First, there's some known issues installing the legacy DirectX SDK. Second, the include & library path order is inverted. Really there's only a few cases where you actually need the old DirectX SDK and for Windows 8 you don't need it. See The Zombie DirectX SDK.
BTW, I hope you are using Windows 8.1 and not Windows 8.0 as Windows 8.0 is no longer supported. See this FAQ.
I've cleaned up a lot of the old DirectX SDK samples so they don't require the legacy DirectX SDK. You can find them on GitHub.
See also DirectX SDKs of a certain age and DirectX SDK Tools Catalog.
With all that said, the default install location for the legacy DirectX SDK is C:\Program Files (x86)\Microsoft DirectX SDK (June 2010) on a 64-bit system or C:\Program Files\Microsoft DirectX SDK (June 2010) on a 32-bit system.
UPDATE:: While it is still a good idea to avoid the legacy D3DX9, D3DX10, and/or D3DX11 utility libraries for new projects, there is now a simpler method for using them that avoids the need to install the legacy DirectX SDK or to rely on the legacy "DirectX End-User Runtime" packages to deploy them. Just use the Microsoft.DXSDK.D3DX NuGet package. See this blog post for more details.
So, now that Visual Studio 2013 supports the Compact Edition AppBuilder.. Does anyone know where to find the right EMDK or how to create a new solution for a Motorols/Symbol MC9090 ?
The Motorola/Symbol EMDK for .NET only is only supported up to VS 2005/2008 since Windows Mobile SDKs only have support up to VS 2008.
This is the most recent EMDK release, check the release notes for installation requirements: EMDK for .NET
Update: Fixed link to new support site.
We still use Visual Studio 2008 for our EMDK development, however, I believe Microsoft has added .NET 3.9 support for Visual Studio 2015.
While the EMDK doesn't support Visual Studio 2015, the references would still work you just wouldn't have the toolbox objects. Not sure how big an issue that would be for you but we've never used them!
So if you started a new project, you should be able to select the EMDK dlls required for your project if you have the EMDK installed on your machine. You will need to select the correct processor architecture for your device (I'm guessing armv4i as most Motorola kit seems to be this)
You also may need to work with .NET 3.9 exclusively which might give you a headache getting that onto the MC9090. You'll not only need to install but you'll need to make it stick for a cold boot. This will either need a platform build or some very creative splicing of the .NET 3.9 CAB file and some SymScript! :)
I have a Windows CE 5.0-based Platform Builder image. It is intended to be installed on Visual Studio 2005. My team would like to upgrade our build tools to utilize Visual Studio 2012, but Visual Studio 2012 does not support this platform image.
To be clear; I am not asking whether or not Visual Studio 2012 (or higher) supports Platform Builder SDKs targeting Windows CE 5.0. That question has already been answered (more or less), and the answer is clearly "No."
Instead, what I'd like to do is install the Platform Builder SDK, and manually modify the Visual Studio 2012 environment to allow compilation of my Windows CE code. Features like remote debugging and deployment are acceptable losses to my team; we have our own pathway for deployment and debugging on our embedded device. What I'm really hoping to gain is simply the ability to build WinCE 5.0 code in VS2012, which was intended for VS2005. I am attempting to reduce the number of Visual Studio installations, and get access to the superior intellisense faculties of newer versions of Visual Studio.
Does anyone know if this is possible? How would I go about doing that?
There does not appear to be a way to do this, in such a fashion as to no longer require Visual Studio 2005.
You can, however, use registry hacks to force Visual Studio 2012 to build a WinCE 5.0 project by utilizing the compiler binaries from Visual Studio 2005, during compilation. This would allow you to develop code in VS2012, but would also require that VS2005 be installed for a successful build.
Here is an article explaining the steps to set this up.
VS2012 doesn't have any of the Windows CE compilers. The last one that shipped with compilers compatible with CE 5.0 was VS 2008, so that's the "latest" version you'll be able to use to build. (VS2012 is capable of building for Windows CE, but only for WEC 2013, and only after installing a WEC 2013 SDK, which includes the requisite compiler pieces).
In short, there's no way you can get VS2012 by itself to compile a CE 7.0 or earlier app.
There is a plug-in for VS 2013 that will allow you to use that IDE for managed code (I've never used it, so I can't say how well it works), but it still requires VS 2008 to be installed to get the compilers.
I'm planning to develop an application targetting the Honeywell Dolphin 6100 running Win CE 5.0. The documentation for the platform SDK and device SDK say that VS2005 is required to use them.
I don't have a copy of VS2005 and since it's not sold or supported by MS any more, I'd much rather buy VS2010. Does anyone know if the Honeywell D6X00 SDKs are compatible with VS2010?
Thanks for your help!
Matt
You can get access to VS2005 or VS2008 by purchasing VS2010 Pro with a MSDN subscription. You can then download old versions of VS and other stuff from the MSDN site. This is the path I have taken as there is lots of info on the web about how VS2010 does not support Win CE 5.0. If you plan to only write straight C++, you can use embedded visual c++ 4.0 which you can download for free from MS. If you have a lot of UI code, you may want to get VS2005.
Good luck.
Visual Studio 2010 removed support for developing Windows Mobile devices (instead replacing that with support for Windows Phone) - you would need to get hold of Visual Studio 2008 (or 2005, as you mention), which should still be available.