Your SlideShare is downloading. ×
0
Source control best practices
Source control best practices
Source control best practices
Source control best practices
Source control best practices
Source control best practices
Source control best practices
Source control best practices
Source control best practices
Source control best practices
Source control best practices
Source control best practices
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Source control best practices

2,029

Published on

Discussion about common problems and solutions with source control usage. …

Discussion about common problems and solutions with source control usage.
Overview of the new Visual Studio 2010 Source Control features

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
2,029
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
17
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. www.orbitone.com Raas van Gaverestraat 83 B-9000 GENT, BELGIUM E-mail info@orbitone.com Website www.orbitone.com Tel. +32 9 330 15 00 VAT BE 456.457.353 Bank 442-7059001-50 (KBC) Presenter: Mel Gerats 7 April, 2010 Source Control Best Practices
  • 2. 7 April, 2010 Source Control Best Practices2 In this presentation Discuss source control standards Discuss deployment standards Overview of Team Foundation Server 2010 features
  • 3. 7 April, 2010 Source Control Best Practices3 Goals Have Source Control standards Have Deployment standards Improve versioning Improve deployability Reduce manual actions
  • 4. 7 April, 2010 Source Control Best Practices4 Current situation: Source Control Trunk Branches
  • 5. 7 April, 2010 Source Control Best Practices5 Current situation: Source Control Work is done on the trunk (most of the time) Branches are used as back-up
  • 6. 7 April, 2010 Source Control Best Practices6 Current situation: Deployment Copy paste “publish” to staging Always manual actions Sql scripts
  • 7. 7 April, 2010 Source Control Best Practices7 Problems Builds get broken Not always a deployable version available Not always possible to check in stuff If there are multiple versions which one to deploy?
  • 8. 7 April, 2010 Source Control Best Practices8 What do we want Automate everything One Click deploy Use more TFS features! Always be able to deploy changes Never break the build
  • 9. 7 April, 2010 Source Control Best Practices9 Demo Time Demo Team Foundation Server 2010
  • 10. 7 April, 2010 Source Control Best Practices10 What will we do? Create clear guidelines for source control usage based on Visual Studio TFS Branching Guide 2010 Start using Team Foundation Server 2010 Start really using build automation / msdeploy
  • 11. 7 April, 2010 Source Control Best Practices11 Challenges Nunit / NCover automation Overview of all builds like CruiseControl
  • 12. 7 April, 2010 Source Control Best Practices12 Resources Team Foundation Server 2010 related questions on Stackoverflow Visual Studio TFS Branching Guide 2010 Team Foundation Server Team Blog (lots of info there!) Team System Development Center

×