Joseph Fluckiger's Blog

  SUSHI Version 3.4 includes the following improvements: Important Improvement : Security Report: The logic for looking up Active Directory Groups that a User is a member of has been improved so that users with read-only privileges to Active Directory can successfully query group membership. Delete old documents: This feature is now asynchronous and includes a cancel so that the action can be canceled after it has started but before it is finished. This is useful when archiving a large number of documents. Bulk List Creation: Tips for bulk deleting lists and renaming list URLs added.

  Microsoft has just released a memory leak checker for SharePoint code . Not sure if all your SPWeb and SPSite objects have been properly disposed? Use this tool to discover which lines of your code are not properly disposing of those objects.   Each SPWeb and SPSite object takes 1-2 megs of unmanaged memory. So no properly disposing of them causes major memory leaks. However, (this is important) if you dispose of a SPSite object that you get from SPContext.Current, you will crash your SharePoint site. So having a tool that you can run to definitively determine if your production code is good, is a big help.   -Joseph

I am pleased to announce the release of SUSHI, version 3.3 .  About SharePoint SUSHI.     New Features, Improvements and Bug Fixes Delete old documents: Copy documents older than a specified date to an archive folder and then delete them from SharePoint. Security Report: User can type and also select from the list. As the user types, the name of the SharePoint User is found. Awesome new screenshot on the Codeplex SUSHI home page. :)   I would like to thank the community for all the great feedback. I am working to incorporate your ideas as quickly as possible. Knowing which features you are using is helpful to know which features to prioritize.   Thank you to all who have donated to SUSHI. This is always a very big help. You are welcome to make a small donation to SUSHI .   -Joseph Fluckiger

Doing a scripted install of MOSS can save a lot of time, and can also ensure that your installs are consistent. Below is a sample scripted install of MOSS. (I have changed sensitive information like passwords, emails and URLS.) I have found that it works best to execute these commands one at a time, rather than as a single script. If you are unlike me and never make mistakes, then feel free to run them all at once. Another added benefit is that this provides very nice documentation of your install for future posterity. And for someone who understands windows scripts can teach quite effectively what it takes to install MOSS, surely much more effectively than the beastly 30 page install instructions on MSDN. One of my favorite benefits of a scripted install is that you can choose a name for the Central admin content database instead of getting stuck with the ugly content database name the includes a Guid. Some of the setproperty statements at the end are optional, but they give you...