ansaurus

Question

Answer 1

+2 A:

The MSDN page seems to be clear that the one used to build is only the fallback case:

http://msdn.microsoft.com/en-us/library/w4atty68.aspx

If the <supportedRuntime> element is not present in the application configuration file, the version of the runtime used to build the application is used.

Are you seeing behavior that doesn't match that of this MSDN page?

James Manning 2010-06-03 07:28:02

btw, just as a data point, I used supportedRuntime to force my powershell process to load under 4.0 when I needed some 4.0 assemblies to get loaded and it worked just fine for me.

James Manning 2010-06-03 07:29:14

Hmmm, this link http://msdn.microsoft.com/en-us/library/9w519wzk.aspx would seem to suggest that the first thing that happens is to check what the app is built against first and use that CLR if it is present.

Andy 2010-06-03 17:19:20

Good point - IMHO that's a doc bug based on the former page. Besides my PowerShell experience in the past (PS v2 seems to have a problem with it), it's also simple to test by creating a new console app targeting 2.0 (I did this in VS 2010) with just 1 line of Console.WriteLine("CLR version: {0}", Environment.Version);- without an exe.config in place (by default), and running the built exe from the command line, I get: CLR version: 2.0.50727.4927 (which is what we would expect). If I add a config with supported of v4.0 (just via notepad, no VS action) I get CLR version: 4.0.30319.1

James Manning 2010-06-04 16:05:25

Thanks James, nice clarification.

Andy 2010-06-04 19:57:59

ansaurus

tags:

views:

answers:

app.config <supportedRuntime>

related questions