This article will display the deployment of using a feature to install code that creates an unpopulated Word Document List. It is part two in a series of articles that will focus on using install techniques and features to perform various actions. When viewed as a whole, these features are designed to stand alone during development, yet they should work together during runtime. As the next part in the series, this demonstration builds upon Part 1 of this series, and is designed to assist newer SharePoint developers in differentiating between the development of a deployable SharePoint feature solution, and the more complex code that may be deployed in the deployment solution.

In Part 1 of this series the goal was to begin the process of developing and deploying a SharePoint feature solution in such a way that it was easy to tell where the act of deployment left off from where the objects that were deployed to perform the intended efforts began. I better appreciate the example code that is broken into articles that clearly differentiate between one technology or section and the next. Deploying a SharePoint Feature and then inserting and displaying code that is delivered via a feature, yet still has its own show and tell criteria is an example of this for me.