Tim Jones

I hit this issue, and found that changing the `` of the test runner project from `net5.0` to `net471` fixed it.

Note that the state property names aren't necessarily keywords - but at least some kind of semantic highlighting is appropriate.

Does the problem still happen if you remove the "DiscordRPforVSPackage" extension that is mentioned in the error message?

Hi @zongsheng-zhao - sorry for the big delay in replying. Thank you for taking the time to prepare this PR! I think I want to go another way though (#235)...

With `DEPTH_RANGE_ZERO_TO_ONE`, did you mean that would be a C# `#define`? A more discoverable API might be to have it as a property on the `[VertexShader]` attribute? It could be...

Thanks for logging this here. This issue is related to #8 - I need to add a way to have project-specific settings, including additional include directories and macros. Another option...

Some info on reading C++ file properties: - https://blogs.msdn.microsoft.com/visualstudio/2010/01/14/how-to-readwrite-the-new-visual-c-project-properties/ - https://msdn.microsoft.com/en-us/library/dn655034.aspx

Hi @Jasonchan35 - thanks for this! I tried to write a test for this but I don't think the implementation actually works: - `token.Kind` is never equal to `SyntaxKind.VariadicArgumentKeyword`. Instead...

I like the second option too. There's some potential for confusion, because HLSL at least already has a similar concept (`ddx_coarse` vs `ddx` vs `ddx_fine`), but good IntelliSense comments can...

Please could you try disabling all auto-formatting for HLSL - as in the attached screenshot - and see if it fixes the performance problem?