Prefix / Suffix for Classes

Question

When you write an application that will have a huge number of classes, do you use prefixes / suffixes for your class names? Or should I just rely on namespaces that I have already defined?

In my case, I have classes like:

Blur
Contrast
Sharpen
Invert
...

I just don’t know what I can have tomorrow, and I want to be as free from conflicts as possible with the commonly used classes in BCL.

Any ideas?

Answer 1

Namespaces were invented specifically to solve this problem. Use them.

Answer 2

, , , , MS. , I, , . , , .

Answer 3

, :

• : IFilter
• , : GaussianBlurStrategy
• (from marc_s) : ImageDoesNotSupportFilterTypeException
• , - : FilterBase

. , API , ( ) . , , .

Per Jon B comment, Handler (FilterExecutedHandler(object sender, FilterEventArgs e);). per se, , , , .

Answer 4

, - (, ), .

-

namespace AppName.ImageOperations
{
    public class Blur{...}
}

Answer 5

(, Effect IEffect), , , Effect .

.

Answer 6

, . BCL, , , . .

I- , .

Answer 7

/ . , , , .

.

namespace Company.Department.Product
{
     public class Class
     {}
}

, . , , .

Answer 8

( Microsoft) - ...

:

:

<Company>.(<Product>|<Technology>)[.<Feature>][.<Subnamespace>]

, Microsoft.WindowsMobile.DirectX

, :

( C).

Interfaces that must begin with the letter I are an exception to this rule.

It’s worth at least scanning to pick up some ideas ...