Can an entire process template be imported to an existing team project

Pretty much the name says it all. Is there a mechanism by which an entire process template can be imported into an existing team project?
[137 byte] By [MichaelRuminer] at [2008-2-24]
# 1
You can upload entire template using Admin UI or use ProcessTemplateManager.exe, or IProcessTemplates interface method as in http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=454833&SiteID=1 . When you say "into an existing project", do you mean updating the current types and data with new template? You can update the workitem types individually by running witimport, but not overwrite existing project with new template data.
NarenDatha-MSFT at 2007-8-30 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - Process Templates...
# 2

Yes, I meant a wholesale replacement of one template on an existing team project with another template. Not a WITimport etc. So that provided my answer- No.

Thanks.

MichaelRuminer at 2007-8-30 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - Process Templates...
# 3
If I wished to do such a wholesale replacement I think the best approach would be to just branch using the new template.
MichaelRuminer at 2007-8-30 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - Process Templates...
# 4

Yes, you'd have to create a new project based on the new template. You cannot replace the process template for an existing project (except for updating and adding work item type definitions).

Thanks!

YogitaManghnani at 2007-8-30 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - Process Templates...
# 5
I would like to clarify what a template means to a project after a project is created. A project is simply an instantation of a template and is free to be modified later on. After a project is created, all parts of it can be modified (work item types, documents, reports, CSS hierarchy, any 3rd party elements, etc) to an extent that it no longer resembles the template it was created from. That is why no association between the template and the project is kept in the project properties. Any effort to relate back to the original template would be futile for this reason. Think of a template as a starting point, not a fully defined project by itself.

So as Yogita suggested, your best option is to create a new project from your new/modified template and migrate in the work items, documents, source control, etc as needed.

-Ravi

RaviTerala at 2007-8-30 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - Process Templates...
# 6
That makes perfect sense. That's a great way to think of it. The template is just that 'A template', 'A Factory' the produced team project incarnation could be any form after the fact.
MichaelRuminer at 2007-8-30 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - Process Templates...

Visual Studio Team System

Site Classified