Merge branch 'master' into consistent-line-endings

README.md

@@ -47,8 +47,4 @@ code .
 
 You can open any of the Markdown files and see a preview with the **Open Preview to the Side** button in the upper right of the editor.
 
-![Markdown Preview Button](images/MDPreviewButton.png)
-
-### Images
-
-You should minify new images you put into the repository. You can run the `gulp minify-images` script to minify all the images in the repository.
+![Markdown Preview Button](images/MDPreviewButton.png)

blogs/2016/02/01/introducing_insiders_build.md

@@ -3,7 +3,7 @@ Order:
 TOCTitle: The Insiders Build
 PageTitle: Introducing the Insiders Build
 MetaDescription: insiders build
-MetaSocialImage: 2016_11_30_opengraph_insiders.png
+MetaSocialImage: /assets/blogs/2016/02/01/opengraph_insiders.png
 Date: 2016-02-01
 ShortDescription: VS Code has its roots in the web (built using TypeScript and Node.js) and one thing we love about cloud based applications is that they are always up to date. Update the service and all of your users are instantly on the latest fixes and features, with no user interaction.
 Author: Chris Dias
@@ -23,7 +23,7 @@ There were two shortcomings to this model. First, you needed to join the “Insi
 
 With the open sourcing of VS Code in November, we are retiring the Insiders Program. With the upcoming January 2016 release, we are introducing a new Insiders build that installs side by side with the monthly, stable VS Code release.
 
