#define WIN32_LEAN_AND_MEAN
#include <windows.h>
#include <stdio.h>
// > this file: test_gettickcount.c
// > cl version: Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 16.00.40219.01 for 80x86
// > vcvars32.bat; cl test_gettickcount.c; test_gettickcount.exe
// 4174243
int main () {
printf("%d", (int) GetTickCount());
}
Why stick with VC++6 if you don't mind us asking?
Heh, actually, VB6 is being dropped after windows 8, so it won't be around forever.
Linux now fully supports compiling and running VB.Net through mono, so VB.Net very easily has more compatibility than VB6. I can run VB.Net code, but not your terrible VB6 code (and VB6 is a very very terrible language, at least VB.Net has .Net access...).
As far as being bloated, the .Net framework is a system level thing with hooks in PowerShell, VB, C#, etc. It is not really fair to call that bloated, it would be like calling libc bloated: Almost every feature of it is used in at least one program, so any "bloat" is perfectly justified because of how much use it gets, and how well it gets its job done.
And .Net does not really take hours to install considering windows comes with it and it is needed for core windows functionality, or the fact that it installed on my XP box in 10 minutes.
And yeah, XP supports VB.Net, and last I checked something like 70% of the planet was running it, so you have no justification for using VB6 for compatibility.
I am not saying you have to move to VB.Net, but don't expect any help for such an outdated API.
Extend all I have said to VC++ 6 except for the horrible language bit, afaik VC++ 6 is still C, so the language itself is not all that terrible, just horribly outdated.