Net framework versions

  • Thread starter Thread starter StrandElectric
  • Start date Start date
S

StrandElectric

I am learning .net with the primary aim of making my applications applicable
to any machine running Windows. I note, however, that we are already up to
framework NET 4.

Doesn't this mean that an app developed say with vb2010 will not work on
machines with earlier framework versions. So we are still on this
obsolescence treademill where an exe file will not work on many machines,
depending on the framework vesrion?

Isn't the idea of a product built with vb.net (say a super duper flashy app)
which can be bought off the shelf in fact impossible to achieve?
 
Am 07.01.2011 21:12, schrieb StrandElectric:
I am learning .net with the primary aim of making my applications applicable
to any machine running Windows. I note, however, that we are already up to
framework NET 4.

Doesn't this mean that an app developed say with vb2010 will not work on
machines with earlier framework versions.
Click to expand...

In the project properties, you can set which Framework version to use.
So we are still on this
obsolescence treademill where an exe file will not work on many machines,
depending on the framework vesrion?
Click to expand...

Right, as always in the past and future, if the environment doesn't meet the
minimum requirements, it doesn't work. This can be stopped by cancelling the
development of the Framework so that all future applications will always work.
Isn't the idea of a product built with vb.net (say a super duper flashy app)
which can be bought off the shelf in fact impossible to achieve?
Click to expand...

The Framework can be shipped with the application as a prerequisite. And if not,
it's download is free. But you can not include Windows and the PC, which are also
prerequisites.

Sorry for the whiff of sarcasm. ;)
 
StrandElectric formulated the question :
I am learning .net with the primary aim of making my applications applicable
to any machine running Windows. I note, however, that we are already up to
framework NET 4.

Doesn't this mean that an app developed say with vb2010 will not work on
machines with earlier framework versions. So we are still on this
obsolescence treademill where an exe file will not work on many machines,
depending on the framework vesrion?

Isn't the idea of a product built with vb.net (say a super duper flashy app)
which can be bought off the shelf in fact impossible to achieve?
Click to expand...

Super duper flashy app bought off the shelf will have an install
project that will install the runtime as needed. Just as any
commerical VB project would as well.

If you are certain of a specific version of .NET - 2.0 and above (that
covers 2.0, 3.0, 3.5, and 4.0) then you can build against that
particular version. Currently, 2.0 has the widest distribution. So,
if you target that you will probably be able to xcopy to a ton of
machines - but, if your doing any kind of public distribution, then you
will want a setup project that includes the boot strapper/installer for
your target .net runtime. If it's there, it won't install, if it is,
it will kick off the web installer and install the runtime.
 
Back
Top