A
Action
As there will be template/generic...
at least, the collection library will be rewrited, is it not?
at least, the collection library will be rewrited, is it not?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
When .Net Framework 2.0 out next year...will the .Net Class Libraries deprecated?
T
Teemu Keiski
Current public information about v2 etc is here:
http://msdn.microsoft.com/vstudio/productinfo/roadmap.aspx#whidbey
--
Teemu Keiski
MCP, Designer/Developer
AspInsiders Member, www.aspinsiders.com
ASP.NET Forums Moderator, www.asp.net
AspAlliance Columnist, www.aspalliance.com
http://msdn.microsoft.com/vstudio/productinfo/roadmap.aspx#whidbey
--
Teemu Keiski
MCP, Designer/Developer
AspInsiders Member, www.aspinsiders.com
ASP.NET Forums Moderator, www.asp.net
AspAlliance Columnist, www.aspalliance.com
D
Daniel O'Connell
From what I've read in MS chats and blogs, older collections and cases where
older collections types were used in the framework will either not be
replaced at all or will be slowly phased out(perhaps 6 years down the line,
regular collections may end up marked obsolete, maybe. But they would still
be left in the framework for a long time to come I'm sure.). Replacing those
classes would break a tremendous amount of code (read, 99% of existing code
base, where have you not used a collection?) and would take support for
basic collections away from languages that don't support generics which, for
a while anyway, will probably be more common than languages that do. Some
languages that a target the framework may never get access to them.
I would expect something more like System.Collections.Generic namespace with
generic collection classes, but until it comes out(or hits a late rc anyway)
no one is going to know for sure how it works.
older collections types were used in the framework will either not be
replaced at all or will be slowly phased out(perhaps 6 years down the line,
regular collections may end up marked obsolete, maybe. But they would still
be left in the framework for a long time to come I'm sure.). Replacing those
classes would break a tremendous amount of code (read, 99% of existing code
base, where have you not used a collection?) and would take support for
basic collections away from languages that don't support generics which, for
a while anyway, will probably be more common than languages that do. Some
languages that a target the framework may never get access to them.
I would expect something more like System.Collections.Generic namespace with
generic collection classes, but until it comes out(or hits a late rc anyway)
no one is going to know for sure how it works.