Re: Is there a standard .Net Aspect software package?

This seems to be a complete summary of the .Net alternatives, only 6
months old ...

 

http://janus.cs.utwente.nl:8000/twiki/bin/view/AOSDNET/CharacterizationO
fExistingApproaches

 

Note that of the 9 for which information is available 5 are dynamic 4
are static - about %50.

 

Only one - EOS - is in a state of both technical and conceptual
completeness. I notice the head of EOS is lead of Technical Risks and
Mitigation Strategies on the site ...

________________________________

From: gregory young [mailto:[email protected]] 
Sent: Wednesday, June 14, 2006 1:18 PM
To: Corpening, Owen
Subject: Re: [aosd-discuss] Is there a standard .Net Aspect software
package?

 

Nearly all will work with 2.0 (the dynamic proxy based ones anyways
which is about 90% of them). They will just not necesarily support
generics in a full way.

 

They operate on closed types so you will still be able to proxy closed
types as you used to. They will not however allow you to proxy generic
types (or to use generic arguments when defining point cuts)

 

ex: instead of saying that you would like to attach an interceptor to

 

List<int>.Add() where it would only apply to generic instances of List
where T was an int

 

you would have to instead use

 

public class Foo : List<int> {

}

 

then apply to your closed class.
 

Other than that rather large missing but of functionality most should
work great.

 

Castle Project's Dynamic Proxy and nAspect are from what I know both
under active development. I know castle is working towards a version
2.0. I have been working on one with full generic support but there are
alot of fringe conditions to think through especially dealing with
mixins and generic proxy reuse. 

 

I have never has the courage to use EOS in a production environment so I
can't really speak on it beyond the trivial examples I have used it for.

 

Cheers,

 

Greg Young
 

On 6/14/06, Corpening, Owen <[email protected]> wrote: 

Seems to me like .Net Aspect development fell off a cliff about 2 years
ago.

 

Are any of the .Net tools still being updated, do any of them work well,
is there a consensus similar to AspectJ being a consensus of sorts in
java? 

 

I successfully used EOS over a year ago but I question whether any of
the .Net packages work of each new release of visual studio, and are in
any way supported. 

 

Open source? EOS was not ...

 

thanks,

Owen Corpening

[email protected] 

602-1000 x59613

 


_______________________________________________
discuss mailing list    -     [email protected] <mailto:[email protected]>


To unsubscribe and change options, go to:
http://aosd.net/mailman/listinfo/discuss_aosd.net 

Check out the AOSD.net Wiki: http://aosd.net/wiki






-- 
If knowledge can create problems, it is not through ignorance that we
can solve them. 

Isaac Asimov

_______________________________________________
discuss mailing list    -    [email protected]

To unsubscribe and change options, go to:
http://aosd.net/mailman/listinfo/discuss_aosd.net

Check out the AOSD.net Wiki: http://aosd.net/wiki