.NET Versions

[William Brown]

Hi do I need all the versions installed or just V4..?


Thanks

[Peter Duniho]

Post by William Brown
Hi do I need all the versions installed or just V4..?

That depends. If you don't run any .NET programs, you don't need any
versions installed at all.

Seriously though, the version(s) of .NET you need installed will depend
on the version of .NET that the program you're trying to run is
targeting. You may or may not need versions other than 4.0.

Pete

[William Brown]

On Tue, 11 Jan 2011 17:22:11 -0800, Peter Duniho

Post by Peter Duniho

Post by William Brown
Hi do I need all the versions installed or just V4..?

That depends. If you don't run any .NET programs, you don't need any
versions installed at all.
Seriously though, the version(s) of .NET you need installed will depend
on the version of .NET that the program you're trying to run is
targeting. You may or may not need versions other than 4.0.
Pete

Are we saying that .Net transport is not backwards compatible..?

[Peter Duniho]

Post by William Brown
Are we saying that .Net transport is not backwards compatible..?

No, that's not what "we" are saying. .NET 4.0 is capable of running
assemblies compiled for earlier versions. But, assemblies do include
information about what DLL versions they are targeting.

By default, a program compiled for an earlier version of .NET won't run
if the only version you have installed is 4.0. But you can update the
application .config file to include the "supportedRuntime" element, to
indicate that it should be permitted to run under the 4.0 version.

In other words, what version of .NET is required depends on how a
particular program you want to run is configured. You don't have to
recompile to change the configuration, but the configured requirements
do have to match what you've got installed.

Here's a forum thread that may explain it better:
http://social.msdn.microsoft.com/Forums/en/netfxsetup/thread/4f0b7821-506f-453f-896e-54a545c75081

Pete

[William Brown]

On Tue, 11 Jan 2011 23:41:27 -0800, Peter Duniho

Post by Peter Duniho

Post by William Brown
Are we saying that .Net transport is not backwards compatible..?

No, that's not what "we" are saying. .NET 4.0 is capable of running
assemblies compiled for earlier versions. But, assemblies do include
information about what DLL versions they are targeting.
By default, a program compiled for an earlier version of .NET won't run
if the only version you have installed is 4.0. But you can update the
application .config file to include the "supportedRuntime" element, to
indicate that it should be permitted to run under the 4.0 version.
In other words, what version of .NET is required depends on how a
particular program you want to run is configured. You don't have to
recompile to change the configuration, but the configured requirements
do have to match what you've got installed.
http://social.msdn.microsoft.com/Forums/en/netfxsetup/thread/4f0b7821-506f-453f-896e-54a545c75081
Pete

Thanks


But were is the Config File..?

Or is this a .INI File..?


I have noticed that a Program that states is needs 3.5 and it generate a
.INI file when its run.?

Very puzzled as I don't think you can patch this as it would be
generated new each time its run.

[Peter Duniho]

Post by William Brown
But were is the Config File..?

It is generally found in the same directory with the executable.

Post by William Brown
Or is this a .INI File..?
I have noticed that a Program that states is needs 3.5 and it generate a
..INI file when its run.?

Not sure what you're talking about. .NET programs do not normally
create or use .ini files (that is, the file format supported by the
unmanaged "…Profile" functions in Windows).

Pete

[cubaman]

Post by William Brown
On Tue, 11 Jan 2011 23:41:27 -0800, Peter Duniho

Post by William Brown
Are we saying that .Net transport is not backwards compatible..?

No, that's not what "we" are saying.  .NET 4.0 is capable of running
assemblies compiled for earlier versions.  But, assemblies do include
information about what DLL versions they are targeting.
By default, a program compiled for an earlier version of .NET won't run
if the only version you have installed is 4.0.  But you can update the
application .config file to include the "supportedRuntime" element, to
indicate that it should be permitted to run under the 4.0 version.
In other words, what version of .NET is required depends on how a
particular program you want to run is configured.  You don't have to
recompile to change the configuration, but the configured requirements
do have to match what you've got installed.
http://social.msdn.microsoft.com/Forums/en/netfxsetup/thread/4f0b7821...
Pete

Thanks
But were is the Config File..?
Or is this a .INI File..?
I have noticed that a Program that states is needs 3.5 and it generate a
.INI file when its run.?
Very puzzled as I don't think you can patch this as it would be
generated new each time its run.

Hello:
In .Net, configuration files are xml files, in the same directory of
your application, having the same name but with .config extension.
So, myapp.exe config file will be myapp.exe.config.
Hope this help. Best regards.

[William Brown]

On Thu, 13 Jan 2011 02:07:02 -0800 (PST), cubaman

Post by cubaman

Post by William Brown
On Tue, 11 Jan 2011 23:41:27 -0800, Peter Duniho

