This documentation is archived and is not being maintained.

Application Creation Process With Enterprise Templates

Visual Studio .NET 2003

After you have customized an Enterprise Template and made it available to your development team, development work can begin. This work progresses through the following phases:

  1. The team begins work by instantiating the new solution from the Enterprise Template prototype files (see Creating an Enterprise Application's Initial Structure). Developers are guided overtly by reading the Help screens and less overtly by policy.
    Note   Once developers have instantiated a project from a template, any changes you make to the template do not affect the existing project. You can make changes to the structure of the template, but those changes will only affect future projects — that is, projects that will be instantiated from the template after you make changes.
  2. If you determine that the policy you specified is incomplete or incorrect, you can correct it. Author the policy file as usual, adhering to the TDL schema, and make the edited policy file available once again to the developers. To read more about changing policy, see Authoring Policy Files in Template Description Language, Adding Policy to an Existing Application, and Managing Policy Versions. To read more about using policy while the application is being developed, see The Use of Policy During Development Work, below.
  3. Similarly, you can add, change, or delete Help files for use in an ongoing project. After you make these changes, developers must close and reopen Visual Studio to see the new Help screens. See Providing Custom Help for Enterprise Templates.

Use of Policy During Development Work

When a developer violates policy, the only effect is that a policy reminder is placed in the Task List of the Visual Studio IDE for that developer. The presence of one or more policy reminders does not keep the developer from building the project or checking components into a source-control system.

Enforcing compliance with policy is therefore a matter of understanding of how your team works and communicates. For example, you might want to state that developers, as part of the code-review process, have no pending policy reminders.

Whenever a project is opened, Visual Studio .NET re-analyzes it for policy compliance. This means that if a developer uses another text editor to edit a source file that is part of a Visual Studio .NET project to which policy is applied, any policy violations introduced into that source file will be reported and displayed when the file is opened using the Visual Studio IDE. (Architects should make sure that code reviews are conducted using the Visual Studio IDE, or at least that the Task List be inspected at some point during the code review.)

Architects can also add specific content to Task Lists, such as assignments. For example, architects can add a "TODO:" comment to the project item templates to let developers know where to add their work. These TODO items appear in the Task List. For more information, see Creating Task Reminders.

See Also

General Templates Must Be Customized | Distributing Policy, Prototypes, and Custom Help | Adding Policy to an Existing Application