Marcel Raad 16c1e444f3 VS projects: use Unicode for VC10+ ... All Windows APIs have been natively UTF-16 since Windows 2000 and the non-Unicode variants are just wrappers around them. Only Windows 9x doesn't understand Unicode without the UnicoWS DLL. As later Visual Studio versions cannot target Windows 9x anyway, using the ANSI API doesn't really have any benefit there. This avoids issues like KNOWN_BUGS 6.5. Ref: https://github.com/curl/curl/issues/2120 Closes https://github.com/curl/curl/pull/3720		2019-04-04 11:19:19 +02:00
..
VC6	VC: Add crypt32.lib to Visual Sudio project template files	2016-06-22 10:57:55 +02:00
VC7	VC: Add crypt32.lib to Visual Sudio project template files	2016-06-22 10:57:55 +02:00
VC7.1	VC: Add crypt32.lib to Visual Sudio project template files	2016-06-22 10:57:55 +02:00
VC8	VC: Add crypt32.lib to Visual Sudio project template files	2016-06-22 10:57:55 +02:00
VC9	VS projects: add USE_IPV6	2018-10-19 09:23:15 +02:00
VC10	VS projects: use Unicode for VC10+	2019-04-04 11:19:19 +02:00
VC11	VS projects: use Unicode for VC10+	2019-04-04 11:19:19 +02:00
VC12	VS projects: use Unicode for VC10+	2019-04-04 11:19:19 +02:00
VC14	VS projects: use Unicode for VC10+	2019-04-04 11:19:19 +02:00
VC15	VS projects: use Unicode for VC10+	2019-04-04 11:19:19 +02:00
.gitattributes	build: check out *.sln files with Windows line endings	2017-08-10 09:11:46 +02:00
.gitignore	projects/Windows/.gitignore: ignore generated files for release	2015-09-03 23:34:53 +02:00