NShader - HLSL - GLSL - CG - Shader Syntax Highlighter AddIn for Visual Studio

Commented Unassigned: visual studio 2010 - nshader fails to uninstall [10850]

alexandre_mutel — Tue, 07 May 2013 05:28:51 GMT

nshader has stopped working in visual studio 2010. Through the extension manager the option to disable or uninstall is blanked out.

I also have visual studio 2012 installed but am using the older compiler.

I cannot remove this software, very annoying
Comments: This apply to VS2010 as well

Commented Unassigned: visual studio 2010 - nshader fails to uninstall [10850]

alexandre_mutel — Tue, 07 May 2013 05:28:24 GMT

Created Unassigned: visual studio 2010 - nshader fails to uninstall [10850]

Culzean — Sat, 04 May 2013 19:23:58 GMT

Updated Wiki: Home

alexandre_mutel — Thu, 07 Feb 2013 03:09:56 GMT

Project Description

NShader is an extension to Visual Studio 2008/2010 that provides syntax highlighting for various shader languages including HLSL - GLSL - CG..

News

19 June 2012, NShader 1.3 - VS2010 + VS2012. Add support for VS2012 and VS2010. Note for VS2012: in case highlighting is not working, follows the steps:
- Remove the registry entry: HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0\FontAndColors\Cache and HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0_Config
- Remove all lines using "fx" or "hlsl" in file C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\CommonExtensions\Microsoft\VC\VC_Pkg_Core_Registration.pkgdef .
28 June 2011, Warning If NVidia Parallel NSight is installed, It will override fx, hlsl and glsl extensions to C++ syntax highlighting. In order to use NShader with those extensions, check How to use NShader syntax highlighting with NSight
29 Jan 2011, NShader 1.2 - VS2010. This release is only working with VS2010 and includes the following bugfix/enhancement:

* Bugfix when using NShader from a user domain account
* Bugfix on preprocessor directive that were not highlighted correctly
* Bugfix for strings. Strings are now highlighted correctly
* Add new GLSL keywords 4.0
* Add new HLSL keywords (Interpolation Modifiers, register modifier)
* Add *.fxh files extension for HLSL files
* Add *.geom files extension for GLSL files

16 May 2010, NShader 1.1 - VS2008. This release is introducing support for Visual Studio 2010 and includes some hlsl bugfixes (add new hlsl file extensions and keyword from Shader Model 5.0)
1st Oct 2009, NShader 1.0 initial release!. This release supports basic highlighting for HLSL, GLSL and CG under Visual Studio 2008.

Features

Basic highlighting for HLSL, GLSL, CG languages (comment, number, floats, keywords, builtin functions)
Additional special highlighting per language : Semantics for HLSL, builin variables for GLSL.

NShader uses a specific shader language highlighting based on the following file extensions :

.fx, .fxh, .hlsl, .vsh, .psh files : HLSL syntax highlighter.
.glsl, .frag, .vert, .fp, .vp, .geom files : GLSL syntax highlighter.
.cg, .cgfx, files : CG syntax highlighter.

Requirement

Visual Studio 2008 or Visual Studio 2010 (at least tested on Pro version). Express editions are not supported as they don't allow community addins.
.NET Runtime 3.5 on Windows (and 4.0 for Visual Studio 2010) : Microsoft .NET 3.5 Runtime.

Limitations

The CG syntax highlighter is using the same HLSL syntax highlighter (they have similar keywords).
No syntax analyzing and checking. NShader only use a basic tokenizer to extract keywords.
No braces/bracket matching
No completion
No formatting

Contribute

You are welcome to contribute to this project.
A non exhaustive list of possible directions to extend this project could be:

Add braces/bracket matching
Add code formatting
Add compilation checking (using fxc...etc.).

Screenshots

Contact

Go to NShader to have more information. Leave a message in the discussion tab.

Contact author: alexandre_mutel <at> yahoo <dot> fr
Contact on Gamedev Forum: AlexandreMutel
Blog : Code4k

New Post: Visual Studio 2012 RC - Dark colour theme issue

GeorgeR — Thu, 07 Feb 2013 03:08:31 GMT

I did this a while ago. I can only confirm it works for vs2010.

http://studiostyl.es/schemes/son-of-obsidian-resharper-nshader

Updated Release: NShader 1.3 - VS2010 + VS2012 (Jun 19, 2012)

alexandre_mutel — Fri, 18 Jan 2013 13:06:08 GMT

This is a small maintenance release to support new VS2012 as well as VS2010.

