This file must be the first file included by all cpp files that are built in any library in the JetByte Tools suite. This file contains global #defines that affect how the code is built
There are various issues with using various early versions of the platform SDK (or using VC6 and no platform SDK) with the winsock2.h header. This is part of a crude attempt to avoid the problems. It doesn't work very well..
There are various issues with using mscoree.h with VC6 as the checks to see if a certain version of the platform SDK is being used is wrong... See here for more details. This header file wraps the real mscoree.h and works around these problems, turns off some annoying mscoree.h specific warnings. If the real mscoree.h can't be found then you may not have set the enviroment variable to the root of the .Net SDK that you want to use, this is usually only a problem with a VC6 build
It was, at some time, possible to build some of the code in VC6 without a copy of the Platform SDK installed. This becomes less and less likely to work as time goes on. Building with VC6 and without a copy of the Platform SDK is no longer a supported option, but it may work. See here for more details on how to get the latest copy of the Platform SDK
This file provides backwards compatibility macros for the secure CRT functions that Microsoft began supplying starting with VS2005. This allows us to work as if the secure CRT was always available... See here for more details
This file provides some macros that allow pragma TODO("message") to give a clickable message in the build window from within Visual Studio. Note that all of these messages only show up in debug builds
If you're building with the JetByte Tools libraries and mixing the code with MFC then you may have problems. See here for more details on the likely problems. Including this file is likely to fix those problems as it fixes up the library link order. You only have to include this file once, usually in the 'main()' .cpp file
This file deals with warning level setting and masking of known safe warnings for either STLPort or native Microsoft STL. It's automatically included in all files because they include Admin.h
There are various issues with using various early versions of the platform SDK (or using VC6 and no platform SDK) with the winsock2.h header. This is part of a crude attempt to avoid the problems