>- copy the .config on the console application You don't actually have to copy the config, instead you just need to make sure that config exists in the host application, in your case it seems like the console is the host application which means that it should be available for that client app. >- add all the dlls in the console application references. But I still need it in the library application (without, the code in the library doesn't compile) : so basically, I have to references twice all the DLLs... no way I'm gonna to do this. Please note the difference between: a) referencing DLLs at compile time b) making sure DLLs are available at runtime In your case it is enough to do (b), so you don't have to do (a). (a) worked for you just because the referenced dlls were automatically copied to the output folder for you but that is not ideal solution, instead you should just have (post) deployment step which will copy required dlls to the output folder, but, again, you don't have to reference the dlls if your application doesn't require then at compilation time.
↧