The principle described applies to any app that targets a later version of. NET Framework than the one installed on the system on which it's running. Some changes in. NET Framework may require changes to your app code; see Application Compatibility before you run your existing apps with. For more information about installing the current version, see Install the.
NET Framework for developers. For information about support for the. NET Framework, see. NET Framework official support policy on the. NET website. NET Framework versions 2. These versions represent successive layers of a single installation.
Each version is built incrementally on top of the earlier versions. It's not possible to run versions 2. When you install version 3. NET Framework 4 ends this layering approach, and it and later releases.
Starting with. NET Framework 4, you can use in-process, side by side hosting to run multiple versions of the CLR in a single process. For more information, see Assemblies and Side-by-Side Execution. In addition, if your app targets version 2. NET Framework 3. For more information, see Install the. If you're new to the. NET Framework, see the overview for an introduction to key concepts and features. For new features and improvements in the. For example,. NET Framework versions include 4.
The common language runtime CLR , which manages and executes your app's code. A single CLR version typically supports multiple. NET Framework versions. For example, CLR version 4. NET Framework versions 4 through 4. CLR version greater than or equal to 4. NET Framework versions starting with. NET Framework 4. Community-maintained tools are available to help detect which. NET Framework versions are installed:. For information about detecting the installed updates for each version of.
NET Framework updates are installed. You can use the RuntimeInformation. FrameworkDescription property to query for which. NET implementation and version your app is running on. If the app is running on. NET Framework, the output will be similar to:. The version of. If the Full subkey is missing, then. NET Framework installed. To determine whether a minimum version of.
For example, if your application runs under. From the Start menu, choose Run , enter regedit , and then select OK. If the Full subkey isn't present, then you don't have. NET Framework version regardless of the Service Pack level, or to detect a service pack level or a later service pack level of the same.
NET Framework version, use the registry information that listed Table 2. Table Environment class, as in the following C code snippet. If you compile this program with the. At the command prompt type the following. Running the tool with no options displays all installed CLR versions. Office Office Exchange Server. Not an IT pro? Find centralized, trusted content and collaborate around the technologies you use most. Connect and share knowledge within a single location that is structured and easy to search.
I have an application that uses the. NET framework 3. I am building this application for a college to help students to study. Sorry Mac users! The Mac version will come out in about 6 months What version of the.
If you want to be certain that you application runs on all of these, you will have to install the framework yourself - use SmallestDotNet. NET Framework 3. I just found out and was scared Have a look at this similar question 'Is there a way to determine the. NET Framework version from the command line? In that answer there is a link to the article on CodeProject that does exactly that As you're going to install.
NET Framework with your application you may also find. NET Client Profile useful. It's a small version of framework that can be bundled with your distribution.
0コメント