VisualSVN Support wrote: > Hi Peter! > Goodness! I posted this nearly 3 months ago. I'd forgotten all about it. Thanks for the reply.
> Have you considered our Knowledge Base article "Web Development with > VisualSVN": http://www.visualsvn.com/support/topic/00002/? > > I hadn't, but I'll take a look now >> 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. > > Certainly. I meant that I didn't want to put the whole of DNN under source contrl. What I wanted to do was to select the bits that belonged to my modules and store them in Subversion. Bear in mind I'm not running a DNN site: just developing modules for other people's sites. So it's only the module I'm developing that I want to keep under source control. The rest of DNN is safely under source control at Sourceforge somewhere :) >> 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 > I think this is the bit that really addresses the problem. Thanks. > 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. > > I'm on my way ... Thanks again. Cheers Peter > 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 >> >> > > > >
