I would like to know what kind of applications are suitable to be developed on top of Sharepoint 2010 and which should not be built on to of it. So when to embrace/avoid Sharepoint 2010 as a development platform for new web applications.

I'm an Asp.net MVC (former web forms) developer and would like to know if usual multi-page semi complex web applications (intra/extra-net) should be built on top of Sharepoint 2010 and why (if yes or if no).

Additional explanation

I would like to determine whether Sharepoint 2010 is suitable for an enterprise-level application with complex functionality, lots of input/manage data screens, processor intensive business processes etc. I see Sharepoint more of a platform as is with minor part-sized extensions. And not as a complete complex application platform. I just don't know whether I'm right or not...

closed as primarily opinion-based by HopelessN00b Jan 21 '15 at 10:34

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.

locked by HopelessN00b Jan 21 '15 at 10:35

This question exists because it has historical significance, but it is not considered a good, on-topic question for this site so please do not use it as evidence that you can ask similar questions here. This question and its answers are frozen and cannot be changed. See the help center for guidance on writing a good question.

Read more about locked posts here.

  • I see where you're headed but probably too hypothetical and open-ended to get a truly useful answer. Or maybe I'm just not smart enough to think of one. – icky3000 May 6 '10 at 21:39
  • @icky2000 check my additional explanation. It may give some more firm information that you can easily answer. – Robert Koritnik May 7 '10 at 18:29

SharePoint 2010 is definitely suitable for enterprise level applications, but with some caveats.

To achieve your complex functionality, you will have to build custom webparts which could actually take more effort than your traditional ASP.NET application.

However the benefit of doing this is to leverage SharePoint's access control. (which is pretty good)

If access control is not a huge concern, and you do not require integration with any other SharePoint feature then I would be inclined to go back to ASP.NET.

In terms of data entry, consider the 'Forms Server' facility of SharePoint:


Finally some organizations I have seen like the idea of a 'single' platform. This is usually a good business driver for just using SharePoint, regardless of the technical advantages/disadvantages.

Not the answer you're looking for? Browse other questions tagged or ask your own question.