CODEWITHSUNDEEP
tfs
Purplegoldfish
Purplegoldfish

Reputation: 5294

What should I store/ Not store in TFS and how?

I'm trying to set up a TFS server for our small dev team, and since this is fairly new to me I have a couple of questions.

1) We are developing ASP.Net websites for internal use (intranet etc), these websites currently are not saved with visual studio solutions, they get saved basically as they are on the server and we just update them using Visual Studio by doing file > open website.

So my first question is should I save these as solutions in TFS? What would the benefit of this be?

Im coming from a background of developing WPF applications and have always seen everything saved with a solution in TFS.

2) What should we store in our TFS repository (and what should we exclude)?

At the moment I am storing source code & Documentation but is it really appropriate to store things like installers for VS plugins / small applications or should this kind of thing all be placed on a server someplace?

Upvotes: 0

Views: 292

Answers (1)

Darin Dimitrov
Darin Dimitrov

Reputation: 1039080

So my first question is should I save these as solutions in TFS? What

Yes, you could create a solution containing the different ASP.NET web applications.

would the benefit of this be?

Your source code will be version controlled

What should we store in our TFS repository

Source code, third party assemblies that your ASP.NET applications might require, script files, basically everything that allow to get your site up and running. Documentation should also be stored along with the project. Same stands for installers (the source code only, not the MSI) if those installers allow to deploy the ASP.NET application on the live servers.

and what should we exclude

Compiled assemblies, but they are automatically excluded by TFS anyway.

Upvotes: 2

Related Questions