Is mapping your TFS local workspace to C:\ a bad idea? -


my small development team uses tfs2010 in corporate setting, , on team has tfs workspace mapped folder @ root level of c: drive (e.g., c:\tfs). security perspective, bad idea?

i fear person in our organization log onto our pcs , have read access uncompiled code , connection strings in there. considered best practice map tfs workspace subfolder in user account's documents folder, non-administrators can't access?

my fellow teammates' original intent house workspace @ level of c: keep mapped directory name simple, , avoid problems directory , filename limitations in tfs (see error tf14078) complex projects.

thanks!

one thing need careful when mapping tfs collection far under root of drive file name/path name length. file name must less 260 characters , file path must less 248 characters.


Comments

Popular posts from this blog

javascript - Iterate over array and calculate average values of array-parts -

iphone - Using nested NSDictionary with Picker -

objective c - Newbie question -multiple parameters -