Nintynuts

Duplicate of #22

Thanks for the feedback. Response inline. > 1. We aren't certain that we would want to update to v142 toolset. We want to still be compatible with the handful of...

I understand that you don't have lots of time, but maybe not doing PRs is the reason the code got a bit messy? It's a really useful process, and it's...

@bo3b That does fill in some gaps, although some of it is still a bit outside my understanding, thanks. I don't know which time zone you're in and what platform(s)...

It turns out newer versions of VS do allow you to install older compilers independently, so I've done that and restored all the projects to v141. I've also moved the...

> I got a chance to test the DX9 project, and it seems to mostly work. When I do a full Build of the DirectX9 project on master branch, it...

Thanks for the insight @DarkStarSword. It sounds like after this hole in HLSL decompilation is fixed there will be quite of bit of work before DX9 3DM is reliably usable....

@bo3b - I've not touched the DX9 fonts as that has nothing to do with the HLSL decompiler, but maybe look at [this](https://github.com/microsoft/DirectXTK/issues/215)? - DX9 debugging being XP exclusive is...

@DarkStarSword I can restore the `includes` and `internal_includes` folders, although it should be noted we are including from both. Just makes consuming it messier. I need to get a better...

@davegl1234 Sounds worth discussing/looking at, but maybe not in this PR? #158 @DarkStarSword @bo3b Also made this for Fonts #157