boekabart opened the ticket and wrote:

In Visual Studio, you 'need' the ottd useful set in order to compile. Until now, you have to make sure the include- and library folders are in your global include directories OR you have to manually add them to the vcproj file for every working copy (annoying when making patches, always need to remove those manually).

Suggested solution:
"* Add $(OTTD_USEFUL)win32\include (and the likes for win64/shared) to AdditionalIncludeDirectories, and AdditionalLibraryDirectories="$(OTTD_USEFUL)win32\libary" (and the likes for win64) to each of the project configurations.
* OTTD_USEFUL may be defined, absolute or relative path, including trailing backslash"

Rationale:
* Current deployments don't break. If OTTD_USEFUL is empty, it just won't find the (relative!) folders like win32\include, win64\library, and they will be conveniently ignored.
* Users that have multiple different versions of libpng or others on their system, can have each project reference his own correct one. No global include directories.
* If there is a global include, the one listed in the project goes first. So, global can list to another one than the one openttd uses.
* Users can have multiple working copies of OTTD src, with 1 useful for all (absolute path) or 1 useful per WC if they want (relative path)
* No more local changes to project files necessary.

Reported version: trunk
Operating system: Windows

This issue was imported from FlySpray: https://bugs.openttd.org/task/3269