Activity overview
Latest activity by !noital
Ok - in the end then, target runtime does not appear to be a useful metric. Sure - reflector is doing it's job, but the information isn't useful - and the subtle difference between Target Runtime and Target Framework will clearly confuse people.
This simply means .NET Reflector isn't really the tool for this. / comments
Ok - in the end then, target runtime does not appear to be a useful metric. Sure - reflector is doing it's job, but the information isn't useful - and the subtle difference between Target Runtime ...
That makes sense - but it's still wrong. When you set the target environment to 3.5 then some of the assemblies necessary to run the application (such as system.core.dll) must be 3.5 or the app will not run. So even though the header says 2.0 - the application will not run - so a better way to Identify the target runtime needs to be found - or it's not really a useful thing to even bother showing.
Des / comments
That makes sense - but it's still wrong. When you set the target environment to 3.5 then some of the assemblies necessary to run the application (such as system.core.dll) must be 3.5 or the app w...
Target Runtime Reported
Why does an assembly compiled specifically for 3.5 show up as having a target runtime of 2.0 (2.0.50727)?
Apparently some of the assemblies in 3.5 are still older 2.0, but I would think that .net r...