No color settings in VS 2015

[Lex-DRL]

The title is self-explanatory.
Just installed the latest release (2.4) of this ext to the VS 2015 - and there's no syntax highlighting at all. More importantly, no way to specify it manually because there are no "NShader – Type" settings under Tools > Options > Environment > Fonts and Colors.

Tried uninstalling and re-instaloing the ext, also tried version prior to VS 2017 support (2.1) - the same thing.

[samizzo]

Did you have a previous version of NShader installed, or any other shader syntax highlighters?

…

On 17 May 2017, at 6:40 pm, Lex Darlog ***@***.***> wrote: The title is self-explanatory. Just installed the latest release (2.4) of this ext to the VS 2015 - and there's no syntax highlighting at all. More importantly, no way to specify it manually because there are no "NShader – Type" settings under Tools > Options > Environment > Fonts and Colors. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[Lex-DRL]

I didn't have NShader installed in the current version of VS (2015 update 3).
But I may have tried it some time ago, when I was using VS 2013.
Anyway, prior to the installation of my currently used VS, I have manually cleaned up whatever I was able to find (any tracks of VS in Program Files, AppData and ProgramData, including Common* folders).

However, I tried the following extension (installed and uninstalled it) before installing your version of NShader:
https://marketplace.visualstudio.com/items?itemName=MarcinODev.ShaderUnitySupport

[Lex-DRL]

I can try installing your extension on the "pure" VS, if you tell me how I can do that. What files/folders on my system disk I need to remove to clean up VS for this ext?

[samizzo]

I'm not totally sure what to do aside from just uninstalling the extension from within VS. You could try extrapolating the instructions here to NShader.

[Lex-DRL]

That topic is about another issue: uninstallig ah extension when it can't do it properly from GUI in VS. I don't have this issue. I have successfully uninstalled that extention before installing yours.

It may have left some of it's settings somewhere in the OS, but I don't know where (if it did).

[Lex-DRL]

I've spent entire day uninstalling VS, .NET framework and VC++ redistributables and then cleaning my system from any garbage left after it. I've removed everything I could find (both on the system disk and in the registry). I searched for any mentions of VS, NSHADER, just "shader" and Resharper.

After it, I've installed from scratch latest .NET framework + VS 2017 (Community).
And now, on the perfectly clean VS, I'm installing your version of NSHADER.

But still, there are no color settings.
I do have "Shader Language" options block under "Text Editor" group. But there's not even a single option labled "NSHADER - ..." under "Environment" group.

I'm desparate.
Are you sure it works in VS 2015/2017?

[samizzo]

I'm sorry to hear that. I've been using it in VS2015 and 2017 on my home machine, and other people have reported that it works as well. However, I have just installed VS2017 on my work machine and now I see that it's not working, so at least I have a repro case now! I haven't yet figured out what's going on; the extension is correctly tokenising the file and returning colours for tokens, but VS doesn't seem to be using those colours when rendering the text.

[samizzo]

In the meantime, why don't you give HLSL Tools a try?

[Lex-DRL]

Oh, I just didn't know about that ext.
But it seems great. Thanks a lot!

[samizzo]

Yeah I think it's better than NShader actually. It has a lot of extra features like navigation and statement completion. I think the syntax colouring might not be quite as extensive as NShader but it works!

[blair0011]

I have a fix for this. It seems that the visxmanifest only allows MPF versions 12 & 13. I am on 16 (aka. Visual Studio 2017). If you open up the range to be [12.0,) and recompile everything works. I had to figure out this fix because HLSL Tools doesn't do glsl compute shaders well, and I really need something to work for those.

[samizzo]

Ahh thank you very much! I'll make this change and push out a new build.

…

On 21 Jul 2017, at 6:22 am, blair0011 ***@***.***> wrote: I have a fix for this. It seems that the visxmanifest only allows MPF versions 12 & 13. I am on 16 (aka. Visual Studio 2017). If you open up the range to be [12.0,) and recompile everything works. I had to figure out this fix because HLSL Tools doesn't do glsl compute shaders well, and I really need something to work for those. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.