Re: What exactly Dll does

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Arne Vajhøj <arne@xxxxxxxxxx>
Date: Sat, 31 Mar 2007 21:41:36 -0400

Nicholas Paldino [.NET/C# MVP] wrote:

What do you mean? As opposed to an EXE? From .NET 2.0 and on, the only difference between dlls and exes are that exes are entry points to applications, dlls are not. You can add references to each of them to use the types that are used in them.

As for 1.1 and before, you could only set references to DLLs.

No.

You can reference an EXE just fine in .NET 1.1 !

Visual Studio 2003 has a check that does not allow it,
but the C# compiler does not have any problems with it.

Arne
.

Follow-Ups:
- Re: What exactly Dll does
  - From: Scott M.

Prev by Date: Re: How to read html files AS IS. Encoding seems to change the characters.
Next by Date: Re: C# IDE - commenting / uncommenting
Previous by thread: Re: How to read html files AS IS. Encoding seems to change the characters.
Next by thread: Re: What exactly Dll does
Index(es):
- Date
- Thread

Relevant Pages

Re: problems with running 32-bit tclsh on Windows x64
... EXEs, while ... inaccessible files from %SystemRoot%\system32 to another directory ... that is accessible to 32-bit applications? ...
(comp.lang.tcl)
Re: References in VS.Net 2003
... There's been a path pointing to the applications directory, ... > Hi Urs, ... I have a number of shared DLLs in my solution, ... >> references to the local directory of the application. ...
(microsoft.public.dotnet.languages.csharp)
Debug/Release confusion in Visual Studio .NET 2003
... Two DLLs are referenced by both ... applications, and one DLL is referenced by one application only. ... debug output directory to the release output directory. ... input file paths on the property pages for the respective references, ...
(microsoft.public.vstudio.general)
References in VS.Net 2003
... I observed that my solutions frequently changes the location of references. ... whole solution and its applications are dependent from these DLLs, ... Any hints where this could come from, or what I could do about it? ...
(microsoft.public.dotnet.languages.csharp)
Default Specific Version setting for references
... Maybe I'm missing the obvious here but can someone explain the logic ... Our product has on the order of 300 dlls and exes and I've gotten ... The external references are the ...
(microsoft.public.dotnet.languages.csharp)