Differences/changes between .NET 2.0 and 3.0

  • Thread starter Thread starter GlennDoten
  • Start date Start date
G

GlennDoten

I'll try this here. Has anyone been successful in finding a full list
of what's changed (apparently nothing) and what's new (apparently a
lot) between .NET 2.0 and 3.0? I know some of the new stuff like WPF,
etc., but need a list of all the differences if one exists.

Thanks for any help.

-glenn-
 
WPF, WWF, and WCF, etc. are *additions* to the .Net *2.0* platform. They are
not .Net 3.0.

--
HTH,

Kevin Spencer
Microsoft MVP
Ministry of Software Development
http://unclechutney.blogspot.com

I just flew in from Chicago with
a man with a wooden leg named Smith
who shot an elephant in my pajamas.
So I bit him.
 
Hello Kevin,

They stated (can't find link) that they've made a minor changes to .net 2.0
that ships with label .net 3.0 for the better compatibility with the Vista.
but they don't specify them

KS> WPF, WWF, and WCF, etc. are *additions* to the .Net *2.0* platform.
KS> They are not .Net 3.0.
KS>
KS> Kevin Spencer
KS> Microsoft MVP
KS> Ministry of Software Development
KS> http://unclechutney.blogspot.com
KS> I just flew in from Chicago with
KS> a man with a wooden leg named Smith
KS> who shot an elephant in my pajamas.
KS> So I bit him.
KS> KS>---
WBR,
Michael Nemtsev :: blog: http://spaces.live.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche
 
OK, now I think I'm really confused. What is there that is left that is
in .NET 3.0?

Are you saying that .NET 3.0 is .NET 2.0 with additional namespaces and
classes for WCF, WWF, and WPF added?

-glenn-
 
GlennDoten said:
OK, now I think I'm really confused. What is there that is left that is
in .NET 3.0?
Click to expand...

..Net 3.0 is just a collection of libraries that sit on top of .Net 2.0.
These libraries offer a new, albiet fancy, alternatives to:
- WinSock (was Indigo, now WCF)
- WinForms (was Avalon, now WPF)
- Passport (was InfoCard, now Cardspace)
- and hand-rolled workflow applications (was Hulkamania, now just WWF)

In terms of additions to .Net itself (the CLR) there really isn't anything.

In no way should this diminish the amazing things you can do with .Net 3.0.
These new technologies are nothing short of amazing.
 
Hi,
OK, now I think I'm really confused. What is there that is left that is
in .NET 3.0?

Are you saying that .NET 3.0 is .NET 2.0 with additional namespaces and
classes for WCF, WWF, and WPF added?

-glenn-
Click to expand...

Roughly said, this is absolutely correct.

HTH,
Laurent
 
Chris Mullins said:
.Net 3.0 is just a collection of libraries that sit on top of .Net 2.0.
Click to expand...

I believe the .NET 2.0 libraries, which have been revised in "version
number" only for the most part, are redistributed in the v3.0 package. So
if you have v2 and v3 installed at the same time, you have two iterations of
basically the same set of 2.0 libraries, one in the v2 directory and one in
the v3 directory in \windows\microsoft.net\framework.

Jon
 
I take that back. I don't see 2.0 framework stuff anywhere in the 3.0
folders (including in program files).

Jon
 
Right. But isn't that what most library updates are (including our own);
just additions to the prior version? You typically don't change apis of
prior version that would break app compat - unless there is a really good
reason. You build on it with new classes (i.e. datetime2, MyObject2, etc)

--
William Stacey [C# MVP]

| Hi,
|
| GlennDoten wrote:
| > OK, now I think I'm really confused. What is there that is left that is
| > in .NET 3.0?
| >
| > Are you saying that .NET 3.0 is .NET 2.0 with additional namespaces and
| > classes for WCF, WWF, and WPF added?
| >
| > -glenn-
|
| Roughly said, this is absolutely correct.
|
| HTH,
| Laurent
| --
| Laurent Bugnion, GalaSoft
| Software engineering: http://www.galasoft-LB.ch
| Private/Malaysia: http://mypage.bluewin.ch/lbugnion
| Support children in Calcutta: http://www.calcutta-espoir.ch
 
Hi Michael,

Yes, of course you're right.

I'm *so confused!*

--
;-),

Kevin Spencer
Microsoft MVP
Ministry of Software Development
http://unclechutney.blogspot.com

I just flew in from Chicago with
a man with a wooden leg named Smith
who shot an elephant in my pajamas.
So I bit him.
 
I have found (and bookmarked a few links that should help clear all this up:

Microsoft .Net Framework 3.0 Community Site:
http://www.netfx3.com/

Microsoft Windows Vista Developer Center:
http://msdn.microsoft.com/windowsvista/support/relnotes/netfx3/default.aspx

Microsoft Visual C# Future Versions:
http://msdn2.microsoft.com/en-us/vcsharp/aa336745.aspx

Microsoft XNA:
http://msdn.microsoft.com/directx/XNA/default.aspx

--
HTH,

Kevin Spencer
Microsoft MVP
Ministry of Software Development
http://unclechutney.blogspot.com

I just flew in from Chicago with
a man with a wooden leg named Smith
who shot an elephant in my pajamas.
So I bit him.
 
Hello Chris,

All old winsocks, winforms and other stuff are still exist, they only add
new WinFX feaures without complete abolishing all old stuff

CM> These libraries offer a new, albiet fancy, alternatives to:
CM> - WinSock (was Indigo, now WCF)
CM> - WinForms (was Avalon, now WPF)
CM> - Passport (was InfoCard, now Cardspace)
CM> - and hand-rolled workflow applications (was Hulkamania, now
CM> just WWF)
CM> In terms of additions to .Net itself (the CLR) there really isn't
CM> anything.


---
WBR,
Michael Nemtsev :: blog: http://spaces.live.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche
 
Hello Jon,

What do u call "framework stuff"
it is, as was mentioned before, in the \Windows\Microsoft.NET\Framework\
folder. There should be 2.0 and 3.0 folders

JD> I take that back. I don't see 2.0 framework stuff anywhere in the
JD> 3.0 folders (including in program files).
JD>
JD> Jon
JD>
JD> JD>---
WBR,
Michael Nemtsev :: blog: http://spaces.live.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsch
 
Right. But isn't that what most library updates are (including our own);
just additions to the prior version?
Click to expand...

I wouldn't say that. This may be the first time I've seen a major
version of a product (3.0 in this case) actually distribute the same
installer kit from a previous version of the product (2.0 in this
case). Normaly when you install 3.0 of something you get just that, not
an earlier version of the product with some additional features added.
See what I mean?

I think this, um, creative packaging has caused a lot of confusion and
will continue to do so. At least I know it has where I work.

Think how odd it would have been if .NET 2.0 consisted of the same
installer kit for .NET 1.0 plus some updates that are applied on top of
..NET 1.0. Wouldn't that strike you a odd?

-glenn-
 
Back
Top