Daniel Scherzer

Any startup/initialization problems with VS 17.3 and the extension? Otherwise I would close this issue.

Thanks for the feedback! I'm busy till mid of February. So this will take some time... Feel free to make a pull request if you did it yourself in the...

Hi! Thanks for your feedback! I can reconstruct this behaviour. First: if you change the file extensions you have to restart VS Studio. After this the frag and vert extensions...

Leave it open! Thanks!

Thanks for your feedback! If I understand you correctly you suggest to integrate the C++ Glslang component into the extension. I think this is indeed a good way to move...

Thanks for your feedback! Could you please try other shader extensions, like `.frag` (More discussion on this topic in https://github.com/danielscherzer/GLSL/issues/32) if those are at least working.

Sorry! I did not understand your original message correctly! The trouble with `.vsh` is discussed in issue #32 Why `.glsl` is not working for you is unknown to me. Could...

Hm the only extension that could make trouble is the spirv one, but I after installing it myself, I have no problems with `glsl`. I use Microsoft Visual Studio Enterprise...

Thanks for finding the problem! So you still could use CUDA and NSight if you choose another extension instead of `.glsl`? I did not make the glsl keyword definition user...

new version with your additions