I am Clueless about source controls

  • Thread starter Thread starter inotyce
  • Start date Start date
  • Tags Tags
    Controls Source
Click For Summary
SUMMARY

The discussion centers on the challenges of using Microsoft Team Foundation Server (TFS) for source control in a virtual machine (VM) environment, which the user finds slow and cumbersome. The user suggests transitioning to Subversion (SVN) using command line or TortoiseSVN for improved performance. However, concerns about client confidentiality regarding software code limit this option. The conversation emphasizes the importance of gathering quantifiable data to support any proposed changes and encourages collaboration with colleagues to assess the team's sentiment towards TFS.

PREREQUISITES
  • Familiarity with Microsoft TFS for source control
  • Understanding of Subversion (SVN) and its command line interface
  • Basic knowledge of virtual machine (VM) environments
  • Ability to gather and analyze performance metrics
NEXT STEPS
  • Research the differences between TFS and SVN, focusing on performance metrics
  • Learn how to use TortoiseSVN for improved source control management
  • Explore techniques for optimizing coding workflows in virtual machines
  • Investigate methods for gathering and presenting quantifiable data on source control efficiency
USEFUL FOR

Software developers, project managers, and IT professionals seeking to improve source control practices and performance in virtual environments.

inotyce
Messages
43
Reaction score
1
My company uses MS TFS for source controlling and I find this really difficult because we have to code on VMs (log on VMs and handle the code in TFS). I would like to make a suggestion to change this into SVN using command line or Tortoise GUI tools. But the client seems not to let publicly seen its software code. As you might know, coding through VMs is odd because it is really slow (GUI graphics drawn and redrawn). Thank you for any ideas.
 
Technology news on Phys.org
Is the issue of TFS vs SVN one of speed or do you just personally find it harder to use? If that's the case (and there are no others on the team who agree) then you might want to simply dedicate some time to getting better with it. If it's an issue where you can gather some quantifiable data to show quicker usage or something like that, then gather it on your own and present it in a coherent and persuasive manner.

Talk to colleagues and supervisors and see if they feel the same as well.
 

Similar threads

  • · Replies 6 ·
Replies
6
Views
5K
Replies
138
Views
27K
  • · Replies 5 ·
Replies
5
Views
3K
  • · Replies 13 ·
Replies
13
Views
6K
Replies
2
Views
3K
Replies
127
Views
23K
  • · Replies 13 ·
Replies
13
Views
4K
  • · Replies 1 ·
Replies
1
Views
3K
  • · Replies 12 ·
Replies
12
Views
3K