SharePoint Architect’s Workspace & Thoughts on Microsoft’s Leadership, Today & Beyond

MOSS 2007 is a very powerful development platform for the experienced developers; but for newbies they tend to see SharePoint or MOSS 2007 as a difficult platform to use. In the end, SharePoint and even the impressive MOSS 2007 is nothing more than a landing page. Below are the shattering mistakes newbies make:

1. SQL Server Tables – so many newbies are afraid of using SharePoint lists and instead they create everything in SQL Server Tables from maintenance, transaction and report tables, etc. SharePoint lists are very powerful and it provides you with the add, edit, delete, view functionalities on the fly.

Furthermore, MOSS 2007 already allows you to create event handlers and activate them as features which listen to any list you desire. Customization for list and column behaviours has never been this easy.

2. ASP.NET Pages – if you create everything in SQL Server tables, you would need aspx pages to go with it which means you have to write stored procedures, business assemblies and as such. Adding all these codes mean you have to write more documents & testing paths which translate to more resources and time.

Come to think of it, all these things are already present in SharePoint.

3. Stand alone SSRS – if you have SQL Server tables, aspx pages, then you would need reports and normally SQL Reporting Services fit the bill. Unfortunately, since you have not developed your SharePoint skills, you end up creating a stand alone SSRS installation which does not integrate in MOSS using the SQL Server 2005 Reporting Services Add-in.

That is additional work from configuration, deployment and testing perspective.

4. InfoPath Obsessed – let’s say you are smart enough not to create everything in SQL Server tables and instead use InfoPath forms and publish them in document libraries.

I would give you a pat on the back because at last, you have are starting to use features of MOSS 2007, but the problem is you created everything in InfoPath forms including the smallest master list maintenace. You placed all the business rules inside InfoPath forms without regard to security. Deployment comes and you are surprised that it did not work out according to plan.

Be reasonable and make sure you don’t get too excited using InfoPath forms in everything you do. Use them when complex controls and user interaction is required that using lists is no longer a good option.

5. Take the MOSS Path – for team leads who do not have experience in MOSS, do not be afraid to take the MOSS path.

Typically, you would need a learning curve of one to two weeks to make your developers comfortable programming in lists, event handlers and features as opposed to developing in SQL Server, aspx pages in Day 1.

That’s alright, I would rather have my team climb the learning curve for two weeks and see the acceleration in development on the third week onwards. Come the fourth week, I am already seeing a stabilized set of modules as opposed to a project going through so many peer reviews and testing paths.

The stability that the SharePoint platform provides is impressive and towards the end of the project the application you are delivering already carries the stability of SharePoint. Programming in SQL Server and aspx pages from scratch doesn’t provide you with the benefits when using SharePoint.

Key Takeaway

It is so tempting for newbies to create everything in the old SQL Server, ASP.NET combo; in the end, going through the learning curve is far more productive and utilizing MOSS 2007 brings you great stability and quality that would only bring your client smiles and praises.

Remember, do not end up using MOSS 2007 as a landing page only.