Re: Sharing Code

Tech-Archive recommends: Repair Windows Errors & Optimize Windows 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.


.

Relevant Pages

  • Re: Reference Point for Code Size
    ... void by listing off a few key routines that occur in much of *my* work ... the purpose of exposing you to routines, applications, and problem ... would know the kinds of routines, applications, and problem domains that ...
    (comp.lang.forth)
  • Re: Reference Point for Code Size
    ... Since you were vague with your requirements, I attempted to fill the void by listing off a few key routines that occur in much of *my* work with the hope that it would trigger others to chime in. ... That also had the purpose of exposing you to routines, applications, and problem domains that you may not have considered. ... After all, if it is just for you, you presumably would know the kinds of routines, applications, and problem domains that were relevant to you, and you wouldn't have posted at all. ...
    (comp.lang.forth)
  • Re: Get your questions answered by LabVIEW developers.
    ... converted app to perform its routines somewhere near an acceptable ... My question applies to future directions in this way:  ... - If future labview versions include sufficient documentation regarding architecture ... the final applications can run fast and efficiently, ...
    (comp.lang.labview)
  • Re: Sharing Code
    ... access those routines from several different .NET applications? ... or I'd need store multiple copies of the DLL. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Dll Hell
    ... :>ship with an installer is tame, and it puts usbcalls.dll and ... DLLs are created to share code between applications and to short used ...
    (comp.os.os2.apps)