Creating a new product: ASP.NET vs SharePoint 2010

Hi, I met an investor who wants a new product to be sold to other companies. We agreed to do this SaaS, but we are discussing three options:

SaaS Product Using Pure ASP.NET Saas Product Using A Huge SharePoint Server Multiple SharePoint Add-ins (Web Parts)

I can’t disclose the product, but it concerns cooperation and involves a lot of interaction between users. For this reason, we have SharePoint as an option, since the user can create web pages (a separate home page) many times if necessary.

Some users do not want SaaS. Thus, it is possible to locate the product locally (to protect its "sensitive" data).

So my question is: which one would you choose from a programming point of view?

(Note: I asked this question on onstartup, and I was asked to ask the technical aspect here)

+5
source share
4 answers

It is difficult to give a definitive answer without knowing the details of the project. However, my general advice is to consider SharePoint only if you plan on using your built-in features and don't need to add a lot of custom ones .

In addition, I recommend that you read the following questions:

+2

, , share point .

+1

, "Sharepoint". Sharepoint Services Microsoft Office Sharepoint Server (MOSS). Sharepoint Services , . , MOSS , , MOSS. MOSS . MOSS WSS (Windows Sharepoint Services).

SaaS, , , .

"Sharepoint ", , , sharepoint . , .

0
source

SharePoint can be the main solution for the enterprise, if users really need RIA and heavy setup, SilverLight will be one of your solutions.

0
source

All Articles