[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: Vijay Gill <vijay.s.gill_at_gmail.com>
Date: 2006-08-02 18:55:58 CEST

On 02/08/06, Rev. Steve Klett <steveklett@gmail.com> wrote:
> are you components changing that often that you need to "always" download
> all the source? Are your component projects part of your main project's
> solution? If so, they should be built wen you build your main project
> assuming your main project has a project reference to the required
> components.
> I'm not really understanding the problem I guess.
> Having the source to components while developing applications that consume
> them is the greatest luxury as you can really chase down bugs when they
> occur, but I'm sure you already know this.
> If data size is the issue, what is the difference between a bloated .net
> assembly and the source to create it? I would think the source is smaller?
> Sorry for not directly answering your question. ;0)
Thanks for reply Steve.
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

My components are not part of main project, but stand-alone projects
which are 'Reference-ed' by the project that uses them.

In the days of broadband, I am a bit less bothered about size of DLLs.
Also individual components are not very large (the most commonly used
components of mine are 42Kbytes, 22Kbytes and 20 K bytes each).

Regards from

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