“An unexpected error has occurred”: the sharepoint developer nightmare

If you are developing with WSS/MOSS, this is a known message. A lot of unexpected errors are displayed simply as "An unexpected error has occurred.". Some of them you can debug in the sharepoint log files, some of them you can find details in the event log, and some... you can't find anything... those are …

Best Practices for Speeding Up Your Web Site

This is an article with a lot of common scense and doesn't apply directly to WSS/MOSS but to all web sites. A must read. You can find it here: Exceptional Performance : Best Practices for Speeding Up Your Web Site. Here is a snipet: (...)The Exceptional Performance team has identified a number of best practices …

this.Dispose();

A couple of days ago a fellow Sharepointer entered the non existence phase. In his memory I leave a profound scream: ask for help if you need it; Always be there for those who do so! RIP Miguel...

Getting rid of a broken webpart

Sometimes (more frequently than I could wish for) a webpart brakes a page and stops you from editing any further. If you find yourseft in such a situation, add the string "?contents=1" as in http://mysite/somepage.aspx?contents=1. This will lead you to the webpart deactivation page where you simply disable/remove the broken webpart.