Two Different Versions of .Net Framework On Pc O.K. ? Does Applic. Pick Automatically Which One ?

  • Thread starter Thread starter Robert11
  • Start date Start date
R

Robert11

Hello:

Is it permissible to have two different versions of .Net Framework on your
PC ?

I seem to have applications that require one version, and others that
require a different one.

If both are on the PC, does the application pick the one it needs
automatically, or...?

Thanks,
B.
 
I know it goes against the way things are typically done, but in the case of
the .net framework, version 2.0 does not include all the features of version
1.1, so you need them both. On the other hand, version 1.1 was an update to
version 1, but I'm not sure if that means you don't need both 1 and 1.1.

I just leave 'em all alone. Microsoft created this - let them figure it out
;-)

In future, don't try to cram your question into the subject line.
 
DotNet programs will use the framework they were written in, or if not installed any later version it can find. If the program optionally specifies one or more versions then it has to be one of them. Anyone can add this info to a program. There were breaking changes from 1.0 to 1.1. Programs can be backwards compatible too but requires developer to plan it (or fluke it) that way.

From MSDN
The application configuration file is an .xml file located in the same directory as the application executable (.exe) file. The configuration file name must be the same as the .exe file name with ".config" appended to the end. For example, the application MyApp.exe would have a configuration file named MyApp.exe.config. Note that the configuration file can contain settings that affect other aspects of the application's behavior beside what version of the Framework it should run on.

The Framework version is affected by the contents of the startup section in the configuration file. In particular, the supportedRuntime element affects the choice of the Framework version. The startup section can contain one or more supportedRuntime elements; each element specifies a version of the Framework that the application supports. The supportedRuntime elements are ordered by preference. In other words, the most preferred version of the Framework is listed first. For example, an application that supports both the 1.0 and 1.1 Framework but prefers to use 1.1 Framework would have the following in the startup section of the application configuration file:

<configuration>
…
<startup>
<supportedRuntime version="v1.1.4322" />
<supportedRuntime version="v1.0.3705" />
</startup>
…
</configuration>
The version number specified in the supportedRuntime element must match the subdirectory where the Framework installed. For example, the version 1.0 Framework is installed in the directory C:\Windows\Microsoft.Net\Framework\v1.0.3705; therefore, the version number specified in the configuration file is "v1.0.3705". Similarly, the 1.1 Framework is installed in the C:\Windows\Microsoft.Net\Framework\v1.1.4322 directory. There are no wildcards allowed in the supported runtime version number. Therefore, an application cannot be configured to support a version of the Framework that has not yet been released.
 
Back
Top