[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: Daniel Buchholz <db.buchholz_at_gmail.com>
Date: 2006-08-02 16:33:02 CEST

2006/8/2, Vijay Gill <vijay.s.gill@gmail.com>:
> Hi,
> I develop my own components some times for using in my projects. I
> maintain every component as an independent project.
> Now after having more than a few of those, I am running into the
> problem of maintaining the latest versions. Currently I have to get
> the latest source code of the components, compile them and then only I
> can start working on my main project (by getting its latest version
> also).

We have quite the same setup. At the moment there are 19 API projects with
several developers committing when they need to.

And that is exactly the reason for us always using comiled code as externals
in our other projects. You can never know which API commit of another
developer breaks your current code. And we encourage developers to get fresh
API code from time to time to build new API DLLs and test them with their
own project code to make sure everything is OK.

Received on Wed Aug 2 16:35:08 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.