Re: Why use "Public" with exe projects?

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

From: Joel Moore <asdadsasd@xxxxxxxxxxxx>
Date: Fri, 08 Dec 2006 12:02:27 -0800

Jon Skeet [C# MVP] <skeet@xxxxxxxxx> wrote in
news:MPG.1fe3a6389a00848298d6d3@xxxxxxxxxxxxxxxxxxxx:

Joel Moore <asdadsasd@xxxxxxxxxxxx> wrote:

Is there any point to making classes or interfaces public in an EXE
project? Executables can't be referenced by other applications so why
would you ever need public classes?

Executables can be referenced by other applications. Prior to VS 2005,
one could only do it by manually editing the project file, but it's
certainly possible.

Well I'll be. Thanks.
.

References:
- Why use "Public" with exe projects?
  - From: Joel Moore
- Re: Why use "Public" with exe projects?
  - From: Jon Skeet [C# MVP]

Prev by Date: Debugging .net libraries in both the GAC and local folder
Next by Date: Web application problems
Previous by thread: Re: Why use "Public" with exe projects?
Next by thread: round buttons in vb.net
Index(es):
- Date
- Thread