Wrox Programmer Forums
Go Back   Wrox Programmer Forums > SharePoint > SharePoint Development
SharePoint Development Programming and development for SharePoint Portal Server and Windows SharePoint Services
Welcome to the p2p.wrox.com Forums.

You are currently viewing the SharePoint Development section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
Old April 1st, 2009, 07:55 AM
Registered User
Join Date: Apr 2009
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default When to use features and when not to?

Hi all,

I've just begun learning sharepoint and there's quite a few qestions that i have. The first are to do with features, and when they should be used, from my reading i understand that there are advantages to using features to deploy sharepoint components, however i'm wondering is there a point where the customization you are making is so trivial that it's not worth using a feature i.e. just use the UI? For example if you have to add a single site column? Where do you draw the line, if you use features for every customization you make you would end up with an unmanageable quantity of features?

Another feature question, should each feature contain only components that are related or can you package unrelated components into the same feature? The reason i ask is say you are working on a project that contains a set of content types and a list. Obviously the content types have been created with the intention of being used by other lists in the future. So if the content types and lists are packaged within the same feature and in the future you decide you no longer need the list and want to deactivate it, the content types are also deactivated and unusable by other sharepoint components? Basically i would like to know if the general consensus is to encapsulate single logical units into seperate features to avoid the above sitaution?

Last edited by chris123; April 1st, 2009 at 07:57 AM..

Similar Threads
Thread Thread Starter Forum Replies Last Post
Rich Text Features austinf Pro JSP 1 December 20th, 2006 03:47 AM
Various security features... rupen Javascript How-To 0 September 20th, 2006 05:04 AM
Forum Features and Limitations englere BOOK: ASP.NET Website Programming Problem-Design-Solution 2 March 10th, 2006 12:37 PM

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.