Fixing code for MSVC

[NotRequiem]

Compiler flags:

Compilation errors found in the previous version:

Fixed in the FIRST COMMIT

To see all the changes made in the first commit, you should click on "Ignore whitespaces", like this:

Link: https://github.com/NotRequiem/VMAware/commit/600d8b79f6be5f8f90382adf5ee4981631a0dfd7?diff=unified&w=1

Compilation warnings found in the previous version:

Fixed some IntelliSense warnings about buffer overruns, variants not being initialized with VariantInit and 'dll could be 0'.

Fixed in the SECOND COMMIT

How did I fix

Normally in large source files, when fixing errors in a source file using Visual Studio, you may find no errors when you finish. But if you copy and paste the same source code with the same compiler flags in other project, using Visual Studio, more errors/warnings may be shown. Example of pasting the same code in another project:

So, if you constantly fix errors and warnings until you find no errors in other projects, then it will compile succesfully for everyone.

In the third commit, I fix every new warning/error that pops up whenever I try to paste the code in other projects with the same compiler and compiler flags

Link: https://github.com/NotRequiem/VMAware/commit/ccfd50e4eefd3dc2c654f2752e14e05627949ff2?diff=unified&w=0

Remember that most issues with compilation errors are because Unicode compatibility issues. Therefore, you need to enfornce "Use Unicode Character Set"

Using unicode character set:

Not using it:

Testing

The final code works for C++ 17:

The final code works for C++ 14:

The final code compiles correctly on other projects:

Final result:

[NotRequiem]

The compilation error in the build test is because the unicode character set that I have explained, "Remember that most issues with compilation errors are because Unicode compatibility issues. Therefore, you need to enfornce "Use Unicode Character Set"". Its just one problematic line thought.

[kernelwernel]

oh wow, that’s a massive PR! I was sleeping until I heard an email notification on my phone from github about this.

I’ll go back to sleep right now since my head is feeling fuzzy at the moment but I will review it whenever I wake up.

I genuinely appreciate the PRs you’ve made recently, it really means a lot :)

[kernelwernel]

hey, i made a PR on your fork here a few days ago. Just letting you know

[kernelwernel]

fixed the conflict in this PR.

[NotRequiem]

nice, I will review the code when I have time, everything seems ok tho and I'm agree with everything you mentioned, including the indentation part

[kernelwernel]

nice, I will review the code when I have time, everything seems ok tho and I'm agree with everything you mentioned, including the indentation part

take your time, there’s no rush :) also, i do agree with the way you formatted preprocessor conditions, it looks better and clearer now

[NotRequiem]

Ignore the compatibility issue with WCHAR and char *:

Did you get the same IntelliSense errors?

[kernelwernel]

Ignore the compatibility issue with WCHAR and char *:

Did you get the same IntelliSense errors?

i have for the preprocessor thing but not for the other errors. I'm using /Wall /std:c++20 flags if that matters. Also, is it possible if you can merge my pull request if possible?

[NotRequiem]

Done, pull request merged.

[kernelwernel]

i'll try to get it fixed on my end, thanks for the effort btw! :)

If you want to contribute more then feel free to share new detection ideas, there's no stupid suggestion.

EDIT: fixed here, that was a mess up on my part

[NotRequiem]

perfect, I'll keep contributing to this project, I like it a lot

Thanks for your effors too, good job