Inconsistencies in .NET 2.0 (Build 40301)

re: Inconsistencies in .NET 2.0 (Build 40301)

Paul Vick — Fri, 23 Apr 2004 22:21:00 GMT

One thing I would add is that there's also a question of ordering that frequently enters into this equasion. When a feature like TryCast gets checked in, it can take a while before tools that support it get accepted to be used to build the frameworks. We also miss things sometimes, too, so feel free to point out places where it looks like we could do things better!

re: Inconsistencies in .NET 2.0 (Build 40301)

Julien Ellie — Thu, 22 Apr 2004 01:48:00 GMT

Yes, it's very simple, generics are not yet CLS compliant, so no API will expose generics until that's the case.

RE: Inconsistencies in .NET 2.0 (Build 40301)

kpako@yahoo.com (Dare Obasanjo) — Thu, 22 Apr 2004 01:04:00 GMT

When last I checked there were guidelines that any API that used generics should also provide non-generic versions of the method so it could be used from languages that didn't support generics. I don't know if this policy has changed but I didn't see the point of doubling my API surface area for what is effectively syntactic sugar so I didn't use generics in any of the APIs I was designing for Whidbey.

I have no idea about about other teams in Whidbey.