-![Insiders and Stable, side by side, don't worry, the green icon is temporary](2016_02_01_insiders_build_icon.png)
+![Insiders and Stable, side by side, don't worry, the green icon is temporary](insiders_build_icon.png)
 
 No longer do you need to manage settings to switch between the two. The Insiders build is a separate installation with isolated settings, extensions, and configurations. This does mean that you will need to configure both and install your favorite extensions into each, but once you’ve done this, trying out new features (and giving us feedback!) is easier than ever.
 

blogs/2016/02/23/introducing-chrome-debugger-for-vs-code.md

@@ -18,7 +18,7 @@ Our Chrome Debugger allows front-end developers to debug their client-side JavaS
 
 <br />
 
-![Demo](2016_02_23_chrome-debugger-demo.gif)
+![Demo](chrome-debugger-demo.gif)
 
 ## How does it work?
 
@@ -30,7 +30,7 @@ For now, Chrome needs to be started with remote debugging enabled, and only supp
 
 ## To get started
 
-To get started, you simply open the Command Palette (`kb(workbench.action.showCommands)`) inside VS Code and type `ext install` to run the `Extensions: Install Extension` command.  When the extension list appears, type 'chrome' to filter the list and install the `Debugger for Chrome` extension.  You'll then create a launch-configuration file which we explain in detail in our README [right here](https://github.com/Microsoft/vscode-chrome-debug).
+To get started, open the **Extensions** view (`kb(workbench.view.extensions)`).  When the extension list appears, type 'chrome' to filter the list and install the `Debugger for Chrome` extension.  You'll then create a launch-configuration file which we explain in detail in our README [right here](https://github.com/Microsoft/vscode-chrome-debug).
 
 You can either setup VS Code to connect to an already running Chrome instance or simply start a new one with remote debugging enabled, but read more about that in our [README](https://github.com/Microsoft/vscode-chrome-debug).
 

blogs/2016/03/11/ExtensionsRoundup.md

@@ -42,7 +42,7 @@ Create a `launch.json` file in `.vscode` folder and add the following:
           "name": "Ruby Debug",
           "type": "Ruby",
           "request": "launch",
-          "program": "${workspaceRoot}/hello_world.rb",
+          "program": "${workspaceFolder}/hello_world.rb",
           "stopOnEntry": false
       }
   ]
@@ -53,19 +53,19 @@ Create a `launch.json` file in `.vscode` folder and add the following:
 
 Below is an example session debugging a simple Hello World Ruby script. You can see setting a breakpoint, starting the debugger, hitting the breakpoint, and single stepping through the code.
 
-![Ruby Debugging](2016_03_11_ruby_debugging.gif)
+![Ruby Debugging](ruby_debugging.gif)
 
 ## yo by Sam Verschueren
 
 This extension lets you use the Yeoman scaffolding tool from within VS Code in the Command Palette. Your installed Yeoman generators are displayed in a drop down and you answer the Yeoman terminal prompts right from within VS Code. [See more details at the Marketplace](https://marketplace.visualstudio.com/items?itemName=samverschueren.yo).
 
-![Yo Demo](2016_03_11_yo_demo.gif)
+![Yo Demo](yo_demo.gif)
 
 ## change-case by wmaurer
 
 Change the case of the currently selected word or selection. This [extension](https://marketplace.visualstudio.com/items?itemName=wmaurer.change-case) is implemented as a wrapper around the [node-change-case](https://github.com/blakeembrey/node-change-case) npm module.
 
-![change-case demo](2016_03_11_change-case_demo.gif)
+![change-case demo](change-case_demo.gif)
 
 ## Subscribe
 

blogs/2016/04/14/vscode-1.0.md

@@ -6,14 +6,14 @@ MetaDescription: Visual Studio Code releases 1.0.
 Date: 2016-04-14
 ShortDescription: Visual Studio Code releases 1.0.
 Author: PJ Meyer
-MetaSocialImage: 2016_04_14_header.png
+MetaSocialImage: /assets/blogs/2016/04/14/header.png
 ---
 
 # Visual Studio Code 1.0!
 
 April 14, 2016 by The VS Code Team, [@code](https://twitter.com/code)
 
-![header graphic](2016_04_14_header.png)
+![header graphic](header.png)
 
 Today we’re very proud to release version 1.0 of Visual Studio Code. Since our initial launch one year ago, 2 million developers have installed VS Code. Today, we’re excited to report that more than 500,000 developers actively use VS Code each month.
 
@@ -27,7 +27,7 @@ And we have strived to make VS Code 1.0 a great editor for every developer. VS C
 
 We could not have reached this important milestone without the help of all our contributors. Since committing to doing development in the open less than four months ago, we’ve consumed over [300 pull requests](https://github.com/Microsoft/vscode/pulls?q=is%3Apr+is%3Aclosed).  Whether you created a PR, filed an issue, gave a thumbs up, tweeted, or simply used VS Code in your day-to-day, you’re a part of the team. **Thank you!**
 
-![installs graphic](2016_04_14_installs.png)
+![installs graphic](installs.png)
 
 ## The History of VS Code
 
@@ -51,7 +51,7 @@ Keeping our principle of using VS Code the way our customers do, we decided that
 
 And at the same time, we open-sourced the VS Code [repository](https://github.com/Microsoft/vscode) and many of our own extensions, and moved to developing Visual Studio Code in the open.
 
-![timeline graphic](2016_04_14_timeline.png)
+![timeline graphic](timeline.png)
 
 ## Being "1.0"
 
@@ -67,7 +67,7 @@ The community responded, with huge growth in the number of extensions and the wa
 
 Seeing the support and help the community has already poured into the product, the potential for VS Code has never been greater.
 
-<img src="/images/Hundreds-of-extensions.png" style="width: 69%;display: block;margin-left: auto;margin-right: auto">
+<img src="/assets/images/Hundreds-of-extensions.png" style="width: 69%;display: block;margin-left: auto;margin-right: auto">
 
 ## Looking Ahead
 

blogs/2016/05/04/extension-roundup-may.md

@@ -22,31 +22,31 @@ If you are new to VS Code extensions, check out the [docs](https://code.visualst
 
 The same folks who created the very popular [Debugger for Chrome](https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome) extension have published [Debugger for Edge](https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-edge) for the Microsoft Edge browser. They were able to reuse the same debugger using the [Chrome Debugger protocol](https://developer.chrome.com/devtools/docs/debugger-protocol). You can learn more about the details in their recent [blog post](https://blogs.windows.com/msedgedev/2016/04/27/introducing-edge-diagnostics-adapter/).
 
-![debugger for edge](2016_05_04_debugger-for-edge.gif)
+![debugger for edge](debugger-for-edge.gif)
 
 ## SVG Viewer by cssho
 
 >**Install:** Quick Open (`kb(workbench.action.quickOpen)`), paste `ext install vscode-svgviewer` and press `kbstyle(Enter)`.
 
 This highly rated extension lets you view Scalable Vector Graphics (SVG) right from within VS Code. [See more details in the Marketplace](https://marketplace.visualstudio.com/items?itemName=cssho.vscode-svgviewer).
 
-![SVG viewer](2016_05_04_svg-viewer.gif)
+![SVG viewer](svg-viewer.gif)
 
 ## CodeMetrics by Kiss Tamas
 
 >**Install:** Quick Open (`kb(workbench.action.quickOpen)`), paste `ext install vscode-codemetrics` and press `kbstyle(Enter)`.
 
 Curious if your TypeScript source code is getting a little too clever and hard for others to maintain? This [extension](https://marketplace.visualstudio.com/items?itemName=kisstkondoros.vscode-codemetrics) computes the complexity of your code and displays a rating in a CodeLens decoration in the editor. Clicking on the rating brings up the rules used to arrive at the complexity score.
 
-![complexity CodeLens](2016_05_04_complexity-codelens.gif)
+![complexity CodeLens](complexity-codelens.gif)
 
 ## npm IntelliSense by Christian Kohler
 
 >**Install:** Quick Open (`kb(workbench.action.quickOpen)`), paste `ext install npm-intellisense` and press `kbstyle(Enter)`.
 
 Bring quick auto completion into the editor for your workspace's npm modules with this handy [extension](https://marketplace.visualstudio.com/items?itemName=christian-kohler.npm-intellisense).
 
-![npm IntelliSense](2016_05_04_auto-complete.gif)
+![npm IntelliSense](auto-complete.gif)
 
 ## Let us know what extensions you're using
 

blogs/2016/05/23/evolution-of-insiders.md

@@ -3,7 +3,7 @@ Order:
 TOCTitle: Evolution of VS Code Insiders
 PageTitle: Evolution of VS Code Insiders
 MetaDescription: Evolution of the Visual Studio Code Insiders Build
-MetaSocialImage: 2016_11_30_opengraph_insiders.png
+MetaSocialImage: /assets/blogs/2016/11/30/opengraph_insiders.png
 Date: 2016-05-23
 ShortDescription: Evolution of the Insiders Build
 Author: Wade Anderson
@@ -17,7 +17,7 @@ Today over five thousand developers use the Visual Studio Code [Insiders Build](
 
 Initially, we released an Insiders build once per month, a few days before the Stable release. Over time, we increased the frequency of Insiders builds and today we ship new Insiders builds roughly once a week.
 
-![value prop of insiders](2016_05_16_value_props.svg)
+![value prop of insiders](value_props.svg)
 
 ## Nightly Builds
 

blogs/2016/06/27/common-language-protocol.md

@@ -1,32 +1,32 @@
 ---
 Order: 11
-TOCTitle: The Language Server Protocol 
-PageTitle: Common Language Server Protocol 
+TOCTitle: The Language Server Protocol
+PageTitle: Common Language Server Protocol
 MetaDescription: A Common Language Server Protocol for any tool and any language.
 Date: 2016-06-27
 ShortDescription: Common Language Server Protocol
 Author: PJ Meyer
 ---
 
-# A Common Protocol for Languages 
+# A Common Protocol for Languages
 
 June 27, 2016 by The VS Code Team, [@code](https://twitter.com/code)
 
 Visual Studio Code is an editor for any developer, no matter what programming language you use.  Between languages bundled in the tool or extensions in the [Marketplace](https://marketplace.visualstudio.com/VSCode), we have support for over [150 languages](/blogs/2016/04/14/vscode-1.0.md).  We’re also committed to developing VS Code in the open, and making the components that power VS Code available and open source.  One of our most notable components is the [Monaco editor](https://github.com/Microsoft/monaco-editor), but another technology that powers VS Code is an [open, JSON-based protocol](https://github.com/Microsoft/language-server-protocol) that anyone can use to add support for a new programming language to VS Code by implementing a "language server".
 
-![any developer any language any tool](2016_06_27_any-developer-any-language-any-tool.png)
+![any developer any language any tool](any-developer-any-language-any-tool.png)
 
 ## Any Language, Any Tool
 
-Today at the [DevNation](https://www.devnation.org) conference in San Francisco, we’ve announced along with [Red Hat and Codenvy](https://developers.redhat.com/blog/2016/06/27/a-common-interface-for-building-developer-tools) that this language server protocol is now being adopted by tool creators and language providers across the industry. For language creators, this means an enhanced tooling experience for their language across a variety of development tools and operating systems, similar to the experience that [TypeScript](https://typescriptlang.org) developers or C# developers (via [OmniSharp](https://omnisharp.net)) get today.  It also means any developer can have a consistent editing experience for their favorite programming language on any tool – even if that tool isn’t VS Code. 
+Today at the [DevNation](https://www.devnation.org) conference in San Francisco, we’ve announced along with [Red Hat and Codenvy](https://developers.redhat.com/blog/2016/06/27/a-common-interface-for-building-developer-tools) that this language server protocol is now being adopted by tool creators and language providers across the industry. For language creators, this means an enhanced tooling experience for their language across a variety of development tools and operating systems, similar to the experience that [TypeScript](https://typescriptlang.org) developers or C# developers (via [OmniSharp](https://omnisharp.net)) get today.  It also means any developer can have a consistent editing experience for their favorite programming language on any tool – even if that tool isn’t VS Code.
 
 ## How it works
 
 Visual Studio Code provides rich language support for many programming languages. Support for a particular programming language is powered by a **language server** that has a deep understanding of that language. VS Code communicates with these servers to enable rich editing capabilities like 'Errors & Warnings', 'Refactor', and 'Go To Definition'.
 
-![language server protocol](2016_06_27_language-server-protocol.png)
+![language server protocol](language-server-protocol.png)
 
-Here’s an example of how a tool and a language server could communicate semantic information during a routine editing session: 
+Here’s an example of how a tool and a language server could communicate semantic information during a routine editing session:
 
 * The user opens a file (referred to as a *document*) in the tool: The tool notifies the language server that a document is open (`didOpen`) and that the information about that document is maintained by the tool in memory.
 
@@ -38,7 +38,7 @@ Here’s an example of how a tool and a language server could communicate semant
 
 This communication, which takes place over [JSON-RPC](http://www.jsonrpc.org/specification), happens many times over the course of a typical session.
 
-![language server sequence](2016_06_27_language-server-sequence.png)
+![language server sequence](language-server-sequence.png)
 
 This architecture allows for VS Code to interact with multiple language servers, each of which can be implemented in any language (independent of the language the tool was implemented in), and support a variety of features, as long as it utilizes the common JSON-based protocol.