In LINQBridge 1.0, ExtensionAttribute was a public class, allowing users
of LINQBridge to write their own extension methods. In LINQBridge 1.1, it
is internal, which doesn't allow for that functionality. In addition, if
you define your own ExtensionAttribute, you get a compiler warning about
two classes in the same namespace (though you can safely ignore it).
Since LINQBridge's goal is to bring .NET 3.5's language features to .NET
2.0, it should have the ExtensionAttribute public.
Original issue reported on code.google.com by allon.guralnek on 29 Jan 2010 at 7:23
Original issue reported on code.google.com by
allon.guralnek
on 29 Jan 2010 at 7:23