Follow @RoyOsherove on Twitter

Useful config files scenarios to keep on hand

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=, Culture=neutral, PublicKeyToken=25283151a234958d“ to version 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=, Culture=neutral, PublicKeyToken=8968ee41e78ce97a“ to codebase ““. '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.

Comment spam wave

T- (11+30) + explanation + apology