.net 3.5 - Naming conventions for extension method namespaces and sponsor classes -

What naming conventions are you using for namespaces and sponsor sections? (I.e. classes that catch extensions law definitions)

Is there a standard / recommended NAT Framework Naming Convention? ("Framework Design Guideline, 2nd Edition" book guides only not to use the name).

For namespace - I will focus on the standard framework guidelines for namespace names. Put the expansion methods in a namespace, where they will usually be used / connected in a meaningful way, and avoid having extra namespace for this.

For the sponsor class - in this case, it is quite unimportant. I try to choose the name of a class which is meaningful, but does not seem to have certain guidelines.

The important thing here is that the sponsor class is never actually used directly / is seen as long as the namespace is included to the user of your extension methods, the extension method is found correctly. . I privately use a lot like this for my extension methods, but Microsoft does not follow this framework (this is a good example square).