This release is also fixing the issue The "Comment Selection" include the first line after the selection

If the new NShader version doesn't highlight your shader, you can try to:

Remove the registry entry: HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0\FontAndColors\Cache and HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0_Config
Remove all lines using "fx" or "hlsl" in file C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\CommonExtensions\Microsoft\VC\VC_Pkg_Core_Registration.pkgdef

Released: NShader 1.3 - VS2010 + VS2012 (Jun 19, 2012)

Fri, 18 Jan 2013 13:06:08 GMT

Remove the registry entry: HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0\FontAndColors\Cache and HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0_Config
Remove all lines using "fx" or "hlsl" in file C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\CommonExtensions\Microsoft\VC\VC_Pkg_Core_Registration.pkgdef

Updated Release: NShader 1.3 - VS2010 + VS2012 (Jun 19, 2012)

alexandre_mutel — Fri, 18 Jan 2013 13:05:05 GMT

Remove the registry entry: HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0\FontAndColors\Cache and HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0_Config
Remove all lines using "fx" or "hlsl" in file C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\CommonExtensions\Microsoft\VC\VC_Pkg_Core_Registration.pkgdef

New Post: Crashing my Visual Studio

alexandre_mutel — Wed, 12 Dec 2012 13:46:35 GMT

Sorry, never had this issue before, so I don't know what is the source of the problem. I have already added some extensions like this in NShader without getting any problem, so It is more likely a configuration problem in your VS.

New Post: Crashing my Visual Studio

CyberMew — Tue, 11 Dec 2012 16:26:03 GMT

Oh I mean "to no avail", sorry if I was unclear on that.

Yea somehow VisualAssistX was causing it to hang.

However one issue still remains. So I delete that tree, disabled VAX and relaunched my project. No hanging. I opened up my .vert file, and it no longers show anything at all for that file. Pure blueness. No text, nothing, just a tab as usual. Any idea why that happened and how to fix it?

New Post: Crashing my Visual Studio

alexandre_mutel — Tue, 11 Dec 2012 08:05:09 GMT

I don't understand this "tried an uninstall, no avail, reinstall". What is "no avail"?

NShader in itself should work well, but VS extensions can conflicts between them, so when you say that this is NShader that is crashing your solution, this could be actually another extension that is interfering with NShader. The only thing I know is that NShader is a pretty simple extension that doesn't mess VS or perform any advanced trick with VS, so it is unlikely to crash. I wouldn't say the same for NSight, ReSharper, VisualAssist...etc. that are complex beast touching several parts of VS and often interfering with other extensions. So if you have a crash, it is not 100% sure that this is NShader, but could be another plugin or a combination of them.

The registry key "10.0_Config" is rebuilt by VS201x when you launch it (unless nothing changed), so you can safely remote it. It is basically rebuilt from 10.0 and all pkgdefs around the disks.

Also ,uninstalling NShader is just a matter of going to the extension manager and press uninstall button, If the button is disabled, you just have to run VS201x in administrator mode.

New Post: Crashing my Visual Studio

CyberMew — Tue, 11 Dec 2012 06:24:37 GMT

I followed the steps here to add extensions since you didn't have time to add in a configurable file/option: http://nshader.codeplex.com/discussions/394745

Because I added some extensions to that pkgdef, deleted the Cache tree, and now what I have is a crashing solution (or rather in a permanent loop) if the associated file is opened.

I removed those extensions in pkgdef, but your plugin is still crashing my Visual Studio. Tried an uninstall, no avail, reinstall, same thing.

I only omitted this part and was wondering is it safe to delete the whole tree (and it subtrees) of

HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0_Config

I would appreciate it if you can post a FULL manual uninstall of your plugin. I have multiple customised settings of plugins and do not wish to do a reinstall of Visual Studio. I am using 1.3 of NShader.

Updated Wiki: Home

alexandre_mutel — Fri, 30 Nov 2012 13:55:42 GMT

Project Description

NShader is an extension to Visual Studio 2008/2010 that provides syntax highlighting for various shader languages including HLSL - GLSL - CG..

News

19 June 2012, NShader 1.3 - VS2010 + VS2012. Add support for VS2012 and VS2010.
28 June 2011, Warning If NVidia Parallel NSight is installed, It will override fx, hlsl and glsl extensions to C++ syntax highlighting. In order to use NShader with those extensions, check How to use NShader syntax highlighting with NSight
29 Jan 2011, NShader 1.2 - VS2010. This release is only working with VS2010 and includes the following bugfix/enhancement:

