Preliminary preparation of the .NET platform

Question

Greetings to friends I need an explanation regarding the preinstallation of the .NET framework when installing a published application on the target machine.

Like java downward compatibility, by which I mean that if I installed java v1.6, and if the application is developed using java v1.5 (I also mean that only classes and packages available in 1.5 are used to create Appln .)

I am sure that the developed application will certainly be launched by installing the latest or later versions of jre or j2se.

Similarly, in the case of the .NET platform, suppose that if I develop my application using the .NET framework 3.5, and I installed the .NET framework 4.0 (the latter) on the target machine, even then he will suggest installing the .NET framework 3.5, why is this so?

Real-time example: I downloaded and tried installing MySQL Workbench, and also installed the .NET framework 4.0. But he still asks to install the .NET framework 3.5 before starting the MySQL installation.

My question is, does the .NET framework support like java or .NET?

Answer 1

Version Compatibility in the .NET Framework :

The .NET Framework 4 is backward compatible with applications that were built using .NET. Framework versions 1.1, 2.0, 3.0 and 3.5. In other words, applications and components created using previous versions of the .NET Framework will work on the .NET Framework 4.

However, in practice this compatibility may be violated by seemingly minor changes in the .NET Framework and changes in programming methods. For example, performance improvements in .NET. Framework 4 may reveal a race condition that did not occur in earlier versions. Similarly, using a hard-coded path to the .NET Framework, assemblies that perform equality comparisons with a specific version of the .NET Framework and obtain the value of a private field using reflection is not the opposite of practice. In addition, each version of the .NET Framework includes bug fixes and security-related changes that may affect the compatibility of some applications and components.

If your application or component does not work as expected on .NET. Box 4, use the following Checklists.

For .NET Framework 2.0, 3.0, and 3.5 applications:

Check the migration of the .NET Framework 4 Questions for any changes that may affect your application and apply the workaround described.

If you recompile an existing source code for the .NET Framework 4, or if you are developing a new version of an application or component that targets the .NET Framework 4 from an existing source code base, check What is deprecated in the .NET Framework for obsolete types and members, and apply the described workaround. (Previously compiled code will continue to work against types and members marked as deprecated.)

If you determine that a change in the .NET Framework 4 has broken your application, check the runtime of the Settings Schema to determine if you can use the runtime settings in your application configuration file to restore the previous behavior.

If you encounter a problem that is not documented, the Microsoft Connect file error and contact [e-mail] with the error number.

Answer 2

Yes, .Net 4 infrastructure is backward compatible with applications built on previous versions of .Net. You can see this link on MSDN for more information.

If you have .Net 3.5 or .Net 4 installed, and the third party still requires (or an older version), then the installer does not check the correct installation conditions.