Visual Studio Team System User Education

Yeah, yeah... but I want to move portions of my TFS to new machines! How the heck can I do it?
Here's...

Would be very nice if you have a document of "how to install TFS in a server that has SharePoint already installed!"

There is now draft documentation available that describes how to move a TFS server.Moving Your Team Foundation...

Quite a few people sent me e-mail recently asking for documentation that supports a number...

Rob Caron blogs about Jack Greenfield on Software Factories and DSLs.

The Software Lifecycle blog...

Given that any of these changes are complex and not all environments are the same, I think it would be great if there was a wizard of some kind that would assist in making changes like this.

What do you do if you cannot remember the reporting services key password and you are halfway through the move? (move to different hardware {actually reinstall on same hardware}).  I have continued with all other aspects of the move but have still got the reporting app pool stopped until I know the best way to proceed.  I know there is documentation about reentering the encrypted information (mainly connection strings and user accounts).  Should I do that and then continue with the reporting move, or will changing the encrypted info stuff it up even more?

What about a procedure to move a Team Project from one TFS to another??

Hi,
   I have TFS RC installed currently. Is it possible to have a new server with TFS RTM installed and then move the backed up data from my original RC server put on the new RTM server? If this is possible, then it looks like the best way to upgrade to RTM from RC for me without disrupting development.

Please let me know.

Just wanted to reemphasize the need for some way to move a project from one Team Foundation Server to another.  

We currently just detach the project from source control and add it to the new server manually, then export the work items to excel and import them to the new project (painful and does not appear to preserve work item links and associations).  This also, of course,  results in a loss of history on the project.

I noticed a tool that will transport work items between servers but it appears to not support the RTM.  Even this would be very helpful.

I am not certain how common this scenario is but for us it has occurred several times as we switch servers to balance load, or simply to separate dissimilar projects (we have both a public TFS server for projects that require client access for review, and private a server for internal development).

Should we expect any official utilities to come about that might ease this process?

Slightly off-topic but in a similar vein.

We have an urgent need to add code (many Solution files) from the source control in one Team Project with the code in another Team Project located offshore.  We will also need to merge code that has been worked on at both sites.

Deleting the .vssscc and .vspscc files alone doesn't work as they are recreated whenever the .sln file is opened in VS.  This then prohibits me from "adding" the solution to the desired target source control.

Is there any way other than manually editing the IP addresses and Paths in the Solution files in a text editor?

Answer: Could you clarify?  It sounds like you’re trying to find a solution for branching and merging two different source trees from different projects on different Team Foundation Server deployments (one in the home office, one offshore).  Or are you using Team Foundation Server Proxy and a single source control server? 

 

Thanks,

-=Susan

 

 

How do I move a work item, let's say a task, that was started in Project A but I want it to live in Project B?  One Team Server deployment.

 VSTSUE says:

Unfortunately, moving work items from one project to another isn't supported.

What's the going method for closing out projects? We have new projects for each new software feature - but folding all the work items, docs, etc. is a fairly manual process. Is Microsoft addressing the problem of not being able to "roll up" projects into a parent project once the separate project is complete?

Similar to the post by Keith.  We have two separate TFS environments.  There is a primary TFS environment that controls what is deployed to production.  Most development takes place in this environment.  However, we also have a second team with their own TFS environment who will also be making changes from time to time.  The developers on the second team do not have access to the primary development environment.

We are looking for a simple and reliable method for comparing and merging changes from the second environment into the primary environment for final testing and deployment.  Any suggestions?

Thanks!