re: VB 10 thoughts (part 8)

bill — Sat, 13 Oct 2007 01:33:01 GMT

Hi Jim,

AOP wasn't what I had in mind when talking about Declarative codign for VB, at least not in terms of how AOP is done today. Rather than interception or IL injection, I'm talking about compiler generated code, same as we have WithEvents.

Admittedly the boundary between those is blurry, os perhaps a better example would be somethign where you indicate the backing storage, Field versus DependencyProperty, e.g:

<Storage(DependencyProperty)> _

Public Property Name As String

Taking this one step further, you might decide that applies to all properties in your class, so rather than mark each property, you could mark the class:

<Properties: Storage(DependencyProperty)> _

Public Class Customer

re: VB 10 thoughts (part 8)

Jim Wooley — Fri, 12 Oct 2007 13:08:31 GMT

To a certain extent, the declaritive validation is already in the works in the Enterprise Library's Validation Application Block. There is a small push for more aspect oriented programming techniques which may take hold in future iterations of the product depending on demand.