I figured this article would serve as somewhat of a conclusion to my other 2 posts about this subject. I don’t have massive amounts of SharePoint experience, but I’m sure that I’ll come across it some more in the future. For now this series will come to a conclusion, but I’m sure that a part IV will be made
What annoys me most about SharePoint development, is the fact that there is no such thing as an SDK and the documentation about performing certain tasks is hardly in existance. Yes, you can work with the SharePoint Designer, which is basically FrontPage for SharePoint but my experience has tought me to avoid that tool as much as possible. Documentation on tasks that I think a SharePoint developer comes across quite often in a custom implementation is hard to find on official Microsoft/SharePoint sources but can be found on blogs of other developers that struggeled with the same problem. Official documentation is simply poor in my opinion.
My general feeling with SharePoint is that I’m constantly trying to find a workaround for a problem that shouldn’t be all that difficult to solve. Out-of-the-box SharePoint is easy to work with, but customization (from my experience) simply isn’t. So far I have yet to find an installation that comes close to the Holy Grail some people call it.
Tweet er over
RSS Feed
Print deze post
83x bekeken
Working with all-in-one machines like MOSS is always “constantly trying to find a workaround for a problem that shouldn’t be all that difficult to solve”. It is never flexible enough.
Just switch to a regular ASP.NET, or, better, ASP.NET MVC, to re-gain control on what you’re developing.
Thanks for the information. For me it is the helpful information. I did not know about it