API naming confusion

Jul 29, 2009 at 5:18 PM

I think that you should consider the naming of ExportAttribute and Export
because ExportAttribute can use as [Export] it can cause confusion.

Because we use to write attribute in the short way we use to think of it as its class name.

Developer that using the ctrl+ . for namespace completion may append the wrong namespace by mistake and
then it really hard to understand why do I get strange IntelliSense

Jul 29, 2009 at 5:36 PM

HI Bnaya

Thanks for the feedback. This has been fixed in the upcoming version of VS. The classes are in different namespace, and have a different name. It is a bug in VS that causes this.

Regards

Glenn

From: bnaya [mailto:notifications@codeplex.com]
Sent: Wednesday, July 29, 2009 10:19 AM
To: Glenn Block
Subject: API naming confusion [MEF:63900]

From: bnaya

I think that you should consider the naming of ExportAttribute and Export
because ExportAttribute can use as [Export] it can cause confusion.

Because we use to write attribute in the short way we use to think of it as its class name.

Developer that using the ctrl+ . for namespace completion may append the wrong namespace by mistake and
then it really hard to understand why do I get strange IntelliSense

Read the full discussion online.

To add a post to this discussion, reply to this email (MEF@discussions.codeplex.com)

To start a new discussion for this project, email MEF@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe or change your settings on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com