…or don't detach your content db.

In server farms that have a large number of sites, installing a software update with the content databases attached can result in too much downtime. To minimize downtime, Microsoft recommends that you perform the additional step of detaching the content databases.
But this time, don't do that for the last August cumulative update.

More details here http://blogs.technet.com/stefan_gossner/

The problem is being investigated

The Sharepoint Pattern & Practice group recently released the August version of Sharepoint Guidance and it’s worth reading!

A common question in the sharepoint newsgroups is “shoud I use a Sharepoint list or the database ?”.

Michael Washam (MSFT) announced today in the sharepoint newsgroups the last release of the Visual Studio Extensions for Sharepoint 1.3 CTP.

I’ve used this tool since its first release in 2007, but the upgrade from 1.2 to 1.3 provides major improvements and is (now) really usable.

This is probably the last release of the venerable VSeWSS before Sharepoint 2010 and the Sharepoint developement tools that will be part of Visual Studio 2010.

By the way if you watched the Sharepoint 2010 sneak peek video, you probably noticed that VSeWSS projects can be imported in Visual Studio 2010.

New features of VseWSS 1.3:

• The extensions now install on x64 bit OS. Visual Studio 2008 and SharePoint must be already installed.
• Command Line Build option for TFS and MSBuild integration
• Separate WSP Package and Retract commands. You can now build the WSP without deploying it
• SPSolGen to Support Exporting from Content Management Publishing Sites
• New Item Template for RootFiles Deployment
• Automatically Remove conflicting existing features on development SharePoint server
• WSP View New Feature Dialog Improvements: scope, receiver checkbox, element checkbox
• WSP View can now be used to merge features and it blocks site features being merged into web features
• Allow adding separate binary files such as Workflow assemblies
• Some refactoring allowing for Web Part renaming and removing lines from feature.xml Item Removed
• Allow selection of GAC or BIN deployment for Web Part Project not including CAS generation
• Increase visibility of hidden features that VSeWSS creates
• Add fast update deploy for DLL only or file only changes to solutions
• Numerous Bug Fixes and improvements to error messages

That is a frequent question I have to answer…This seems to be a common issue.

In Central Administration, Application management, you will find the following option:

When you selected it, you will get this :

In the setting “Enable user-defined workflows for this site”, select “No” (you will notice other interesting options for internal or external users who don’t have site access, but who need to take part of workflows).

Now, if you open one of the site of the web application with Sharepoint Designer 2007, when you try to create a End User workflow

You will get this warning :

Don’t forget ; more details here.

Don’t forget it, that’s the place to be if you really want to learn something about Sharepoint 2010. Hope to see you there…

I guess this will help many people in the Sharepoint community (according to some messages in the Sharepoint newsgroups…)

After working on it this week-end, I’ve decided that the quality was good. Now it’s time to move it to Sharepoint 2010; more details after the Sharepoint Conference in Las Vegas. Enjoy !