Two project templates have been created and are available for developers to download and use with Visual Studio 2005. The templates provide the basic Web application project configuration for the presentation and business tiers, and eliminates the majority of the start-up coding necessary to begin developing an application. While the project templates contain much of the code outlined in the Application Configuration section, it is recommended that you read the section in its entirity to understand the logic and reasoning behind the choices made. To add the project templates to Visual Studio 2005, complete the following steps:

1. On the Visual Studio 2005 toolbar, click on Tools
2. Select Options...
3. Click on Projects and Solutions
4. In the box below Visual studio user project templates location: enter \\dotnettest01\ProjectTemplates
5. Click on OK

Once the project templates have been added to Visual Studio 2005, create the presentation and business tiers for your Web application project using the following steps:

1. Select File > New > Project...
2. Under the Project types listing on the left, select Visual C#
3. Click on UCS - ASP.NET Web Application under the My Templates heading
4. Name the presentation tier using the Pascal capitalization standard
   For example: AdminConsole
5. Click on OK
6. After creating the presentation tier, add the business tier by right clicking on the solution name and select Add > New Project...
7. Click on UCS - Class library under the My Templates heading
8. Name the business tier using the Pascal capitalization and Uppercase standards
   For example: BSU.UCS.AdminConsole
9. Click on OK
10. Note: The presentation tier contains an invalid reference to the BSU.UCS.ASPDotNetTemplate project. You will need to remove this reference and add a new project reference to the class library you created in the step above.

Using these standards will create the necessary folder structure needed to follow the Microsoft Visual SourceSafe naming conventions. There are several benefits gained by using the aforementioned project templates. First, the templates are stored in a common area available to all developersWhen a new template is deployed to the server by copying the ZIP file to the share, all developers immediately have access to it from within Visual Studio. After the initial deployment, changes to the template can be made in one place instead of having to be deployed to each developer's workstation. In addition, because the template is used as a true template, it remains unchanged and can be used repeatedly to create new projects. This is a vast improvement over the old "copy and paste" approach where one developer would create a file or project and hand it off to another. Without careful management, the original was quickly lost and modified with no chance to get back to a known good configuration.