Have a project compiled to use (TargetFrameworkVersion) framework version 3.0 however it looks like there are some bug fixes in the latest v4.0 framework and HF. As we want the app to be available even if it is leaking a bit on the earlier frameworks, we don’t want to just set the target to 4.0.
When you browse the project you can see it has a runtime version but the ‘specific version’ is flagged false.
When we run the app, can we tell what framework parts it is actually using. Will it default to 3.0 or will it use the latest assemblies.
If it defaults to 3.0 is there some way of setting some policy of some sort to use the new assembly if available.
Will compiling against/targeting the 4.0 framework yield any different results on top of using it at runtime?
When you run a .NET app, it will default to the version of the Framework it was compiled for. You can specify that it can use other Frameworks by including SupportedRuntime elements in the app config file in the Configuration/Startup section. However, I do not think an application can specify that it runs on a later framework than what it’s built for.
If you want the runtime to try to use v4.0, but if that’s not installed you will still run on v3.5, you should compile the app in 4.0 and include a SupportedRuntime element in the app config with the full version (including build) of v3.5.