Hi,
In updated to .NET Framework 3.0 but projects, even new, still reference the
2.0 framework.
If I go to my ASP .Net tab in web site properties, my only options are
framework versions 1 and 2.
A reinstall of 3 tells me that it is already installed.
This is running on Windows XP Prof.
Anyone know what the problem is with this?

TIA,
Chris

I don't get it.
The first thing I went to check out was System.IO.Packaging but it was not
there...


"sloan" <(E-Mail Removed)> wrote in message
news:uF4Rgz%(E-Mail Removed)...
>
> 3.0 is not a replacement, its an Addon.
>
> 2.5 would have been a better name for it.
>
> But oh well.
>
>
>
>
> "Chris" <(E-Mail Removed)> wrote in message
> news:OYIIcq%(E-Mail Removed)...
>> Hi,
>> In updated to .NET Framework 3.0 but projects, even new, still reference
> the
>> 2.0 framework.
>> If I go to my ASP .Net tab in web site properties, my only options are
>> framework versions 1 and 2.
>> A reinstall of 3 tells me that it is already installed.
>> This is running on Windows XP Prof.
>> Anyone know what the problem is with this?
>>
>> TIA,
>> Chris
>>
>>
>
>

3.0 is not a replacement, its an Addon.

2.5 would have been a better name for it.

But oh well.




"Chris" <(E-Mail Removed)> wrote in message
news:OYIIcq%(E-Mail Removed)...
> Hi,
> In updated to .NET Framework 3.0 but projects, even new, still reference
the
> 2.0 framework.
> If I go to my ASP .Net tab in web site properties, my only options are
> framework versions 1 and 2.
> A reinstall of 3 tells me that it is already installed.
> This is running on Windows XP Prof.
> Anyone know what the problem is with this?
>
> TIA,
> Chris
>
>

Hi Chris,

..Net 3.0 is just .Net 2.0 with a few added libraries, there is nothing new
in the basic framework, and installing .Net 3.0 on a system without .Net
will result in both .Net 2.0 and 3.0 being installed. With .Net 3.0 you
get WF (Windows Workflow Foundation), WPF (Windows Presentation
Foundation) and WCF (Windows Communication Foundation).

The next upgrade of .Net Framework is actually .Net 3.5, which will be
launched with Visual Studio Orcas


On Wed, 14 Feb 2007 05:10:06 +0100, Chris <(E-Mail Removed)>
wrote:

> I don't get it.
> The first thing I went to check out was System.IO.Packaging but it was
> not
> there...
>
>
> "sloan" <(E-Mail Removed)> wrote in message
> news:uF4Rgz%(E-Mail Removed)...
>>
>> 3.0 is not a replacement, its an Addon.
>>
>> 2.5 would have been a better name for it.
>>
>> But oh well.
>>
>>
>>
>>
>> "Chris" <(E-Mail Removed)> wrote in message
>> news:OYIIcq%(E-Mail Removed)...
>>> Hi,
>>> In updated to .NET Framework 3.0 but projects, even new, still
>>> reference
>> the
>>> 2.0 framework.
>>> If I go to my ASP .Net tab in web site properties, my only options are
>>> framework versions 1 and 2.
>>> A reinstall of 3 tells me that it is already installed.
>>> This is running on Windows XP Prof.
>>> Anyone know what the problem is with this?
>>>
>>> TIA,
>>> Chris
>>>
>>>
>>
>>
>
>



