I get this question from time to time. People are used to downloading some separate package that includes the SDK because that is how Windows and a few other Microsoft products do it. Since our entire product is built on top of the SDK we ship the SDK with the product itself. The binaries that we support people including in their Visual Studio projects and using in their solutions are found in the folders below (depending on version) on the SCSM management server.
2010: C:\Program Files\Microsoft System Center\Service Manager 2010\SDK Binaries
2012: C:\Program Files\Microsoft System Center\Service Manager 2012\SDK Binaries
If you installed to a different location than C:\Program Files then just look for a similar path in the location that you installed to.
These are the three assemblies you should include references to in your Visual Studio projects:
Travis, mistype in path for 2012 Sdk;)
Pinged him already via Lync ;-)
Thanks Travis, but I think providing it as a redistributable download would still make sense.
Especially for 3rd party products that do not run on the management server directly.
Today one has to install the according console in order to get a 3rd party extension up and running one another server.
A redist-package would simplify the deployment a lot and would make it more lightweight I believe..
Of course I agree, a dev would have no problem taking the bits from the folder and linking them into VS :-)
This really should be a separate download, or at least a redist EXE as part of the service manager install, or maybe just install it by default with Console installs? I have noticed MANY MANY areas where Service Manager is not following Microsoft best practices, especially the SE Baseline.