In these cases, your main project will be the only existing one. In case of the many simple applications (like many of the tutorials will be) you do not need to break down the application into modules. Every project will realize something and you will have a main project in which you can put together this project puzzle. Projects are the building blocks of an application. A solution may contain multiple projects. The base item of a project in Visual Studio is a solution. Inside the global section of this tutorial I'll show what the main differences are. There is a 2008 and previous versions and a 2010 way of doing it. In case of the global one how you do it depends on the Microsoft Visual Studio you use. The advantage of the global one is that you only need to do it once however, it may be undesirable to clump all your projects all the time with all this information. To pass on all this information to the Visual Studio IDE you can either do it globally (so all your future projects will get this information) or locally (so only for you current project). The good part is that at runtime only the DLL is required.
#Visual studio winforms image library windows
This is why when you make some DLLs in Windows you will also end up with some lib extension libraries. Nevertheless, they aren't static libraries. This information is stored inside lib files. It seems that the linker needs to know that where in the DLL to search for the data structure or function at the runtime. If you use the DLL system you must again specify all this, however now for a different reason. During the build the linker will look into these libraries and add the definitions and implementation of all used functions and data structures to the executable file. If you use the lib system you must set the path where the library files are and specify in which one of them to look. Tell to the linker from where to get the functions or data structures of OpenCV, when they are needed. You do this by showing it the header files.