Suzanne shows some useful application config files that allow you do achieve specific CLR stuff:. I'll probably need this some day. here are the examples titles:
- Forces the v1.0 CLR to be run. If the v1.0 CLR is not installed, the app will fail to run.
- Redirects “assemblyName, Version=220.127.116.11, Culture=neutral, PublicKeyToken=25283151a234958d“ to version 18.104.22.168 of that assembly. This is only useful for strongly-named assemblies, since versions don't matter for those that are simply-named.
- Redirects “assemblyName, Version=22.214.171.124, Culture=neutral, PublicKeyToken=8968ee41e78ce97a“ to codebase “http://www.yourwebsite.com/filename.dll“. 'Href' can also be set to something like “file:///c:/localfile/filename.dll“. Note that redirecting to a codebase causes a System.Net.WebPermission or System.IO.FileIOPermissionAccess.Read + PathDiscovery demand when loading that assembly.