R – What SharePoint development concepts are the hardest for ASP.Net developers to understand

asp.netsharepointsharepoint-2007sharepoint-2010

I'm trying to put together SharePoint 2007 (and, eventually, 2010) training materials for experienced ASP.Net developers, and having done SharePoint for years, I don't really remember where the worst sticking points were at the beginning – not to mention the amount of Googlable SharePoint content is greater by an order of magnitude than two years ago.

That said, what SharePoint concepts are the hardest to grasp, and/or what parts of SharePoint are esoteric enough to be non-obvious to a newbie SharePoint developer just diving in?

Best Answer

Greg,

In my experience, issuing relating to proper object disposal (SPWeb and SPSite objects that, in turn, reference SPRequest wrappers around unmanaged COM objects) are a common gotcha and the source of many scalability, performance, and other coding issues. Once Microsoft realized the scale of the issue and the degree of developer confusion in this area, they wrote a large guidance article (http://msdn.microsoft.com/en-us/library/aa973248.aspx) and developed the SPDisposeCheck tool (http://code.msdn.microsoft.com/SPDisposeCheck).

That's my vote for "non-obvious to a newbie SharePoint developer just diving in" :-)

For what it's worth!

Related Topic