Skip to main content

JScript Editor Extensions for Visual Studio

While browsing through some Channel 9 videos, I discovered the following session:

Damian Edwards, a member of the ASP.NET team at Microsoft talks in this episode about the JScript Editor Extensions(Microsoft calls it JScript because Oracle owns the rights on the name JavaScript) and about what can be expected in Visual Studio vNext.

This JScript Editor Extensions bundles the following functionality:

  • Brace Matching

Adds support for automatically highlighting the matching opening or closing brace to the one currently at the cursor. Supports matching parenthesis: (), square brackets: [], and curly braces: {}. Braces in strings, comments and regular expression literals are ignored.

  • Outlining / Cold-folding

Adds support for automatically creating outlining regions for JScript blocks. Blocks are detected via opening and closing curly braces. Braces in strings, comments and regular expression literals are ignored.

  • Current Word Highlighting

Adds support for highlighting all instances of the word currently at the cursor.

  • IntelliSense Doc-Comments <para> Support

Adds support for the <para> element in JScript IntelliSense doc-comments to allow display of new lines in IntelliSense tooltips, e.g.

function hello(name) {
/// <summary>A great function
/// < para>Some info on a new line</para>
/// </summary>
/// <param name="name" type="String">The name to say hello to</param>
return "hello " + name;
}

Download the extension here: http://visualstudiogallery.msdn.microsoft.com/872d27ee-38c7-4a97-98dc-0d8a431cc2ed?SRC=Home

And if you want to know more about the improvements in the Visual Studio 11 JavaScript editor: http://www.asp.net/vnext/whats-new#_Toc303354500

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...