sharepoint - MOSS vs. traditional ASP.NET -


I am in the process of evaluating MOS (SharePoint) and traditional ASP.NET for my client's site. The site will be available to the client's partners on the Internet. I am interested in the difference between these two approaches from the following perspectives:

  1. How does development perspective evolve? What are the professional and cons of both methods?
  2. Which platform will provide better performance than the display perspective?

So far, we know that much of MOS's features can not be used out-of-the-box, and features will be added through web parts.

The big difference you need to be aware of is licensing on the internet to use an internet mOS License will be required. The actual cost depends on your deal with MS, but this is a significant cost.

We have found that developing ASPNNet pages for SharePage is more expensive to develop. Due to requirements especially for development environment and deployment problems.

From a demonstration perspective, it depends on how you program it. You have more control with ASP.net and therefore, you should be able to get better performance.

Do not use MOSS unless you take advantage of the functionality provided by MOSS.


Comments

Popular posts from this blog

c# - ListView onScroll event -

PHP - get image from byte array -

Linux Terminal Problem with Non-Canonical Terminal I/O app -