Naming

Jan 12, 2008 at 7:50 PM
I'm concerned about the naming of various pieces of the pipeline, particularly retention of the I prefix.

My contract, being an interface should begin with an I

The adapters, being classes, should not begin with an I

In fact, when I madea mistake and failed to begin my contract interface name with an I, I still received adapter files that started with an I

Is there a reason for this? It would appear to go against Microsoft naming guidelines.

It feels early enough to change this, but a year down the road when people have variations of their pipeline builder components it will be more painful.

Thoughts?

Kathleen