Reputation: 10223
I work on a site where none of us have used TFS before, but we are now having to do so. As a result there are some odd issues that I need to sort out. Where I have an application say APP, when I build my application a new APP.dll is created. I have found that when I build and deploy my application, I have to check in this into source control on TFS 2010. That is fine when I am working on this my myself. But how should I manage this when I am working in a team? Everyone will want to compile their own version of APP and will need a different APP.dll as a result. I am sure there is a simple solution to this. I look forward to finding out what it is.
Upvotes: 1
Views: 297
Reputation: 12668
Do not store your build assemblies (*.dll) in source control, but use the build that is available for you in TFS. The Build system will compile all the sources and drop the created binaries in a folder share. You can use the files in the share to distribute / deploy your application.
You can find more information on the build at http://msdn.microsoft.com/en-us/library/ms181709.aspx
Upvotes: 2