16 May 2010, NShader 1.1 - VS2008. This release is introducing support for Visual Studio 2010 and includes some hlsl bugfixes (add new hlsl file extensions and keyword from Shader Model 5.0)
1st Oct 2009, NShader 1.0 initial release!. This release supports basic highlighting for HLSL, GLSL and CG under Visual Studio 2008.

Features

Basic highlighting for HLSL, GLSL, CG languages (comment, number, floats, keywords, builtin functions)
Additional special highlighting per language : Semantics for HLSL, builin variables for GLSL.

NShader uses a specific shader language highlighting based on the following file extensions :

.fx, .fxh, .hlsl, .vsh, .psh files : HLSL syntax highlighter.
.glsl, .frag, .vert, .fp, .vp, .geom files : GLSL syntax highlighter.
.cg, .cgfx, files : CG syntax highlighter.

Requirement

Visual Studio 2008 or Visual Studio 2010 (at least tested on Pro version). Express editions are not supported as they don't allow community addins.
.NET Runtime 3.5 on Windows (and 4.0 for Visual Studio 2010) : Microsoft .NET 3.5 Runtime.

Limitations

The CG syntax highlighter is using the same HLSL syntax highlighter (they have similar keywords).
No syntax analyzing and checking. NShader only use a basic tokenizer to extract keywords.
No braces/bracket matching
No completion
No formatting

Contribute

You are welcome to contribute to this project.
A non exhaustive list of possible directions to extend this project could be:

Add braces/bracket matching
Add code formatting
Add compilation checking (using fxc...etc.).

Screenshots

Contact

Go to NShader to have more information. Leave a message in the discussion tab.

Contact author: alexandre_mutel <at> yahoo <dot> fr
Contact on Gamedev Forum: AlexandreMutel
Blog : Code4k

New Post: Can't uninstall v1.3 and the highligting function is not working too

alexandre_mutel — Fri, 02 Nov 2012 14:24:17 GMT

This was for 2008 not for 2010.

In order to remove NShader, It should be removable from extension manager if you are running your VS2012 in administrator mode.

New Post: Can't uninstall v1.3 and the highligting function is not working too

jeng — Fri, 02 Nov 2012 14:21:42 GMT

NShader 1.3 for VS2010 not highlighting and I can't remove it.

About manually remove NShader: http://nshader.codeplex.com/workitem/6701,

but I did't find the "32bits : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{24E159B3-9D95-48CC-8A29-C48EB4184487}"

Created Issue: Cg with VS 2012 [10849]

finlaybob — Thu, 01 Nov 2012 13:21:17 GMT

Syntax highlighting does not seem to work for me in VS2012 for Cg shaders.

Both *.cg and *.cgfx extensions do not highlight.

GLSL and HLSL both work.

I've disabled all other addons and just left NShader but to no avail.

New Post: Visual Studio 2012 RC - Dark colour theme issue

jsmars — Wed, 24 Oct 2012 11:38:42 GMT

I'm in the same situation as cmdalbem. I wish I could use this with the dark color theme. Everytime I work on shaders for a longer while I end up having to convert back to a light theme.. mainly because the the dark blue/red is hard to read. Wish I could just edit them manually, or that there was a "dark version" of the nshader.. maybe based on the immensely popular dark theme SonOfObsidian :)

New Post: Support for .shader file extension

hrlarsen — Thu, 20 Sep 2012 19:57:00 GMT

Thank you alexandre this works like a charm :)

New Post: Support for .shader file extension

alexandre_mutel — Thu, 20 Sep 2012 13:43:26 GMT

1) Close your VS2012 (or VS2010)

2) Edit the NShader.pkgdef located in YOUR_DRIVE:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Extensions\a_cryptic_subfolder (search for it in extensions directory). 10.0 for VS2010 version.

3) Add the following line to NShader.pkgdef (where other extensions are):

[$RootKey$\Languages\File Extensions\.shader]
@="{4c554917-0eb7-3742-9f6b-f2f529fc6729}"

4) Then to be sure that everything is going to be highlighted correctly, open a registry and remove the following registry (be careful!):

HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0\FontAndColors\Cache

HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0_Config

Launch VS and It should be ok.

New Post: Support for .shader file extension

retypeNick — Wed, 19 Sep 2012 17:32:00 GMT

This would be very nice.

There are some suggestoins how to get it work, which won't work for me:

http://forum.unity3d.com/threads/108995-Tutorial-How-to-use-NShader-with-Unity-shaders