SharePoint as a Development Platform

Jeffrey Palermo argue that SharePoint is not a good development platform and implies that working with ASP.NET from the ground up is better.

I would understand the sentiment that SharePoint is not a good development platform especially if you are just starting it out in SharePoint. I remember during my first few months developing in SharePoint, I would always argue with my Architect that modules should instead be done using pure ASP.Net applications. Putting SharePoint at the core of our development only made things slower and difficult. I could remember how a simple treeview would easily work in ASP.NET pages but when placed under the layout folder of SharePoint, things got messy and as such.

My architect would emphasize that using SharePoint speeds development and the level of stability brought in by SharePoint is already added to our modules which makes things easier for us across the entire development lifecycle. For example, using SharePoint lists and storing our data there saves us a lot of time from analysis until the implementation stage because if we used SQL Server tables instead, we would have to plan and allocate budget for designing, testing and implementing stored procedures, triggers, views, etc. Since using custom ASP.NET doesn't give you any starting point of stability, the development process takes twice or thrice the time it takes when SharePoint is used as a development platform.

True enough, after sometime of using SharePoint, I could not imagine development without it. Pure ASP.NET is not good enough and in tune in the fast demands of the industry. Using SharePoint as a development platform make things so much easy and faster.

Jeffrey's main points why he doesn't think SharePoint is a good development tool are as follows:

1. Easy to install

Techticles argue - Installation of SharePoint is not rocket science and it may not be as easy as installing MSN Messenger, installation of SharePoint is not something a developer could not do given tons of documents on this subject.

2. Easy to configure

Techticles argue - Everything can be configured using a browser via the Central Administration page. Most of the links in that page is self-explanatory.

3. Doesn't require perpetual network connectivity

Techticles argue - What does your development environment look like? We have everything in Virtual PC and we have the option to connect online to a centralized SharePoint development platform or work offline.

4. Integrates well with simple tools

Techticles argue - SharePoint is a collaboration platform and integrates well than any other platform or tool out there.

5. Easily extended to make simple tools

Techticles argue - Simple codes can do the trick and so many free web parts, and it's default gallery and architecture already makes creation of simple tools very easy.

6. Must run on Vista/XP, not server OS

Techticles argue - As I said, what does your development environment look like? As mentioned, we have everything in Virtual PC and we have the option to connect online to a centralized SharePoint development platform or work offline.

SharePoint may not come easy out of the box, but putting in a little more time than the ordinary and setting up the right development environment can only bring you loads of productivity.

Leave a Comment