Add crypt32.lib to Visual Studio project template files

[JDepooter]

Similar to #849, this pull request fixes the generated Visual Studio project files. They now link in crypt32.lib when libcurl is built with schannel. This is required following #822.

[mback2k]

Maybe the schannel.c code could be updated to check for crypt32.lib instead of requiring it per default, similar to https://github.com/libssh2/libssh2/blob/master/src/wincng.c#L54.

[mback2k]

@captain-caveman2k Would you mind taking a look at this pull-request? I think it is fine, besides my previous comment which will mainly affect the autotools-based builds.

[captain-caveman2k]

No problem @mback2k.

Do you think it is better to try and use the #pragma fix instead like libssh2 does?

[mback2k]

@captain-caveman2k It might be, but I think for curl it would probably be more logical to use the same consistent approach as for other libraries. If we were to use the #pragma fix then we should probably move all linked libraries to that approach. What do you think?

[bagder]

We can't wait anymore for the fix. I merged this and if we want it improved, we can do that from here.

[mback2k]

Thanks @bagder. But I am still wondering how it worked for Win CE before, because the specific parts for that platform already used crypt32 functions:

curl/lib/vtls/schannel.c

Line 1532 in 91697d2

if(!CertGetCertificateChain(NULL,

[bagder]

The Win CE users have always had a busload of various 3rd party additions and necessary "hacks" to build and run curl so maybe they just also then added that lib. It wouldn't surprise me.