Here is a quick and easy way to determine the version of the framework, under which an assembly was compiled (code written using
SnippetCompiler):
using System;
using System.Collections.Generic;
using System.Reflection;
public class MyClass
{
public static void Main()
{
Assembly a = Assembly.LoadFile(@"C:\PathToFile\AssemblyFile.dll");
WL(a.ImageRuntimeVersion);
RL();
}
#region Helper methods
private static void WL(object text, params object[] args)
{
Console.WriteLine(text.ToString(), args);
}
private static void RL()
{
Console.ReadLine();
}
#endregion
}
Since Visual Studio is modular, you can install multiple SKUs on top of each other.
You may run across the scenario where you have already installed the applicable SP1 package(s) for Visual Studio 2005 SKUs on your machine, and then install a new SKU (for example, installing VSTS 2005 Tester Edition after already applying SP1 packages to VSTS 2005 Developer Edition). In this case, it is necessary to re-install the applicable SP1 package(s), as documented here:
http://blogs.msdn.com/heaths/archive/2007/03/22/vs-2005-sp1-update-for-vista-requires-vs-2005-sp1.aspx
There are two different Visual Studio 2005 SP1 packages that apply just to Visual Studio (regardless of OS being used):
Then, if running Windows Vista, the
Visual Studio 2005 Service Pack 1 Update for Windows Vista, must be applied
after the applicable patch(es) from the list above.