Okay, I may have misread.

As long as you are referencing a 2.0 assembly, you should be fine. These can
be found in a variety of locations, but you cannot mix 2.0 and 3.5 without
some form of service boundary. If you need 3.5 funcationality in an app that
cannot be upgraded, you will have to wrap it with a service and call it.

--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA

Subscribe to my blog
http://gregorybeamer.spaces.live.com/lists/feed.rss

or just read it:
http://gregorybeamer.spaces.live.com/

********************************************
| Think outside the box! |
********************************************
"....DotNet4Ever...." <hate.spam@nowhere.com> wrote in message
news:uJdOdFa7IHA.1952@TK2MSFTNGP02.phx.gbl...
> So if I understand correctly it should be no problem if I reference the
> v3.5 System.Net assembly (apparently not available in previous frameworks)
> from a v2.0 solution?
>
> Emilio
> http://www.PanamaSights.com/
> http://www.Virtual-Aviation.info/
>
>
> "Cowboy (Gregory A. Beamer)" <NoSpamMgbworld@comcast.netNoSpamM> wrote in
> message news:O6pXjRZ7IHA.4108@TK2MSFTNGP04.phx.gbl...
>> 3.0 and 3.5 sit on top of 2.0, so there is no big deal here. All you will
>> find in the 3.x directories is extra stuff. Check it out yourself.
>>
>> Not sure why one is referenced in one spot and not in the main spot. Most
>> likely someone was working with it from there and did not reset the link.
>> As long as it works, it is not a big deal.
>>
>> --
>> Gregory A. Beamer
>> MVP, MCP: +I, SE, SD, DBA
>>
>> Subscribe to my blog
>> http://gregorybeamer.spaces.live.com/lists/feed.rss
>>
>> or just read it:
>> http://gregorybeamer.spaces.live.com/
>>
>> ********************************************
>> | Think outside the box! |
>> ********************************************
>> "....DotNet4Ever...." <hate.spam@nowhere.com> wrote in message
>> news:uOvvpyY7IHA.3480@TK2MSFTNGP03.phx.gbl...
>>>I got a problem in one of my solutions and ran into something that I
>>>suppose is what I think but I find the versioning a bit confusing.
>>>
>>> I was trying the Add Reference in Visual Studio and noticed that it
>>> lists both "Version" and "Runtime". Apparently the .NET Framework
>>> version is in the "Version" but all of them (v2.0, v3.0 & v3.5) have the
>>> same runtime "v2.0.50727" which maps to the
>>> c:\windows\Microsoft.NET\Framework\v2.0.50727\
>>>
>>> So, System.NET shows as follows:
>>> System.Net 3.5.0.0 v2.0.50727 c:\Program Files\Reference
>>> Assemblies\.....
>>> System.Messaging 2.0.0.0 v2.0.50727 c:\Windows\Microsoft.NET\Fra....
>>>
>>> why does the v3.5 framework DLL shows the same runtime as the v2.0 and
>>> v3.0 frameworks? and why is it in a different directory root (C:\Program
>>> Files\Reference Assemblies\*) instead of the standard
>>> C:\Windows\Microsoft.NET\Framework\v3.5\... ?
>>>
>>> Shouldn't Visual Studio 2.5 not restrict itself to showing only
>>> Framework 2.0 assemblies?
>>>
>>> Emilio
>>
>