Post by William Brown
Are we saying that .Net transport is not backwards compatible..?

No, that's not what "we" are saying.  .NET 4.0 is capable of running
assemblies compiled for earlier versions.  But, assemblies do include
information about what DLL versions they are targeting.
By default, a program compiled for an earlier version of .NET won't run
if the only version you have installed is 4.0.  But you can update the
application .config file to include the "supportedRuntime" element, to
indicate that it should be permitted to run under the 4.0 version.
In other words, what version of .NET is required depends on how a
particular program you want to run is configured.  You don't have to
recompile to change the configuration, but the configured requirements
do have to match what you've got installed.
http://social.msdn.microsoft.com/Forums/en/netfxsetup/thread/4f0b7821...
Pete

Thanks
But were is the Config File..?
Or is this a .INI File..?
I have noticed that a Program that states is needs 3.5 and it generate a
.INI file when its run.?
Very puzzled as I don't think you can patch this as it would be
generated new each time its run.

In .Net, configuration files are xml files, in the same directory of
your application, having the same name but with .config extension.
So, myapp.exe config file will be myapp.exe.config.
Hope this help. Best regards.

Problem is that it not a stay resident program, for what it does is to
install hooks,tasks scrip's etc, sort of a patch program.

[mp]

Post by Peter Duniho

Post by William Brown
Hi do I need all the versions installed or just V4..?

That depends. If you don't run any .NET programs, you don't need any
versions installed at all.
Seriously though, the version(s) of .NET you need installed will depend on
the version of .NET that the program you're trying to run is targeting.
You may or may not need versions other than 4.0.
Pete

pete
If i install vc#2010 is it going to hose my 2008 files/ ide?
ie do files written in 2008 need revised to run in 2010?
or is it a pretty painless transition?
thanks
mark

[Peter Duniho]

Post by mp
If i install vc#2010 is it going to hose my 2008 files/ ide?
ie do files written in 2008 need revised to run in 2010?
or is it a pretty painless transition?

You can easily run VS2008 and VS2010 together on the same computer, no
problem. In fact, I have had at least three version installed at once
on one computer (2005, 2008, and 2010).

However, you will find that the .sln and .csproj files are not
interchangeable. VS2010 can upgrade from 2008, but you won't be able to
open those files in 2008 later. And you can't use a 2008 solution or
project form 2010 unless it's been upgraded first to the 2010 format
(and I use the term "format" loosely…99.9% of the content of the files,
which are just plain text files, is identical from version to version; I
find the versioning issues frustrating).

The actual .cs files (and other kinds of source code) _can_ be shared,
of course. But that means referencing the same source file from
multiple projects, which is generally not a great idea. Sometimes it's
the only way out of an already less-than-optimal situation though. :)

In general, you should stick to doing only things in 2010 that you know
you won't want to go back and use 2008 for. It is possible to downgrade
a solution/project from 2010 to 2008, but it's usually more trouble than
it's worth. I've found it's easier, if I really have to get my 2010
code back into a 2008 project, to just create a new solution and project
from scratch and add the source files back to the project manually. But
it's easiest to just not have to do that in the first place. :)

Pete

[mp]

Post by Peter Duniho

Post by mp
If i install vc#2010 is it going to hose my 2008 files/ ide?
ie do files written in 2008 need revised to run in 2010?
or is it a pretty painless transition?

You can easily run VS2008 and VS2010 together on the same computer, no
problem. In fact, I have had at least three version installed at once on
one computer (2005, 2008, and 2010).
However, you will find that the .sln and .csproj files are not
interchangeable. VS2010 can upgrade from 2008, but you won't be able to
open those files in 2008 later. And you can't use a 2008 solution or
project form 2010 unless it's been upgraded first to the 2010 format (and
I use the term "format" loosely.99.9% of the content of the files, which
are just plain text files, is identical from version to version; I find
the versioning issues frustrating).
The actual .cs files (and other kinds of source code) _can_ be shared, of
course. But that means referencing the same source file from multiple
projects, which is generally not a great idea. Sometimes it's the only
way out of an already less-than-optimal situation though. :)
In general, you should stick to doing only things in 2010 that you know
you won't want to go back and use 2008 for. It is possible to downgrade a
solution/project from 2010 to 2008, but it's usually more trouble than
it's worth. I've found it's easier, if I really have to get my 2010 code
back into a 2008 project, to just create a new solution and project from
scratch and add the source files back to the project manually. But it's
easiest to just not have to do that in the first place. :)
Pete

Thanks for the feedback
optional args would be nice from time to time
but not sure if it's worth upgrading
lacking any other imperative to convert
not that into the lastest thing just for the sake that it's newer
i'm sure there's lots more in 4.0, just not sure if i need it at my level
mark