Developing with Source Code Control - Best Practices Part 2

re: Developing with Source Code Control - Best Practices Part 2

PeterRitchie — Wed, 24 Jun 2009 00:40:36 GMT

@Adam D. I've never actually had a problem merging designer code. But, I know some designers have had issues with merging--some don't generate files that are merge friendly.

re: Developing with Source Code Control - Best Practices Part 2

Adam D. — Tue, 23 Jun 2009 22:05:38 GMT

Another point is to make sure you do not merge designer code. Some designers expect certain things in certain order. No matter what the merging tool, it will not know what the designer expects. Last observable failure due to this was the WinForms designer of VS2005. Haven't dared this yet on VS2008/2010.

re: Developing with Source Code Control - Best Practices Part 2

TD — Mon, 16 Mar 2009 22:05:24 GMT

I used Subversion at my last job, but SourceSafe at my current contract. It's very painful. How I miss my Subversion.

Developing with Source Code Control - Best Practices Part 2 - Peter Ritchie's MVP Blog

Mon, 16 Mar 2009 11:27:48 GMT

DotNetBurner.com - news and articles about .net DotNetBurner

re: Developing with Source Code Control - Best Practices Part 2

Hyacinth Broadchest — Sun, 15 Mar 2009 01:02:39 GMT

Really useful article, Peter. We have long had religious wars about when one hould check in. What you say here has moved us along a bit. It makes sense and is based on experience and everyone has been able to find it within themselves to take it on-board. Many thanks,

Hyacinth.

re: Developing with Source Code Control - Best Practices Part 2

PeterRitchie — Sat, 14 Mar 2009 21:28:11 GMT

@Daniel. Actually, you made me realize that I wasn't clear in my statement. By generated code, I mean code that is generated as part of the/a build process. One-time generation of code such as that usually generated by Visual Studio wizards should be checked into SCC as long as it never gets regularly generated.

re: Developing with Source Code Control - Best Practices Part 2

Daniel — Sat, 14 Mar 2009 15:20:01 GMT

Curious how you exclude VS-generated code. I've had issues with this- for example with datasets or L2S generated code. Both will prompt a checkout even if you just open the file to look at. Sometimes ASP.NET designer generated code will do the same thing.

Developing with Source Code Control - Best Practices Part 2 - Peter Ritchie's MVP Blog

DotNetShoutout — Thu, 12 Mar 2009 22:05:38 GMT

Thank you for submitting this cool story - Trackback from DotNetShoutout

Dew Drop - March 12, 2009 | Alvin Ashcraft's Morning Dew

Dew Drop - March 12, 2009 | Alvin Ashcraft's Morning Dew — Thu, 12 Mar 2009 12:27:34 GMT

Pingback from Dew Drop - March 12, 2009 | Alvin Ashcraft's Morning Dew

Dew Drop - March 12, 2009 | Alvin Ashcraft's Morning Dew

Dew Drop - March 12, 2009 | Alvin Ashcraft's Morning Dew — Thu, 12 Mar 2009 12:27:31 GMT

Pingback from Dew Drop - March 12, 2009 | Alvin Ashcraft's Morning Dew

re: Developing with Source Code Control - Best Practices Part 2

PeterRitchie — Wed, 11 Mar 2009 17:35:31 GMT

Security? Do you mean lack of security? I'd need an entire post to devote to the all the reasons why not to use VSS.

re: Developing with Source Code Control - Best Practices Part 2

Tom Opgenorth — Wed, 11 Mar 2009 16:57:53 GMT

Yah Peter for explicitly callout VSS as the festering POS that it is!

You also forgot about how chatty VSS is on a network (suchs for VPN/WAN scenarios) and how the security on it is horrible.

Developing with Source Code Control Best Practices Part 2

DotNetKicks.com — Wed, 11 Mar 2009 14:43:40 GMT

You've been kicked (a good thing) - Trackback from DotNetKicks.com