Why use "Public" with exe projects?

[Joel Moore]

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?

Do people leave them public simply because that's how VS.NET's code
generator produces them or are there other advantages I'm missing
altogether?

Is it worth it to convert public types to "Friend" (or whatever the C#
equivalent is...) or is that just wasted effort?

Joel Moore

 

[Kelly Ethridge]

In DotNET (2.0 at least), you can reference EXE's just like DLL's.

Kelly

 

[Jon Skeet [C# MVP]]

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.

 

[Joel Moore]

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.