Naming .NET executables: any practices?

  • Thread starter Thread starter A. Petrov
  • Start date Start date
A

A. Petrov

Hi,

What MS recommends regarding naming .NET executable files?

Is it better to name my assembly as MyCompany.MyProduct.exe or

MyProduct.exe?

Is there any guidelines from MS? Specifically, if the product contains many
assemblies (exe + many dlls).

Many thanks in advance!

Alexander
 
Take a look in your local machine's file system, where Microsoft
applications reside, for an idea of how Microsoft names executable files.
Generally, the file names are fairly short, probably due to the limitations
of the OS regarding the total length of a file path. As for assemblies,
their names are sometimes longer, and sometimes include periods to indicate
namespaces, probably for clarity, and because they reside in the GAC, which
is a known path that is short in length (C:\Windows\Assemblies). See the GAC
for examples.

--
HTH,

Kevin Spencer
Microsoft MVP
Short Order Coder
http://unclechutney.blogspot.com

The devil is in the yada yada yada
 
Thank you for the clarification.

Alexander

Kevin Spencer said:
Take a look in your local machine's file system, where Microsoft
applications reside, for an idea of how Microsoft names executable files.
Generally, the file names are fairly short, probably due to the
limitations of the OS regarding the total length of a file path. As for
assemblies, their names are sometimes longer, and sometimes include
periods to indicate namespaces, probably for clarity, and because they
reside in the GAC, which is a known path that is short in length
(C:\Windows\Assemblies). See the GAC for examples.

--
HTH,

Kevin Spencer
Microsoft MVP
Short Order Coder
http://unclechutney.blogspot.com

The devil is in the yada yada yada
Click to expand...
 
Back
Top