Using a 3rd party C(++) library in a VC project should be as easy as right-clicking that VC project and selecting "Use library > "library name", then being presented with a dialog where I customize rest of the options (library version, dll vs. static), hitting OK and it should _just work_ for compiling, linking and running, taking into account different platforms and configurations (Debug vs. Release) the 3rd-party library is available for.
This could maybe be implemented using some kind of SDK registry, where 3rd-party libraries could register their version(s), location of headers, location and name of import libraries and DLLs, and library-specific options (presented then in the UI and resulting e.g. in defining of some preprocessor macro), and how debug and release files are named.
Integrating this somehow with CoApp would be fantastic. Automatic download of the library with headers and import libraries compiled with the correct compiler without me leaving VC ... I can dream.
The tedious and errorprone process of using 3rd party libraries in Visual C++ is for me its greatest shortcoming.
Thanks for considering this feature request.