Correct me if I wrong, but, as I understand, to compile DX VC project I only need DX proper version installed and contets of "Includes", "libs" directories. And if it is true, is there anyway to get the contents of this directories except illegaly from other users ![]()

DX SDK 9.0 cutted edition :)
Jean-Pierre
Everybody take a deep breath.
We're _never_ cutting the docs out of the SDK.
We do, however, welcome suggestions on how to improve the SDK and how we can make our web-based DirectX Developer Center a better place to visit.
At the moment, there are no plans to change the SDK from what it is now. We want the SDK to be a "one stop shop" for your DirectX needs. Basically, almost everything you need to learn and develop DirectX will be in the SDK. This is what our developers have asked for the loudest.
We know that those of you on limited bandwidth will have challenges, but our #1 priority is to deliver the best collection of software that delivers up-to-date guidance with every SDK release. And we do it every two months, faster than any other SDK release in Microsoft (well, I'm pretty sure about that one).
I am, however, planning on expanding the DirectX Developer Center to offer more tutorials and samples, plus links to other contributing "fan sites" like The Zbuffer and CodeSampler.
lankapalli
Perhaps an SDK "lite" could be made, for people who want to compile code but aren't really developers. That would eliminate all the samples, and documentation (30MB for regular DX, and another 30MB for Managed). It's a valid idea to suggest to MS. I've seen many others put off by the large download as well.
Sorry I couldn't be any more help.
Mr_Mod
Rich MSFT
I still think a version without docs would be good for people who just need to compile existing code, who aren't developers.
A lighter version with docs could exist too. Right now the SDK includes managed and unmanaged. The managed docs are 27MB, and the managed samples another 8. All samples and media together are 112MB. Add another 3 or so for the managed debug runtimes.
To see how much we might save, I compressed a few folders.
After compression, the managed docs becomes 22.3MB.
All samples are 112MB. It's 44.7MB after compression.
A C++ only SDK, without samples, could then be 158MB-44.7MB-22.3MB = 91MB. Lets assume another 1MB for the debug runtime, bringing it down to 90MB. A managed only SDK would likely be a similar size.
Personally, I've got tons of bandwidth to use, so it doesn't bug me to download the full 158MB. If you're one of the people who dislike the large 158MB download, would 90MB be better, or is that still much too large If it's still too large, then there's no point at all. Bringing back orderable CD/DVDs would be the only solution for the coder on a budget.
NotaProgrammer
http://msdn.microsoft.com/directx/
jupitor_rules
What about this:
http://msdn.microsoft.com/library/default.asp url=/library/en-us/directx9_c/directx/directx9cpp.asp
All sdk documents can be read online. So they are not really required in the download.
a SDK light for compiling only, only requires the lib's and headers (16mb) if they have the correct redist installed.
SRichardson
However, since the DX team releases so frequently the DVDs are usually one SDK behind - e.g they currently ship the June SDK.
Adriano Richard
I have to strongly disagree about leaving out the docs. They are far too important and few enough people read them as it is. Making it easier to not read them won't help anyone.
Wiskers69
Eretria-chan
Trivia: The MS XDKs used to be released each month, until they switched to every 2 months. Currently the XDK is not updated, so the DX SDK is probably the fastest released MS SDK right now... assuming of course, the 360 SDK isn't currently releasing faster, which is entirely possible.
ren_reyes
scokim
It's not likely we will separate the DirectX "native" code from the managed code, for a variety of reasons, but going primarily back to the "everything in the SDK" approach we take.
While individual developers might not use both native and managed libraries, we find that almost all our ISVs _do_ use the managed DirectX libraries for various reasons.
Naoto Honda
Thanks