Home/ Questions/Q 726043
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T06:24:25+00:00

I am building a publicly facing website that does the following. Users log in.

  • 0

I am building a publicly facing website that does the following.
Users log in.
And then view a list of their customers.
They click on a customer to view their past purchases, order them, change them etc.
This is not a shopping site by the way.
It is a simple look up tool.

Note that none of the data accessed by the website is in anything other than a SQL database – no office documents. Also, the login does not use users Windows credentials on a VPN or something like that.

Typically I would build this using a standard ASP.NET MVC website.
However the client says they want to use Sharepoint.

As I understand it, Sharepoint is used for workflow and websites that are collaboration tools such as the components you can see here http://www.sharepointhosting.com/sharepoint-features.html

Here are my questions:

  • Would I be right in saying that WSS is completely inappropriate for this task as it comes with an overhead that provides no benefits?

  • If I had to use it, would I need WSS or MOSS?

  • If I had to use it, would I be right in saying the site would consist of :

  • List item

    a) Web Parts

    b) And a custom site layout. How do I create one of these?

Addendum:The book Professional SharePoint 2007 Web Content Management Development looks like a good start

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You can technically use WSS for this task but MOSS has more features aimed at building public facing websites. The publishing infrastructure comes to mind. It has has the CQWP which enables you to build custom interfaces which perform well in SharePoint. With SharePoint there are potentially challenges around scalability. If you know the platform well then doing something like what you have suggested would be a pretty quick task. If you don’t know SharePoint and the underlying system well you could face challenges.

    You do not want to approach building the final application with SharePoint Designer. It has behavior which can cause major problems with scalability. You want to create a SharePoint Solution comprising a number of features which can be easily deployed to SharePoint. Going this route does not alleviate performance problems but you are going to be closer to the right solution. You can package up the custom user interface elements as CQWPs or write Web Parts. I personally prefer to write Web Parts.

    You do the overall site design in a Master Page. Pages within a site are then inheriting from this. If you have MOSS then you can create what are called publishing pages which contain your Web Parts. These are not available in WSS which is why people recommend against it for public websites.

    To decide whether SharePoint (any version) is worth it, you need to find out if they are going to use any of the core features. If everything is going to be custom and you are not going to make use of any workflow or document management features in your deployment then I would stay away. To see whether you want to go further with SharePoint from a development perspective, take a look at the WSS developer labs. I recently ran an intro course at my employer using the materials from that site. They are dated, and need more info on best practices but they provide a quick way for you to dip a toe in the water and decide whether you want to go any further.

    • 0