You might already be aware of the great Ent Lib and its immense support for framework like activities such as data access, logging, exception handling etc. The dlls shipped out of the box are not strong named and therefore could be a lot of trouble (if one's not judicious). So the key is to build the Ent Lib solution with a strong name key referenced in the global configuration file.
So now your application would need to reference these strong named assemblies (mostly GACed), however since the application configuration has been created with EntLibConfig.exe (GUI) the resultant files will have reference to the 'raw' non-strong named assemblies.
So one of the solutions is to manually add the fully qualified names of EntLib dlls in the freshly created config files.
I have not tried but i presume that strong-naming all the dlls in the bin folder of should help as well since in that case EntLibConfig.exe would use the strong-named dlls to create the configuration in the first place therefore saving you the trouble of manual modifications.
Possunt quia posse videntu...