yeh, I don't quite understand the heart burn some folks are having over
that. I mean its about double the size of 2.0. And the framework itself is
nothing but a bunch of libraries that they stamp with a version number so
you can expect certain libs to be in the framework. Same thing here. They
added a lot more apis and gave fx got a new stamp. I mean the kernel does
not need to change to roll out a new OS with a bunch of new stuff ontop it.
That said, it seems like a hard thing to pass up doing pending fixes on
core. I can only guess the versioning issues for everyone would be too
drastic of a change and delay too many things at this point. Its still in
CTP, so maybe things will change. Not sure. Anyone know of killer bugs in
2.0 that will not be fixed?
--
William Stacey [MVP]
| Jared wrote:
| > Any bug fixes?
|
| No. Take a look at
| <
http://blogs.msdn.com/somasegar/archive/2006/06/09/624300.aspx> and you
| will see that what is now going to be called '.NET Framework 3.0' is
| "comprised of the *existing* .NET Framework 2.0 components, including
| ASP.NET, WinForms, ADO.NET, additional base class libraries and the CLR,
| as well as new developer-focused innovative technologies in WPF, WCF, WF
| and WCS". That is, the WinForms and WebForms stuff we have now isn't
| changing. Some people think it's unfortunate to up the version number of
| something when it isn't changing, merely having new bits bolted on. But
| there you go.
|
|
| --
| Larry Lard
| (e-mail address removed)
| The address is real, but unread - please reply to the group
| For VB and C# questions - tell us which version
