Here’s our MOSS story:
http://pro-thoughts.blogspot.com/2008/01/why-i-hate-ms-sharepoint.html

The break even point for just making a custom (web)application is reached much sooner then everybody thinks. When implemented, I think the custom application has a great advantage. It is just easier to add/change new (complex/not sharepoint standard) functionality.

Also the fantastic sharepoint websites can suck the life out of any server. THAT’S WHAT YOU DON’T WANT!

1) It stores and consumes bits and bytes were even (Lord) Bill Gates didn’t find them yet!

2) For some weird reason it performs like shit, maybe it has something to do with those bits and bytes.

Actually the people who want sharepoint as a functionality aren’t stupid, all together with MS Dynamics. But all those tools in Dynamics and sharepoint etc just won’t work perfectly together plug and play. And maintenance is expansive, because you have to train someone at age of 5. Never teach the child math. Teach him to write an _UnderScore_ before every word.

Sharepoint Olé!

Why would you choose not to have a form of referential integrity in your lists?

In my opinion having a different internal and display name just adds unnecessary overhead to your C#/VB.NET code. If I were to give a piece of code that has some columns referencing to an internal name to another developer he would probably search for hours to eventually find out that he’s been searching for the wrong name. I can imagine the code becoming a mess when you are constantly using internal names that you can’t find in SharePoint because they’ve been renamed.

Also, as Oppie noted, if I would want to retrieve the (reserved!) “Name” field, I need to make different code for an English or a Dutch installation. Retrieving the “Name” column simply won’t work in the Dutch version. It’s strange to me that what you could call the data layer in SharePoint is language dependant.

Isn’t that at least somewhat weird?

You could get Field using GUID too.

Think about scenarios where you have a C# code in your web part to display details where you are getting a field called “Product” based on which your entire code does some rendering. You deploy the solution for the customer. Now you have user using your wondrful web part but at same time you have contribute users who feel the need to call field name something else (let’s say Business_Prod) Now if display name was always used to retrieve Field then your C# would have failed.

I do understand there are lot of grips about SharePoint i myself have a list of them.. but not this 2nd part, Share point list never maintains referential integrity between 2 lists. If you need to do that, you need to write custom even receiver like you have to write Triggers in Database.

Nah just kiddin, just talk to our SharePoint boss im sure he will listen…