http://blogs.msdn.com/marcalt/archive/tags/VSTS+Experience/default.aspxTags: VSTS ExperiencedeCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/marcalt/archive/2008/05/27/where-should-team-documents-be-stored.aspxTue, 27 May 2008 15:41:12 GMT91d46819-8472-40ad-a661-2c78acb4018c:8554809marcalt0http://blogs.msdn.com/marcalt/comments/8554809.aspxhttp://blogs.msdn.com/marcalt/commentrss.aspx?PostID=8554809<p>I really hear this question quite often and the answer is not easy: If you use Team Portal you are able to profit from all SharePoint Collaboration possibilities, but you don't get Versioning/Labeling with the related Source Code. If you store Documents in&#160; Versioncontrol, all NON Developer Roles, not having Team Explorer installed, can't work on them. Both solutions don't really satisfy :-( </p> <p>Sometimes good solutions are so near. With the <a href="http://www.codeplex.com/MigrationSyncToolkit" target="_blank">TFS Migration Toolkit</a> we deliver a reference implementations for syncing data between TFS and WSS. This makes it possible to use best of both worlds and lets you just synch Team Portal Docs into Versioncontrol. Just have a try!</p> <p>Many thanks to Klaus Liebe from <a href="http://www.zuehlke.com" target="_blank">Z&#252;hlke</a> for this tip.</p><img src="http://blogs.msdn.com/aggbug.aspx?PostID=8554809" width="1" height="1">Visual Studio Team SystemVSTS Experience