http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660I really distrust systems which do automated deployments to prod. I want a human to have to pull the trigger. http://ayende.com/3554/strategies-for-editing-dsl-scripts-in-production#comment5http://ayende.com/3554/strategies-for-editing-dsl-scripts-in-production#comment5Mon, 25 Aug 2008 14:32:24 GMTFor a good Subversion .NET library (managed wrapper) try SharpSvn: http://sharpsvn.open.collab.net/ but to just update some files in production a simple bat script would suffice :) http://ayende.com/3554/strategies-for-editing-dsl-scripts-in-production#comment4http://ayende.com/3554/strategies-for-editing-dsl-scripts-in-production#comment4Mon, 25 Aug 2008 07:30:00 GMTInteresting idea, but it works only in some cases - in many cases it is hard to convince the client, which might be on another continent, that he will have to install and manage also a SVN server, in addition to the usual web server and database server.. http://ayende.com/3554/strategies-for-editing-dsl-scripts-in-production#comment3http://ayende.com/3554/strategies-for-editing-dsl-scripts-in-production#comment3Mon, 25 Aug 2008 07:00:16 GMTKonstantin, you could checkout SharpDevelop sources and have a look at project SVNChangelogToXml, in the tools subfolder (SharpDevelop\src\Tools\SVNChangeLogToXml ) http://ayende.com/3554/strategies-for-editing-dsl-scripts-in-production#comment2http://ayende.com/3554/strategies-for-editing-dsl-scripts-in-production#comment2Mon, 25 Aug 2008 05:08:35 GMTOren, the idea is nice. The problem of changable reports can be solved with this approach. Can you recommend .Net API to use to integrate SVN into the application? http://ayende.com/3554/strategies-for-editing-dsl-scripts-in-production#comment1http://ayende.com/3554/strategies-for-editing-dsl-scripts-in-production#comment1Mon, 25 Aug 2008 04:49:08 GMT