.net - To SharePoint Or Not (as a foundation for application development)(vs ASP.NET) -


I have a POV that you should use SharePoint only for application development under these conditions.

1) Application uses documents and these documents require some type of functionality which is very well (coordination with search / indexing, outlook, etc ... etc) if SharePoint If you want a document bucket and a list then ASP.NET or ASP.NET MVC.

2) Applications should use workflow or custom workflow. No workflow, then I will look at ASP.NET or ASP.NET MVC.

3) The company must dedicate at least 1 full time developer to SharePoint. Developer's 1/2 or 1/3 Not To SharePoint Development Properly You Need Commitment And Focus You Should Drink Qualified Support If you are not ready for expertise in SharePoint, but are only willing to tamper with, the resultant solution Horrible (IMHO) are better than you can dedicate to two developers or team (Aidability / Maintenance / Specialization / Expertise).

So what do you think?

Note: I think all Microsoft stores should use SharePoint's out-the-box features if their company has changed their form of shareholding architecture to the Exchange. Is added in After I was sitting in the SP Workshop, I came to know that SharePoint workflow only applies only to the sharepoint based on the list of items I & Nbsp;

UPDATE Therefore, if your workflow does not use SharePoint list items, you should probably look at the .NET Workflow Foundation or some custom. Consider this instead of my # 2 item.

I will agree. Currently SharePoint (Mass 2007 / WSS 3.0) makes custom Dev a very painful and slow process. I disagree with only one point workflow part. In my opinion, workflow in SharePoint is almost useless, and it should be avoided. If you are going to workflow, go for Massransat K2: BlackPear or Open Source Free Option.


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 -