search

oblitum / Interception

The Interception API aims to build a portable programming interface that allows one to intercept and control a range of input devices.
http://oblita.com/interception
1.33k stars 271 forks source link

Update WDK with Integration with Visual Studio 2015? #39

Closed YenForYang closed 7 years ago

YenForYang commented 7 years ago

I can't seem to figure out how to "convert" the command line "buildit" scripts to work with the newer WDK (integrated with Visual Studio 2015). Is there any way you could give "solutions" (in both meanings of the word I guess, solution and *.sln) for the library/samples? I think Microsoft might've deprecated the older build command.

oblitum commented 7 years ago

I have some plans on upgrading, but I would simply avoid anything Visual Studio related. I don't like it and the solution files are simply a hassle to deal with, the simple build mechanism as it's now is much better, in fact, I've moved out from VS solution files which I used to use formerly.

If there's any upgrade route, it will be through Enterprise WDK, which would maintain a simple build procedure through the command line.

YenForYang commented 7 years ago

I looked at Enterprise WDK as well and it seems similar to WDK 7.1--how much would have to be changed for EWDK to work with the sources projects right now?

Unrelated question: if you are avoiding anything Visual Studio related, I'm assuming you don't use Visual Studio to code C++, right? That is, do you use Visual Studio (for C++)? Or are you just a text editor kind of person (vim?), lol.

oblitum commented 7 years ago

It shouldn't take much to move to EWDK but I'm not look into this now as WDK 7.1 still works fine. I'm still able to download, install and use WDK 7.1 on a Windows 10 machine.

caps2esc exist for a reason: vi. I've long moved out from Visual Studio for good. I just use Vim, with some goodies when possible: