Statically Link with the VC Runtime

[candera]

Background

A user requests on this thread that we statically link with the VC runtime to reduce the need to run the redist installer on a bunch of machines.

Acceptance Criteria

• ShadowSpawn no longer requires the VC redist to be installed first.

Tech Notes

It may be possible to statically link with the VC redist, in which case shadowspawn would become standalone. The issue with doing that is that Microsoft publishes security updates to the redist via Windows Update, and we wouldn't get those if we were statically linked. At that point, it would be on the user to download a new version that had the updated version included. Assuming that one of us notices the update and remembers to compile a new version.

Another possibility would be to do the work to remove the dependency on the VC redist. That work may be extensive in nature - no idea.

Our current priority for this issue is low. Comments, however, are welcome.

[candera]

Comment from a mailing list reader:

We can add 3(6) more configurations to project file 
Release-Static-XP ....
We just need to change C++ -> Code Generation -> Runtime Library