.net version usage

  • Thread starter Thread starter Berryl Hesh
  • Start date Start date
B

Berryl Hesh

What are some reasons why a given development effort might be done in a
version of .net less than the latest release, considering that it's backward
compatible?

OTOH, if you do create an app in the latest release, and use the features in
it, would a user need to have that release on their machine in order to
execute the compiled binaries?

Thanks,
BH
 
Berryl Hesh said:
What are some reasons why a given development effort might be done in a
version of .net less than the latest release, considering that it's
backward
compatible?

OTOH, if you do create an app in the latest release, and use the features
in
it, would a user need to have that release on their machine in order to
execute the compiled binaries?
Click to expand...

Yes, if you use the features in the latest release, every target
computer will need that release installed on their machine in order to use
your application. This is one reason to develop in an "old" version of .Net.
Note that Visual Studio 2008 can target versions 2.0 and 3.0 (besides 3.5),
so you can develop using the latest environment, and use many of the new
language features, and still generate binaries that will run under these
older .Net Framework versions.

Another reason to develop on an old version of the Framework is the case
where you need to maintain an old, well-tested application. Even though new
versions are supposed to be backwards compatible, the compatibility is not
always perfect, and the applications need to be re-tested and debugged after
migration.
 
Berryl Hesh said:
What are some reasons why a given development effort might be done in a
version of .net less than the latest release, considering that it's backward
compatible?

OTOH, if you do create an app in the latest release, and use the features in
it, would a user need to have that release on their machine in order to
execute the compiled binaries?

Thanks,
BH
Click to expand...

There are enviroments that are very locked down, and do not allow tools to
be added to systems. On such a system you must develop to the lowest common
denominator.
 
What are some reasons why a given development effort might be done in a
version of .net less than the latest release, considering that it's
backward
compatible?
Click to expand...

In my case my boss got a great hosting deal with FastHosts years ago (no
idea what the details are) which he can keep for life. I suspect though
that they regret the life-time guarantee because they decided to stop
providing .NET at V2 for this type of account in order to "entice" you to a
different (and undoubtedly more expensive) alternative option.

It was bad news for me, all that lovely code I had to "downgrade" to make it
work in V2. Especially the fact that I had to switch to ASP.NET from
ASP.NET MVC. Oh well :-)
 
Back
Top