The DXSDK isn't intended for end-users. It contains developer tools, programming documentation, and utility libraries. In particular, it does not contain a new version of the DX runtimes.
The DXSDK isn't intended for end-users. It contains developer tools, programming documentation, and utility libraries. In particular, it does not contain a new version of the DX runtimes.
I've not checked out the full details myself, but the end-user package will contain updated binaries for any of the optional components tied to the Feb'07 SDK release. Most notably this has been the updated D3DX DLL's (d3dx9_xx.dll) but can also include XInput/XACT components as well.
The February end-user package will only be required if you want to run software built with the February SDK, it's unlikely to offer anything for existing applications - although I'm not entirely sure if there are any rules against them shipping updates to older components via this mechanism...
There aren't, so they can ship updates to the core DirectX components via these redists as you suspect. I think it's usually made clear when that's the case, though.
There aren't, so they can ship updates to the core DirectX components via these redists as you suspect. I think it's usually made clear when that's the case, though.
The bit that threw me is that the move to dynamically linked D3DX was to allow for updates and fixes via Windows Update; but they won't distribute new D3DX DLL's via this mechanism. Which, if read one way, could mean that the bimonthly end user redist's are for NEW components whereas fixes to OLD components would be via auto-update.