I have a project that has 1 exe and several dll projects in it. One of those DLLs is loaded via LoadLibrary() by the exe. When I set the DLL to be a dependency of the exe MSVS assumes that the DLL will output an export library which it does not. Instead it factories out the object in the DLL which means it does not need to export the class.
Why is MSVS assuming that my DLL project is going to output a library? Does this mean if the DLL does not create an export library that I cannot set it as a dependency for the exe? It is a dependency just not one required until run-time which is perhaps why MSVS is a bit confused. I know I have done this in MSVS 2008 but it is not working in 2005.
Any help would be appreciated.