http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Thanks for the shout-out Oren. My thoughts are in line with what Stefan said. Our current product suite is well suited for source control. As a vendor, when we walk in to a customer site, one of the initial implementation tasks should be to get things under version control. I spent all day yesterday at a customer site coding some customizations for them. At the end of the day, I didn't have anywhere to check code into. I felt somewhat dirty. Like my job wasn't really done. When I asked their technical team about what version control system they used, they just shrugged. Ugh. Last week I had a customer ask me to resend them some custom development that we did for them 8 months ago, because they had "lost" the entire project that we delivered. Double-ugh. http://ayende.com/2953/platform-should-have-source-control-and-that-is-not-optional#comment3http://ayende.com/2953/platform-should-have-source-control-and-that-is-not-optional#comment3Thu, 15 Nov 2007 19:37:15 GMT...platform that does hurt... You meant "doesn't" right? http://ayende.com/2953/platform-should-have-source-control-and-that-is-not-optional#comment2http://ayende.com/2953/platform-should-have-source-control-and-that-is-not-optional#comment2Thu, 15 Nov 2007 19:08:22 GMTI think built-in is the wrong path. Enterprise plattforms should work well with my text files and DLLs, and allow me to import them by file copy operations. So, no need to mess with some proprietary version control mechanisms, or take the configuration and troubleshooting pains to integrate the app with an existing SCM. Just point SVN to the directory that has your customization files, done. http://ayende.com/2953/platform-should-have-source-control-and-that-is-not-optional#comment1http://ayende.com/2953/platform-should-have-source-control-and-that-is-not-optional#comment1Thu, 15 Nov 2007 17:52:18 GMT