The reason you get the error is because your assembly is signed, and most likely your link to it has the Specific Version property equal to True, and your assembly version number with which you changed this change. I tried many scripts and this was the only script in which I was able to get a FileLoadException. If you change the Target Framework to a newer version, such as 4.0, you will get a BadImageFormatException instead. Even if you say that you have not changed the version number, still check it or set the specific version to False by selecting your link and right-clicking and selecting properties.
Your exception might look like this:
Could not load file or assembly 'LoadedAssembly, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=889080b75eb3bad2' or one of its dependencies. The located assembly manifest
definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
, , , 1.0.0.0 (, - , ). (beit small) , reference 1.0.0.0, True, 2.0.0.0, FileLoadException.
, , " " "False" DLL. .
