I have a predicament in a project I'm currently involved in. Due to the nature of the project and the customer, I will not be able to disclose any detailed information regarding the actual project, but I will try to be as specific as possible anyway.
- The site will feature regular logon (forms)
- The site will contain some lists where the content is either retrieved from local database or backoffice system
- The site needs to be able to be branded on a customer basis.
- Every user will have alot of profile-information connected to it, which needs to be kept in sync with backoffice on a scheduled basis (every night). This information needs to be sortable and searchable, as well as editable in SharePoint.
- There will be publishing of news that needs to be targeted to specific audiences (groups of users)
- The general design of the site needs to be changed from the standard "SharePoint look-and-feel"
These are in general some of the main points of the application, and my question is then:
Would you consider this to be a "typical" SharePoint project, or will it be beneficial to roll-our-own? (cost of licensing does not have to be considered into this question).
I really hope you can provide me with some good pros/cons here.
The decision was made to go for SharePoint 2010 as the platform for this project. During analysis we (SharePoint experts were included in the analysis) concluded that there was little or no benefits with SharePoint 2010 on the mentioned points, and we could probably just as well have gone with an ASP.NET MVC3 app. But, when a few future feature-requests were put on the table the score shifted slightly over to SP, and since the customer has a policy that leans towards SharePoint 2010, the choice was simple.
Thanks for all your input! All the points in the answers were taken into consideration when presenting the analysis to the customer.