--
Happy Coding!
Morten Wennevik [C# MVP]

Hi Chris,

I agree with Morten and Sloan. This behavior is by design.
The .NET Framework 3.0 is an additive release to the .NET Framework 2.0.
The .NET Framework 3.0 adds four new technologies to the .NET Framework
2.0: Windows Presentation Foundation (WPF), Windows Workflow Foundation
(WF), Windows Communication Foundation (WCF), and Windows CardSpace. There
are no changes to the version of the .NET Framework 2.0 components included
in the .NET Framework 3.0. for these reason, your application will still
reference the 2.0 framework.

Additionally, this is the reason why .NET Framework 3.0 installer will
check whether you already have the .NET Framework 2.0 installed. If not,
the .NET Framework 3.0 installer will install the .NET Framework 2.0 for
you, and then install the new .NET Framework 3.0 components. If you do have
the .NET Framework 2.0 installed, the .NET Framework 3.0 installer will
only install the new components of the .NET Framework 3.0

You can get more detailed information from the following document.
http://msdn2.microsoft.com/cn/netfra.../aa663314.aspx
[.NET Framework 3.0 Versioning and Deployment Q&A]

Please feel free to reply me if there is anything unclear.
Hope this helps.
Wen Yuan

I got a message during install that regedit had to install the Windows
Workflow Foundation 3.0.0.0. I wonder if that service is legit. I'm guessing
yes, but I'd like to know what it is there for under XPSP2.

"Chris" wrote:

> Hi,
> In updated to .NET Framework 3.0 but projects, even new, still reference the
> 2.0 framework.
> If I go to my ASP .Net tab in web site properties, my only options are
> framework versions 1 and 2.
> A reinstall of 3 tells me that it is already installed.
> This is running on Windows XP Prof.
> Anyone know what the problem is with this?
>
> TIA,
> Chris
>
>
>

That's one of the new technologies added by Framework 3.0.

Mike Ober.

"hselburn" <(E-Mail Removed)> wrote in message
news:C959B13B-B936-4EDB-BFE7-(E-Mail Removed)...
>I got a message during install that regedit had to install the Windows
> Workflow Foundation 3.0.0.0. I wonder if that service is legit. I'm
> guessing
> yes, but I'd like to know what it is there for under XPSP2.
>
> "Chris" wrote:
>
>> Hi,
>> In updated to .NET Framework 3.0 but projects, even new, still reference
>> the
>> 2.0 framework.
>> If I go to my ASP .Net tab in web site properties, my only options are
>> framework versions 1 and 2.
>> A reinstall of 3 tells me that it is already installed.
>> This is running on Windows XP Prof.
>> Anyone know what the problem is with this?
>>
>> TIA,
>> Chris
>>
>>
>>

I understand what everyone is saying, but the MS Launch Tour presentation
showed that we would use the System.IO.Packaging class to work with the new
Office 2007 formats. They said it is part of framework 3.0.
Now I have installed framework 3.0, I cant find the Packaging class and it
seems most of the links pertaining to framework 3.0 on the MS website are
dead end links.

Do I need to add another reference to my project to make use of 3.0
features?
Chris



"Morten Wennevik [C# MVP]" <(E-Mail Removed)> wrote in message
news(E-Mail Removed)...
> Hi Chris,
>
> .Net 3.0 is just .Net 2.0 with a few added libraries, there is nothing new
> in the basic framework, and installing .Net 3.0 on a system without .Net
> will result in both .Net 2.0 and 3.0 being installed. With .Net 3.0 you
> get WF (Windows Workflow Foundation), WPF (Windows Presentation
> Foundation) and WCF (Windows Communication Foundation).
>
> The next upgrade of .Net Framework is actually .Net 3.5, which will be
> launched with Visual Studio Orcas
>
>
> On Wed, 14 Feb 2007 05:10:06 +0100, Chris <(E-Mail Removed)>
> wrote:
>
>> I don't get it.
>> The first thing I went to check out was System.IO.Packaging but it was
>> not
>> there...
>>
>>
>> "sloan" <(E-Mail Removed)> wrote in message
>> news:uF4Rgz%(E-Mail Removed)...
>>>
>>> 3.0 is not a replacement, its an Addon.
>>>
>>> 2.5 would have been a better name for it.
>>>
>>> But oh well.
>>>
>>>
>>>
>>>
>>> "Chris" <(E-Mail Removed)> wrote in message
>>> news:OYIIcq%(E-Mail Removed)...
>>>> Hi,
>>>> In updated to .NET Framework 3.0 but projects, even new, still
>>>> reference
>>> the
>>>> 2.0 framework.
>>>> If I go to my ASP .Net tab in web site properties, my only options are
>>>> framework versions 1 and 2.
>>>> A reinstall of 3 tells me that it is already installed.
>>>> This is running on Windows XP Prof.
>>>> Anyone know what the problem is with this?
>>>>
>>>> TIA,
>>>> Chris
>>>>
>>>>
>>>
>>>
>>
>>
>
>
>
> --
> Happy Coding!
> Morten Wennevik [C# MVP]

The link is broken and it seems that most of the MS links that relate to
framework 3.0 are also broken.
I replied to one of the other posts asking how I would access the Packaging
class so that I could work with Office 2007 document.

I still don't now how to access anything that




""WenYuan Wang"" <v-(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi Chris,
>
> I agree with Morten and Sloan. This behavior is by design.
> The .NET Framework 3.0 is an additive release to the .NET Framework 2.0.
> The .NET Framework 3.0 adds four new technologies to the .NET Framework
> 2.0: Windows Presentation Foundation (WPF), Windows Workflow Foundation
> (WF), Windows Communication Foundation (WCF), and Windows CardSpace. There
> are no changes to the version of the .NET Framework 2.0 components
> included
> in the .NET Framework 3.0. for these reason, your application will still
> reference the 2.0 framework.
>
> Additionally, this is the reason why .NET Framework 3.0 installer will
> check whether you already have the .NET Framework 2.0 installed. If not,
> the .NET Framework 3.0 installer will install the .NET Framework 2.0 for
> you, and then install the new .NET Framework 3.0 components. If you do
> have
> the .NET Framework 2.0 installed, the .NET Framework 3.0 installer will
> only install the new components of the .NET Framework 3.0
>
> You can get more detailed information from the following document.
> http://msdn2.microsoft.com/cn/netfra.../aa663314.aspx
> [.NET Framework 3.0 Versioning and Deployment Q&A]
>
> Please feel free to reply me if there is anything unclear.
> Hope this helps.
> Wen Yuan
>

On Feb 14, 8:35 am, "Chris" <chri...@newsgroups.nospam> wrote:
> The link is broken and it seems that most of the MS links that relate to
> framework 3.0 are also broken.
> I replied to one of the other posts asking how I would access the Packaging
> class so that I could work with Office 2007 document.
>
> I still don't now how to access anything that

You can access Packaging after you install the Windows SDK for .NET
3.0 and then the VS extensions for .NET 3.0 (there are two packages to
install).

Then you can either create a new .NET 3.0 project or you can add a
reference to WindowsBase.

Now when you add your using declarations System.IO.Packaging is an
option.