Re: Sharing Code

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Please see my reply to Jon Skeet.

--
Jonathan Wood
SoftCircuits Programming
http://www.softcircuits.com

"pedrito" <pixbypedrito at yahoo.com> wrote in message news:QoOdndcFde4N9lXbnZ2dnUVZ_jKdnZ2d@xxxxxxxxxxxxxxx
"Jonathan Wood" <jwood@xxxxxxxxxxxxxxxx> wrote in message news:uuoQ7Ri4HHA.3716@xxxxxxxxxxxxxxxxxxxxxxx
Carl,

Can anyone point me in the right direction getting started learning
the best way to write a library of routines and then being able to
access those routines from several different .NET applications?

You put them in DLLs. This doesn't result in "DLL Hell" because such DLLs are then generally deployed "app local" - in the applications 'bin' directory, rather than in some silly place like %systemroot%.

That wouldn't work very well if I was using the lib from several different applications. Either I'd need to put all the applications in the same directory, or I'd need store multiple copies of the DLL.


Can you explain to us why this wouldn't work? Just curious. You seem pretty convinced this is a problem, but maybe you're seeing problems where problems don't exist. If you can tell us why that won't work, maybe we can understand a little better what the problem is.


.

Quantcast