Naming Convention

[programmervb netc]

What naming convention do you use so that you can easily find your public functions/routines in intellisense. I love intellisense like my first born but they keep adding stuff to it and it is getting harder and harder to find what I am looking for. Of course we are always adding things to that make it harder to find things. Humble Programmer

[Lost User]

The usage of namespaces can signigicantly reduces the number of items that are present in your intellilist. A naming-conventions' usage should be readability, not discoverability.

I are Troll :suss:

[DaveAuld]

I am sure if you stick to the various guidelines you cannot go far wrong. Obviously your employer/or any project may have specific guidelines which you must adhere to, but i am sure they will soon tell you if they exist. See the likes of here; http://msdn.microsoft.com/en-us/library/ms229045.aspx[^]

Dave Don't forget to rate messages!
Find Me On: Web|Facebook|Twitter|LinkedIn
Waving? dave.m.auld[at]googlewave.com

[fjdiewornncalwe]

My answer would be about simplicity. Use namespacing to classify, and for the love of god name your methods to accurately reflect what they do and don't have the methods do any more. i.e. DO NOT END UP WITH DoThisAndThatAndEverythingElseInHerePlease

[programmervb netc]

Thank you that makes sense. Another somewhat related question I see the big companies compile their own framework as dlls which makes them easy to handle when using them so the question is if I am sharing code across multiple projects but it is addedto almost constantly should I be compiling it as dll files and if so are their any performance benfit/loss in doing so. So what I am saying is will the code run faster as a dll than the code that is compiled in the executable also this code is shared by executables that will probably be ran concurrently I don't know if that makes a difference. Thanks again. Humble Programmer

[Lost User]

programmervb.netc++ wrote:

So what I am saying is will the code run faster as a dll than the code that is compiled in the executable also this code is shared by executables that will probably be ran concurrently I don't know if that makes a difference.

There's not much difference once the library is loaded. It might take a bit longer if you start to load libraries dynamically, especially if Windows' needs to search it's path. Static linking would mean that it loads the library at the start of the application (like it would be if it were part of the executable) Libraries that are shared amongst applications would best be situated in the GAC[^].

I are Troll :suss: