title: SSIS + AnkhSVN strategy
body: <p>I've read a couple of other questions/answers on stack overflow regarding this, but wanted to get some clarification if possible.</p>
  
  <p>Situation - we have about 20 dtsx files and want to start using SVN to track changes to these packages - we are aware that using SVN will probably not allow us to merge changes within a package due to the complex XML that comprises dtsx file which is acceptable as SVN will still provide some benefits in change tracking.  Currently our development/deployment strategy is that each developer loads dtsx files as needed from the target server, develops locally, and then copies the file back to the target server.  Each developer uses his/her own strategy in terms of whether to have a large project with all of the packages included or to create a new project each time a dtsx needs modification, etc.</p>
  
  <p>I'm looking for suggestions on efficient ways to implement SVN in this environment - should the VS project file (for instance) be included in SVN control?  If not, how does a developer 'Open a project from Subversion'?  Can everything be done within VS or will we need to go the Windows Explorer, Update at  the folder level, then Add Existing Package from within VS - and if we do it that way will we still be able to Commit from VS?</p>
  
  <p>Sorry for the basic questions, new to using SVN in this way and hoping for some specific steps.</p>