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

A suggestion needed on using shared .Net DLLs

From: Vijay Gill <vijay.s.gill_at_gmail.com>
Date: 2006-08-02 14:36:09 CEST


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

Is it ok if I do the following?

I create another repository for the compiled version of my components.
And then use this repository as externals in every project that I
develop. This way, if I download the latest source code of my project,
I will get latest version of my components also.

Since this involves another developer over-seas, I need a solution to
my problem badly. We both are sick of downloading the latest versions
of source code of every component, compiling it before starting to
work on the actual project.

If my idea is not wrong, I will try to do the things myself and may be
come back later with more questions :)

Regards from


PS: Apologies if this mail should have gone to subversion ML.

To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Wed Aug 2 14:36:19 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.