Asp Forum - Use 2.0 assembly in 3.5 project? - microsoft.public.dotnet.framework

Pieter

11/3/2008 5:14:00 PM

Hi,

We would liek to start using .NET Framework 3.5, and migrate some of our
projects. Although: some of them will stay for a while on .NET 2.0. The
problem is: some projects will be referenced in a 3.5 and in a 2.0 project.
Will this work? And if yes: do we have to do anything special?

For instance:
- Project A = 2.0
- Solution B = 2.0
- Solution C = 3.5
-> Project A is referenced in Solution B and in Solution C.

Thanks a lot in advance,

Pieter

4 Answers

Patrice

11/3/2008 5:45:00 PM

A 3.5 project is just a 2.0 projects that uses some new DLLs (actually it
applies a SP to 2.0). In particular it still uses the 2.0 CLR so you
shouldn't have any problem.

Similarly if you don't plan to use anything new in your C project then there
is no need to upgrade.

--
Patrice

"Pieter" <pieterNOSPAMcoucke@nospam.nospam> a écrit dans le message de
groupe de discussion : OKaWeedPJHA.576@TK2MSFTNGP04.phx.gbl...
> Hi,
>
> We would liek to start using .NET Framework 3.5, and migrate some of our
> projects. Although: some of them will stay for a while on .NET 2.0. The
> problem is: some projects will be referenced in a 3.5 and in a 2.0
> project. Will this work? And if yes: do we have to do anything special?
>
> For instance:
> - Project A = 2.0
> - Solution B = 2.0
> - Solution C = 3.5
> -> Project A is referenced in Solution B and in Solution C.
>
> Thanks a lot in advance,
>
>
> Pieter
>

Cowboy

11/4/2008 12:09:00 AM

In most cases there is no problem, as 3.5 sits on top of 2.0. If you have a
problem, wrap the 2.0 bits in a service call of some sort. A bit of
overhead, but saves you from upgrade right now.

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

Subscribe to my blog
http://feeds.feedburner.com/Greg...

or just read it:
http://feeds.feedburner.com/Gre...

********************************************
| Think outside the box! |
********************************************
"Pieter" <pieterNOSPAMcoucke@nospam.nospam> wrote in message
news:OKaWeedPJHA.576@TK2MSFTNGP04.phx.gbl...
> Hi,
>
> We would liek to start using .NET Framework 3.5, and migrate some of our
> projects. Although: some of them will stay for a while on .NET 2.0. The
> problem is: some projects will be referenced in a 3.5 and in a 2.0
> project. Will this work? And if yes: do we have to do anything special?
>
> For instance:
> - Project A = 2.0
> - Solution B = 2.0
> - Solution C = 3.5
> -> Project A is referenced in Solution B and in Solution C.
>
> Thanks a lot in advance,
>
>
> Pieter
>

stcheng

11/4/2008 3:08:00 AM

Hi Rafia,

As other guys has explained, you can run .NET 2.0 application in a .NET 3.5
environment without problems. This is because .NET 3.5(also .NET 3.0) is
built upon .NET 2.0, it rely on the .NET 2.0 clr engine and most
fundamental class library. In my opinion, .NET 3.0 and 3.5 is more like
some advanced pack on the .NET framework 2.0 which add more features(such
as the W*F in .NET 3.0 and the LINQ, AJAX in .NET 3.5)

For development consideration, the VS 2008 IDE support multi-target
projects(from .NET 2.0, .NET 30 to .NET 3.5). Therefore, you can develop
applications target different version of .NET framework.

#VS 2008 Multi-Targeting Support
http://weblogs.asp.net/scottgu/archive/2007/06/20/vs-2008-multi-ta...
pport.aspx

http://blogs.msdn.com/dajung/archive/2008/03/17/vs2008-and-multi-t...
eworks.aspx

In addition, you can read the following articles about more explanation on
the .NET 2.0 and .NET 3.X versioning:

http://blogs.msdn.com/zxue/archive/2008/01/02/how-is-the-net-frame...
ifferent-from-net-2-0-and-net-3-0.aspx

http://blogs.msdn.com/johnmullinax/archive/2008/01/09/what-is-the-...
et-3-5-vs-net-2-0-well-that-depends-on-you.aspx

If you have any further specific questions, welcome to post here.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we

can improve the support we provide to you. Please feel free to let my
manager know what you think of

the level of service provided. You can send feedback directly to my manager
at: msdnmg@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to

http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#not....

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
>From: "Pieter" <pieterNOSPAMcoucke@nospam.nospam>
>Subject: Use 2.0 assembly in 3.5 project?
>Date: Mon, 3 Nov 2008 18:14:20 +0100

>
>We would liek to start using .NET Framework 3.5, and migrate some of our
>projects. Although: some of them will stay for a while on .NET 2.0. The
>problem is: some projects will be referenced in a 3.5 and in a 2.0
project.
>Will this work? And if yes: do we have to do anything special?
>
>For instance:
>- Project A = 2.0
>- Solution B = 2.0
>- Solution C = 3.5
>-> Project A is referenced in Solution B and in Solution C.
>
>Thanks a lot in advance,
>
>
>Pieter
>
>
>

Pieter

11/4/2008 8:30:00 AM

Ok, thanks a lot all of you for the answers!

microsoft.public.dotnet.framework

Use 2.0 assembly in 3.5 project?

Pieter

Patrice

Cowboy

stcheng

Pieter

x Login to ForumsZone