Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I think the closest you can reliably get is to determine what version of the CLR is required. You can do this by using ILDASM and looking at the ‘MANIFEST’ node or Reflector and looking at the dissasembly view of the ‘Application.exe’ node as IL. In both cases there is a comment that indicates the CLR version. In ILDASM, the comment is ‘// Metadata version’ and in Reflector the comment is ‘Target Runtime Version’.
Here are examples for a .NET WinForms application named WindowsFormsApplication1.exe:
ILDASM:
Reflector:
You can also look at the list of referenced assemblies and look for the reference with the highest version number.
Again, using ILDASM looking at the ‘MANIFEST’ node data:
And using Reflector, looking at the dissambly (still as IL) for each reference listed:
By finding the reference with the highest version metadata you can determine what version of the Framework that reference came from, which would indicate that you need the same version of the Framework installed for the application to run. That being said, I wouldn’t treat this as 100% reliable, but I don’t think it will change any time soon.