Hans Rasmussen » WSS

Enable AJAX Support in SharePoint,WSS, MOSS 2007

Hans Rasmussen — Fri, 19 Feb 2010 23:45:50 +0000

Microsoft suggests the following changes to web.config for your SharePoint installation if you want to enable AJAX functionality. http://msdn.microsoft.com/en-us/library/bb861898.aspx

However it is easier to use this Feature and activate it through SharePoint central administration. Benefits are that it both creates the changes when you activate and undo the changes when you deactivate. And from a deployment perspective it is more “clean”.

http://www.moss2007.be/blogs/vandest/Documents/SPWebConfig_XML.zip

Avoid unghosting by avoiding SharePoint Designer

Hans Rasmussen — Fri, 19 Feb 2010 23:36:35 +0000

YES, SharePoint Designer serves a purpose. However think for yourself a bit before you decide to make your changes to a page with SharePoint Designer. The minute you made changes to a page it is unghosted and saved in the database. If you provision these changes to new web sites you will struggle if you need to make new changes to the page. The changes will not cascade and you’ll need to update each site manually and there can be MANY of them. Making a feature that will help you deploy design changes is one solution because you can automate the process with stsadm commands. However I also found this little interesting approach I’d like to share http://www.cleverworkarounds.com/2008/02/28/more-sharepoint-branding-customisation-using-javascript-part-3/ which allows you to make changes but still keep the pages ghosted.

Sharepoint Workflow Feature.xml and Workflow.xml for WSS 3.0 & MOSS 2007

Hans Rasmussen — Fri, 19 Feb 2010 23:26:30 +0000

It seems like when you create workflows in Visual Studio and deploys them to SharePoint you have to consider the environment you are deploying them to. In the feature.xml the ReceiverAssembly and ReceiverClass are specified if you want to go for the MOSS 2007 deployment. Remove the lines in bold if you need to deploy them to WSS 3.0 installation.

Title=”Thenameofyourfeature”

Description=”The description of your feature”

Version=”12.0.0.0″

Scope=”Site”

ReceiverAssembly=”Microsoft.Office.Workflow.Feature, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” xmlns=”http://schemas.microsoft.com/sharepoint/“>

ReceiverClass=”Microsoft.Office.Workflow.Feature.WorkflowFeatureReceiver”

Your workflow.xml however can look the same regardless of deployment

http://schemas.microsoft.com/sharepoint/“>

Name=”Nameofyourworkflow”

Description=”Description of your workflow”

Id=”Workflow-GUID-Goes-Here”

CodeBesideClass=”Projectname.Classname”

CodeBesideAssembly=”Projectname.Classname, Version=1.0.0.0, Culture=neutral, PublicKeyToken=TokenForYourSignedDll”>

_layouts/WrkStat.aspx

Comparing different editions of SharePoint including a WSS 3.0 only installation

Hans Rasmussen — Fri, 19 Feb 2010 23:16:04 +0000

A good to have link is one where you could quickly find the differences between the editions of SharePoint and even more important the differences between a SharePoint and a WSS 3.0 install.

http://office.microsoft.com/en-us/sharepointtechnology/FX101758691033.aspx?ofcresset=1