Content Types and WSS API

The WSS api is a powerful beast but as the old saying goes with great power comes great responsibility.

When you are adding content types note that they are just groupings of either existing or created fields. Now in a development lifecycle I am sure you will create a content type deploy and then find that you want to redeploy it with some additional features.

If the above scenario is the case then a word of warning.... if you don't delete the constituent fields before adding the augmented content type then you are going to be adding loads of fields again to the site and when it comes to using the content type it may look as if Sharepoint has not picked up your changes. However if Sharepoint has fifty fax number fields then how does it now which one to use?

Although this sounds obvious and as a new comer to Sharepoint this blog represents a newbie coding journey with the product you must always remember check for the existence of an object and delete it before redeploying it.