You can't "not" install .NET 2.0--installing VS 2005 will force it.
Think of it .NET 3.0 as the wallpaper (WPF), telephone line (WCF), and the
door locks (Cardspace) of a house. You wouldn't roll out just those items
because they're missing their foundation (.NET 2.0), which is the house itself.
Without 2.0, you wouldn't have System, System.Data, etc.
In reverse,
though, your house CAN exist without wallpaper, telephone lines, or door
locks; they're simply accessories.
While I think I understand what you're trying to do, there is no real separation
between 2.0 and 3.0, 3.0 is simply 2.0+extras and requires 2.0 (AFAIK) to
be installed.
From the link you posted for the SDK download:
For customers that already have the .NET Framework 2.0 installed, this .NET
Framework 3.0 redistributable package installs only the new Windows Vista
components. This ensures that any .NET Framework 2.0-based applications work
seamlessly when the .NET Framework 3.0 is installed, with no application
migration or updates of any kind required.
-dl
--
David R. Longnecker
http://blog.tiredstudent.com
Thanks David,
I want to setup Runtime environment to make some tests. For a machine
which is empty (.Net 2.0 is not installed), I think I should install
the following Runtime SDK to enable .Net 3.0, right?
http://www.microsoft.com/downloads/details.aspx?FamilyId=10CC340B-F857
-4A14-83F5-25634C3BF043&displaylang=en[^]
Any need to install .Net 2.0 Runtime before install the Microsoft .NET
Framework 3.0 Redistributable Package?
regards,
George
David R. Longnecker said:
Like Jon said, it's not so much you develop against 3.0 like you do
2.0; 3.0 is only called on when you call those objects. Microsoft
has somewhat made our developer salespitch (to customers, managers,
and to ourselves somedays when we get confused) a bit difficult with
their odd versioning.
3.0 is simply 2.0 with the Foundations (WinFX) added in. Think of it
as 2.0+WPF,WCF,CardSpace--not so much 3.0. The libraries simply
happened to be "versioned" 3.0 (and someone at MSFT maybe thought it
sounded cool). To complicate matters, if you look at framework 3.5,
the System.Web.Extensions (AJAX) libraries are version 2.0.0.0.
*sigh*
A good way to show the transition is in Orcas... urr.. VS2008. 2008
has the ability to create projects targeting a specific
framework--2.0, 3.0, and 3.5. When you look at your available
projects for 2.0, you see the normal things you see in VS 2005.
However, when you look at 3.0, you see additional templates for the
foundation projects--however they still consume the 2.0 libraries; it
just adds references in to the additional foundation assemblies.
Somewhere around here, I have a document with an object-->framework
map; though I'm sure you can google it too--I think that's how I
found it and it made explaining it to peers FAR easier.
To address your SDK question--no, if you have the 3.0 SDK installed
and happen to consume those objects, your references will
automagically (given you're building in the VS IDE or have specified
it using NAnt or such) couple those libraries to your project in your
config files. Your only concern is that if you share your project,
all of your developers need to have matching SDKs. As far as I know,
there is nothing in 3.0 that overlaps 2.0, simply appends to the
functionality of 2.0.
HTH.
-dl
