Re: A lesson on why Windows dominates computing...


nobiscuit wrote:
> >> >It also shows that DLLs are a powerful and useful system asset, not
> >> >simply the "DLL Hell" of Maccies' imaginations.
>
> >> DLLs do have their advantages. Ease of deployment is not one of them.
> >> I know from experience. I used to be the install guy for the Windows
> >> development shop where I work. It doesn't help that dlls provided by
> >> Microsoft that are supposed to be backwards compatible sometimes
> >> aren't. This makes them difficult to update them without hosing the
> >> system. Heck, even Microsoft has acknowledged that dll hell exists:
>
> >> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndo...
>
>
> >For some reason you overlooked that solutions to the problem are there,
> >not just an acknowledgement of it.
> >
> >Those solutions have been deployed for a long time too.
>
> My point was that dll hell is not imaginary.

It was not imaginary. It no longer exists, except for people who are
behind the times.

> It is true that .Net deployment is supposed to avoid dll hell. That is
> assuming a program runs purely in .Net. I haven't seen a .Net app
> deployed to a wide user base yet so I can't speak to that. I hope that
> it does. However, the problem of dll hell remains when deploying COM
> objects.
>
> Unfortunately, COM isn't going away any time soon. There is way to
> much legacy stuff running around. That's the reason .Net and COM can
> interoperate.

..Net isn't the only solution. The easiest way out of DLL Hell is to
use path assignments for DLLs specific to an appliction. They go into
the applications' folder instead of into the System Folder, so there's
no conflict between different versions of System DLLs.

.

Relevant Pages

  • Re: Deployment Question
    ... > use those core DLLs. ... > in the system folder and just share them between the two applications. ... deployment method. ... locating assemblies is concerned. ...
    (microsoft.public.vstudio.general)
  • Re: Deployment Question
    ... >> applications that use those core DLLs. ... >> .DLLs in the system folder and just share them between the two ... I would go ahead with the simple XCopy deployment. ...
    (microsoft.public.vstudio.general)
  • Re: Deployment Question
    ... > applications that use those core DLLs. ... Put the assemblies in the bin folders of their respective apps. ... I would go ahead with the simple XCopy deployment. ...
    (microsoft.public.vstudio.general)
  • Enterprise Service Deployment
    ... Business Logic Layer is a Serviced Component and has been ... Application Proxy and installed on a client machine. ... these dlls are dependencies for the Business Logic Layer. ... deployment procedure, but this did not work either: ...
    (microsoft.public.dotnet.distributed_apps)
  • RE: .NET dll config file
    ... a suitable deployment scenario. ... The Application A, uses my dlls, via a COM dll. ... B.Dll will load Common.C.Dll from the common subfolder ...
    (microsoft.public.dotnet.framework)