DLL output file naming convension

This is a discussion on DLL output file naming convension within the C# Programming forums, part of the General Programming Boards category; Hello everyone, Previously, I think if I am using namespace ns1, and declaring and defining a public class cs1 using ...

  1. #1
    Registered User
    Join Date
    May 2006
    Posts
    1,579

    DLL output file naming convension

    Hello everyone,


    Previously, I think if I am using namespace ns1, and declaring and defining a public class cs1 using C# Class Library project, I have to name the output DLL name to be ns1.dll. I have this idea because I noticed that Microsoft names the DLLs, like System.dll for name space System, System.Data.dll for name space System.Data.

    Now I tried that I can name the output DLL name to arbitrary name (not ns1), like mylib.dll. Then the applications which use the DLL still work.

    So, I think the conclusion should be, we can use arbitrary name which is not related to namespace. Right?


    thanks in advance,
    George

  2. #2
    Confused Magos's Avatar
    Join Date
    Sep 2001
    Location
    Sweden
    Posts
    3,145
    You can name it whatever you want. Microsoft's naming is just a convenience to (quickly) know what is in each dll.
    MagosX.com

    Give a man a fish and you feed him for a day.
    Teach a man to fish and you feed him for a lifetime.

  3. #3
    Kernel hacker
    Join Date
    Jul 2007
    Location
    Farncombe, Surrey, England
    Posts
    15,677
    Yes, there's absolutely no connection between the name of the DLL and it's content. If you want to call a DLL fred.dll or kernel32.dll or hagfifgajggaduteauryejhjs.dll, that's entirely up to you - but it's probably hard to remember the third one, and the second might get a bit confusing to which kernel32.dll that you wish to use - the one supplied by MS or your own.

    Obviously, if there's a good way to associate your DLL with what it does, then that's a bonus in most peoples mind. If you have a DLL that implements encryption/decryption, then calling it "crypt.dll" might be a good idea. If the namespace of a class is meaningfull as the name of a DLL, then that's one possible good name.

    --
    Mats

Popular pages Recent additions subscribe to a feed

Similar Threads

  1. A development process
    By Noir in forum C Programming
    Replies: 37
    Last Post: 07-10-2011, 11:39 PM
  2. Basic text file encoder
    By Abda92 in forum C Programming
    Replies: 15
    Last Post: 05-22-2007, 02:19 PM
  3. Batch file programming
    By year2038bug in forum Tech Board
    Replies: 10
    Last Post: 09-05-2005, 04:30 PM
  4. what does this mean to you?
    By pkananen in forum C++ Programming
    Replies: 8
    Last Post: 02-04-2002, 03:58 PM
  5. Simple File Creation Algorithm
    By muffin in forum C Programming
    Replies: 13
    Last Post: 08-24-2001, 04:28 PM

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21