architecture - Frameworks vs. SDKs

Question

What is the difference between a framework and an SDK? Take, for example, the MS platform SDK and the .NET framework. Both have API's, both hide their inner workings, and both provide functionality that may not be quickly/easily accessible otherwise (in other words, they serve a real-world purpose).

So what's the difference? Is it primarily a marketing game of semantics, or are there actual differences in how developers are expected to interact with the software (and conversely, how the developers can expect the software to behave)? Is one expected to be higher- or lower-level than the other, etc?

Thanks!

EDIT: This question applies to SDKs and frameworks in general, not just the two mentioned above.

question from:https://stackoverflow.com/questions/424846/frameworks-vs-sdks

Answer 1

An SDK is expected to offer tools to program against a certain system resource or feature. A Framework not necessarily (although .NET offers a whole set of tools such as the compilers, etc - but these are mandatory for it to work anyways).

So, you could develop a Framework consisting solely of libraries, but if you call it SDK you will be expected to offer something to support development.