Tools can use this attribute to detect potential violations of the compatibility guarantee in future versions of a component. NET Framework 4, you can specify the degree to which a component is expected to remain compatible across multiple versions by applying the attribute to that component. NET Framework that the app runs on.īecause of this restriction, compatibility guarantees are especially important for components. Components and class libraries are loaded in the context of a particular app, and that's why they automatically run on the version of the. NET Framework on which it runs, but a component can't. Version compatibility for componentsĪn app can control the version of the. įor more information, see How to: Configure an App to Support. Each element lists a supported version of the runtime, with the first specifying the most preferred version and the last specifying the least preferred version. To define the specific versions on which your app runs, add one or more elements to your app's configuration file. In this case, the attempt to run the app will fail. NET Framework initialization error may occur. If that version isn't present and the app configuration file doesn't define supported versions, a. Version compatibility for appsīy default, an app runs on the version of. ![]() NET Framework should behave identically on later versions of. NET Framework, and binaries that run on one version of. ![]() NET Framework should compile on later versions of. Backward compatibility means that an app that was developed for a particular version of a platform will run on later versions of that platform.NET Framework tries to maximize backward compatibility: Source code written for one version of.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |