Derik Whittaker



Images in this post missing? We recently lost them in a site migration. We're working to restore these as you read this. Should you need an image in an emergency, please contact us at
Rant: Sharepoint SDK Installation

Today I needed to install the sharepoint SDK because I need to write some code to access it.  So I installed the OfficeServerSDK.exe setup which contains all the SDK stuff.  After it is installed I had to ‘find’ where on my drive it was placed.  After some hunting, I found it on my E: drive.  Great.

Inside the new directory is a great big .chm file.  I opened this bad boy up and it looked great.  There is more information inside this chm than I can process in a life time.  However, NOWHERE does it tell you where to find the damn .dll’s with the sdk.

So I set out searching my box for Microsoft.sharepoint.dll.  It was NOT found.  I started searching the net to only come across this post (found here).  Turns out the .dll’s are NOT installed with the sdk, WTF.  I had to go look on the server where WSS was installed in order to find them.  But the only way to find the file was to do an entire search for Microsoft.Sharepoint.dll on the hard drive.  I finally found it at C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\ISAPI

What SDK does not install the damn assemblies…..

Ok, My rant is over.

Posted 07-13-2007 10:22 AM by Derik Whittaker
Filed under:



expresso wrote re: Rant: Sharepoint SDK Installation
on 07-15-2007 11:01 PM

I remember SharPoint as a big waste.  I remember that prior to 2007, same problem...couldn't find the damn API and found out that there was no API you could customize.  That the only way to customize it was through lousy web parts which limits you to some extent.

For example, what if I liked whatever module out of the box but that I wanted to expand that module to customize it to add some functionality that was obviously missing in a real-world shop.  Well, I found that you can't, at least prior to SharePoint 2007 so I ended up not wanting to even touch it.  I don't mind using it as a tool, but when it comes down to the business wanting to "integrate into it", in my experience, you're limited to web parts which only goes just so far.

The point MS is missing is that if they opened up their API, it would be so awesome.  I would then be able to tweak the C# source to do some real extra useful things for my enviornment.

I don' t know if 2007 is any better.

About The CodeBetter.Com Blog Network
CodeBetter.Com FAQ

Our Mission

Advertisers should contact Brendan

Google Reader or Homepage Latest Items
Add to My Yahoo!
Subscribe with Bloglines
Subscribe in NewsGator Online
Subscribe with myFeedster
Add to My AOL
Furl Latest Items
Subscribe in Rojo

Member Projects
DimeCasts.Net - Derik Whittaker

Friends of
Red-Gate Tools For SQL and .NET


SmartInspect .NET Logging
NGEDIT: ViEmu and Codekana
NHibernate Profiler
Balsamiq Mockups
JetBrains - ReSharper
Web Sequence Diagrams
Ducksboard<-- NEW Friend!


Site Copyright © 2007 CodeBetter.Com
Content Copyright Individual Bloggers


Community Server (Commercial Edition)