Hi Peter! Have you considered our Knowledge Base article "Web Development with VisualSVN": http://www.visualsvn.com/support/topic/00002/?
>I obviously don't want to commit the entire Website to svn. Could you please clarify why don't you want to have the entire Web site under Subversion? It's a common practice even if you have a lot of pictures and other binary files. >Would that work, and is it the best solution to the problem? We could suggest you to add the entire site under Subversion and ignore all folders except <myBusinessLayer> and <myModuleUI>. You'll get the following structure of the Working Copy: -MyWebSite // versioned ---App_Code // versioned -----myBusinessLayer // versioned -----otherCode1 //ignored -----otherCode2 //ignored ---DesktopModules -----myModuleUI //versioned -----otherModule1 //ignored ---OtherWebSiteFolder //ignored You could find more information about the svn:ignore property in the Subversion documentation: http://svnbook.red-bean.com/en/1.5/svn.advanced.props.special.ignore.html. On Fri, Jan 9, 2009 at 4:42 PM, Bradley, Peter <pbrad...@uwic.ac.uk> wrote: > > Hi, > > I have a requirement to store DotNetNuke modules in svn. Modules in DNN are > developed from within DNN itself (which is a Visual Studio Web Site project), > and are stored in two separate folder trees (App_Code\<myBusinessLayer> and > DesktopModules\<myModuleUI>). > > I obviously don't want to commit the entire Website to svn. I just want to > control the two trees with their roots at <myBusinessLayer> and <myModuleUI>. > Is the best way to do it to treat these as two separate sets, such that I > might commit the <myBusinessLayer> tree to > <myRepos>/<myProject>/trunk/<myBusinessLayer>, and commit the <myModuleUI> > tree to <myRepos>/<myProject>/trunk/<myModuleUI>? > > If I did that, presumably I'd have to commit each project separately from > within VS2008? > > Would that work, and is it the best solution to the problem? > > Thanks, > > > Peter > -- Olga Dolidze VisualSVN Support