The most prevalent SharePoint API mistake that I see is the lack of freaking Exist properties on proxy objects.
What do I mean?
One can’t do this in order to test, for example, whether a SPList object exists:
PLAIN TEXT
C#:

public static void DoesMyListExistIDunno()

{

SPWeb web = SPContext.Current.Web;

SPList list = web.Lists["Heres My List"];

 

bool areYouThere = list.{An Exists Property Would Be [...]

Continue Reading This Article...

EDIT: OK, after reading through the comments I got, conceivably this is over-generalizing.  I didn't mean ALL SharePoint User Groups are like this. However my personal experience with the one I did IS like this. The ONLY point that I am trying to make is that there must exist a business / technology split with [...]

Continue Reading This Article...

I was at dinner last night with a SharePoint-y friend of mine and the dialogue arose about distinctions in what is coined as a SharePoint developer and as a SharePoint architect. In a majority of SharePoint projects these are advised as key, mutually exclusive roles that are obligatory for project success. And while I to [...]

Continue Reading This Article...

A preponderance of fundamental SharePoint proxy objects implement the IDisposable pattern, and therefore the disposal state of such objects becomes a subject of interest, this is predominantly important when using mock object schemes. Recently, I had to do just this and it's not actually very complicated, but I needed to remember it so decided to [...]

Continue Reading This Article...

The main site is going to be kinda iffy for a while since I am rotating the front end Apache server and I am making some edits to the new production main configuration httpd .conf file. As well, I haven't backed up the site since last year apparently, so will probably kick that off as [...]

Continue Reading This Article...