[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: A suggestion needed on using shared .Net DLLs

From: Rev. Steve Klett <steveklett_at_gmail.com>
Date: 2006-08-03 02:10:05 CEST

Just to add to this, they can still be part of their own solution as well.
If you have a solution called "MyComponents", adding them to your apps
solution as well doesn't take away from the organization you have already in
place. Like Gavin said and I hinted at in my post, it just makes things a
lot easier. lots and lots. :0)

On 8/2/06, Gavin Lambert <tsvn@mirality.co.nz> wrote:
> Quoth Vijay Gill:
> > My components (as any other piece of code) undergo changes even while
> > the projects using them are being developed. Also whenever I need some
> > new functionality, while developing a project, which can be placed in
> > a component, I do it right-away. But since this component comes into
> > existance as a part of development, it might need changes as we go
> > along.
> >
> > My components are not part of main project, but stand-alone projects
> > which are 'Reference-ed' by the project that uses them.
> In which case the simplest and most sensible thing to do is to make them
> all part of the same solution file. Not only will they all build
> together (making sure you're using the most up-to-date code), you'll be
> able to more easy debug into them as necessary.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
> For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Thu Aug 3 02:10:12 2006

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.