I'm creating a openly facing website that does the next. Customers sign in. After which view a listing of the clients. They click a person to see their past purchases, order them, change them etc. This isn't a shopping site incidentally. It's a simple lookup tool.

Observe that no data utilized through the website is within anything apart from a SQL database - no office documents. Also, the login doesn't use customers Home windows qualifications on the VPN or something like that like this.

Typically I'd build this utilizing a standard ASP.Internet MVC website. Nevertheless the client states they would like to use Sharepoint.

When I comprehend it, Sharepoint can be used for workflow and websites which are collaboration tools like the components you can observe here http://world wide web.sharepointhosting.com/sharepoint-features.html

Listed here are my questions:

  • Would I be in stating that WSS is totally inappropriate with this task as it has an overhead providing you with no benefits?

  • Basically needed to utilize it, would I want WSS or MOSS?

  • Basically needed to utilize it, would I be in saying the website would contain :

  • List item

    a) Web Parts

    b) Along with a custom site layout. How do you create one of these simple?

Addendum:It Professional SharePoint 2007 Content Management Development appears like an excellent start

1.) To be sure that SharePoint could be quite inappropriate with this task. A couple of reasons:

  • It is 1000's of dollars to license SharePoint to be used around the open Internet
  • SharePoint uses lots of assets (SQL Server, IIS, Active Directory...) which are unnecessarily demanding for the task
  • SP provides you with hardly any versatility to build up an answer inside your way -- it may sound like you should produce a database-connected Web Part in ASP.Internet anyway (to ensure that might be entirely separate from SP)

SharePoint has it's place--it may be remarkably useful like a company's internal document management, intranet, and workflow/approval system--but it's not perfect for custom code nor Internet use.

2.) In my opinion MOSS could be needed for the net license (as with the hyperlink above).

3.) SP development isn't like typical relation database systems (for instance, it uses flat, unnormalized tables). In case your SQL matched up the SharePoint thought process, you may have the ability to connect with your database being an exterior List using SharePoint Designer. Much more likely you should use Visual Studio to produce a custom Web Part in ASP.Internet.

Hopefully this'll be considered a couple of reasonable arguments will assist the customer observe how SharePoint is inappropriate for that task... Actually, I expect only the first point (the price of certification) will turn them.