Re: How do I get VB.Net to use .net framework 3.5?

[Chris Dunaway]

On Jun 25, 11:05 am, Rory Becker <[e-mail]:

Yes it's true that there are large sections of libraries that you will be
able to use and I guess probably a lot of controls too.

You should be able to use them all! You just won't have any of the
new language syntax to help you. You will have to call all the code
in the 'traditional' manner.

>
But any new language features will be off limits as you need the new compiler

Just to add to this, the new syntax made available in VB2008 compiles
down to ordinary 2.0 IL. So any of the classes in the 3.5 assemblies
are available to be used from VS2005, you just have to code them in
the traditional manner using VB2005 syntax.

Chris

[Jerry Spence1]

So if I compiled using VB2005 it will take 2.0. Now, what happens when I
deploy it on a 3.5 machine? Will it use the latest that is installed, or
stick to 2.0?

- Jerry
"Chris Dunaway" <du******@gmail.comwrote in message
news:aa**********************************@z72g2000 hsb.googlegroups.com...

On Jun 25, 11:05 am, Rory Becker <[e-mail]:

>Yes it's true that there are large sections of libraries that you will be
able to use and I guess probably a lot of controls too.

You should be able to use them all! You just won't have any of the
new language syntax to help you. You will have to call all the code
in the 'traditional' manner.

>>
But any new language features will be off limits as you need the new
compiler

Just to add to this, the new syntax made available in VB2008 compiles
down to ordinary 2.0 IL. So any of the classes in the 3.5 assemblies
are available to be used from VS2005, you just have to code them in
the traditional manner using VB2005 syntax.

Chris

[Rory Becker]

Hello Jerry,

So if I compiled using VB2005 it will take 2.0. Now, what happens when
I deploy it on a 3.5 machine? Will it use the latest that is
installed, or stick to 2.0?

3.5 libraries also use the 2.0 CLR and therefore from your apps perspective,
nothing will have changed.

It will still be running under 2.0 CLR

3.5 includes (and requires) 2.0... your app will just work.

:)

--
Rory

[rowe_newsgroups]

Is there really hardware plus OS around that is not able to use the 3.5

framework.

Windows Server 2000 is one that makes a huge difference.

A ton of businesses still use Windows Server 2000 to run their
websites and have zero interest in shelling out thousands and
thousands of dollars to upgrade it to 2003 or 2008 for the new 3.5
features. One problem (imo) is that OS licensing doesn't fall nearly
as fast as hardware costs do. It's really hard to justify dropping
tens of thousands of dollars so a programmer can use LINQ queries
instead of for loops or to use extension methods instead of just plain
old modules. In some cases an OS upgrade can easily be justified (such
as Entity or similar solutions), but most things I see people using in
3.5 don't have the return on investment for the business owner.

Thanks,

Seth Rowe [MVP]
http://sethrowe.blogspot.com/