Merge pull request #1 from Microsoft/master

auto-merge updating fork from upstream

blogs/2016/02/01/introducing_insiders_build.md

@@ -10,6 +10,8 @@ Author: Chris Dias
 
 # Introducing the Insiders Build
 
+February 1, 2016 by Chris Dias, [@chrisdias](https://twitter.com/chrisdias)
+
 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.
 
 This is why VS Code has automatic updates on by default. We periodically query the update service to see if a new version is available, download it when ready, and then gently prompt you to restart.

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

@@ -10,6 +10,8 @@ Author: Andy Sterland
 
 # Introducing Chrome Debugging for VS Code
 
+February 23, 2016 by [Andy Sterland](https://twitter.com/AndySterland) and [Kenneth Auchenberg](https://twitter.com/auchenberg)
+
 Since the first release of Visual Studio Code, one of our focuses has been to simplify the daily workflow for developers by enabling them to debug their code directly from the editor. We started out with .NET and Node.js debugging, and today we are taking the next step by introducing our Chrome Debugger for Visual Studio Code.
 
 Our Chrome Debugger allows front-end developers to debug their client-side JavaScript code running inside Google Chrome directly from Visual Studio Code.
@@ -51,7 +53,7 @@ We believe there’s much to be done for front-end developers, as building for t
 
 We’ve released this extension on [GitHub](https://github.com/Microsoft/vscode-chrome-debug) as an MIT licensed open source project. It’s a work in progress, so see our issues page for known bugs – for example, we have a few issues around supporting all flavors of generated source maps.
 
-For now we are support Google Chrome, but we’re also looking at expanding our support to [Microsoft Edge](https://www.microsoft.com/en-us/windows/microsoft-edge) and other browsers. We really want your feedback and help to build an even better debugging experience.
+For now we support Google Chrome, but we’re also looking at expanding our support to [Microsoft Edge](https://www.microsoft.com/en-us/windows/microsoft-edge) and other browsers. We really want your feedback and help to build an even better debugging experience.
 
 If you have any issues or ideas for improvements, feel free to reach out to us on [Twitter](https://twitter.com/code) or [GitHub](https://github.com/Microsoft/vscode-chrome-debug/).
 

blogs/2016/03/07/Feb2016Release.md

@@ -10,10 +10,12 @@ Author: Chris Dias
 
 # February 2016 Release
 
+March 7, 2016 by The VS Code Team, [@code](https://twitter.com/code)
+
 Today we are releasing the February 2016 build of Visual Studio Code. This release brings many improvements to your development experience, including:
 
 * **JavaScript**: [Salsa](https://github.com/Microsoft/TypeScript/issues/4789) is now the default JavaScript/TypeScript language service, bringing support for React and React Native to VS Code.
-* **Code Folding**: The most requested feature in [User Voice](https://visualstudio.uservoice.com/forums/293070-visual-studio-code/suggestions/7752321-add-code-folding-support) is now on by default.
+* **Code Folding**: The most requested feature in [UserVoice](https://visualstudio.uservoice.com/forums/293070-visual-studio-code/suggestions/7752321-add-code-folding-support) is now on by default.
 * **Extensions**: VS Code can make recommendations for extensions based on the files you've opened in the tool (Press `kb(workbench.action.showCommands)`, search for "recommend").
 * **Accessibility**: Screen reader support in the Editor is now on by default.
 

blogs/2016/03/11/ExtensionsRoundup.md

@@ -10,6 +10,8 @@ Author: Wade Anderson
 
 # VS Code Extensions
 
+March 17, 2016 by Wade Anderson, [@waderyan_](https://twitter.com/waderyan_)
+
 In November 2015, we open sourced Visual Studio Code and introduced the [extensions API](http://code.visualstudio.com/docs/extensionAPI/vscode-api). The VS Code extensions [Marketplace](https://marketplace.visualstudio.com/VSCode) has over 850 extensions. Many new languages (Go, PowerShell, PHP, Python) and frameworks (Apache Cordova, React Native) are now supported.
 
 We will continue to iterate on improving the API and we would love your [feedback](https://github.com/Microsoft/vscode/issues). If you are new to VS Code extensions, check out the [docs](http://code.visualstudio.com/docs/editor/extension-gallery) for instructions on finding and installing new extensions. We are invested in empowering the community to make VS Code the world's greatest code editor.
@@ -18,7 +20,7 @@ In the spirit of a great [curated extensions list](https://github.com/viatsko/aw
 
 ## Ruby by Peng Lv
 
-Ruby language support is a popular request on [User Voice](https://visualstudio.uservoice.com/forums/293070-visual-studio-code?query=ruby), with a handful of extensions
+Ruby language support is a popular request on [UserVoice](https://visualstudio.uservoice.com/forums/293070-visual-studio-code?query=ruby), with a handful of extensions
 in the [Marketplace](https://marketplace.visualstudio.com/search?term=ruby&target=VSCode&sortBy=UpdatedDate). We've enjoyed playing with this [Ruby extension](https://marketplace.visualstudio.com/items?itemName=rebornix.Ruby) that provides language and debugging support. The setup is simple and is contained in the extension's [README](https://marketplace.visualstudio.com/items?itemName=rebornix.Ruby).
 
 ### Install Ruby Dependencies

blogs/2016/03/14/Feb2016Recovery.md

@@ -10,6 +10,8 @@ Author: Chris Dias
 
 # February 2016 "Recovery" Release
 
+March 14, 2016 by The VS Code Team, [@code](https://twitter.com/code)
+
 If we find critical issues after a major update, we do what we call a "recovery" release. Today we're updating the February 2016 build with fixes for the following four issues:
 
 - [3903](https://github.com/Microsoft/vscode/issues/3903): [js] syntax highlight for 'var' and 'function' not working in Default VS theme

blogs/2016/04/04/vscode-at-build.md

@@ -0,0 +1,48 @@
+---
+Order: 6
+TOCTitle: VS Code at //build/
+PageTitle: Visual Studio Code at Build 2016
+MetaDescription: Visual Studio Code at Build 2016. Learn about presentations featuring VS Code. 
+Date: 2016-04-05
+ShortDescription: Visual Studio Code had a great presence at Build 2016.
+Author: Wade Anderson
+---
+
+# VS Code at //build/
+
+April 5, 2016 by Wade Anderson, [@waderyan_](https://twitter.com/waderyan_)
+
+This year's [Build 2016 conference](http://build.microsoft.com/) in San Francisco was very exciting and Visual Studio Code was happy to be a part of it. VS Code featured prominently as the editor of choice in many talks and demos and there were several presentations dedicated to VS Code.
+
+## Tips and Tricks
+
+Don't miss this well attended session on [Best of VS Code: Tips and Tricks](https://channel9.msdn.com/Events/Build/2016/B887). You'll start by learning the basics of VS Code and quickly become a power user through useful [Tips and Tricks](https://github.com/Microsoft/vscode-tips-and-tricks). The talk finishes with a working "To Do" list [sample](https://github.com/Microsoft/vscode-react-sample) written in JavaScript, Node.js and React/JSX.
+
+## What's New in TypeScript
+
+TypeScript architect Anders Hejlsberg's talk on [What's New in TypeScript?](https://channel9.msdn.com/Events/Build/2016/B881) used VS Code throughout his demos. This talk is also a great way to understand the TypeScript/JavaScript improvements in VS Code when we adopted the new TypeScript language service, codename "Salsa".
+
+## The Future of C#
+
+There's a nice section on VS Code integration and C# debugging later in [The Future of C#](https://channel9.msdn.com/Events/Build/2016/B889) starting at minute 39 (but you'll want to watch the entire entertaining talk).
+
+## Node.js and Microsoft
+
+As you'd expect from a talk called [Node.js and Microsoft: A Love Story about Developer Tools](https://channel9.msdn.com/Events/Build/2016/B870), VS Code is going to be starring.  Check out the sections on using `nodemon` to automatically reattach the VS Code Node.js debugger (minute 28) and the cool prototype of time travel debugging (minute 39).
+
+## Channel 9
+
+[Channel 9's coverage of //build/ 2016](https://channel9.msdn.com/Events/Build/2016) is a great resource to learn more about VS Code and technologies like Cordova, Ionic, Angular, and React Native where VS Code is a good match for a high performance editor. Browse or search for your area of interest and we're sure you'll find a relevant presentation or panel discussion.
+
+## New Extensions
+
+There were also several new VS Code extensions released at //build/:
+
+* [C/C++ for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=ms-vscode.cpptools) - Complete C/C++ language support including code-editing and debugging. See a demo in [C++ Discussion](https://channel9.msdn.com/Events/Build/2016/C-Discussion).
+* [Visual Studio Team Services](https://marketplace.visualstudio.com/items?itemName=ms-vsts.team) - Monitor builds and manage pull requests and work items for Team Services Git repositories.
+* [NativeScript](https://marketplace.visualstudio.com/items?itemName=Telerik.nativescript) - NativeScript support for Visual Studio Code.
+
+Visit the VS Code [Extensions Marketplace](https://marketplace.visualstudio.com/VSCode) to learn more about these and other useful extensions.
+
+Wade Anderson, VS Code Team Member <br>
+[@waderyan_](https://twitter.com/waderyan_)

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

@@ -0,0 +1,83 @@
+---
+Order: 7
+TOCTitle: 1.0 Release
+PageTitle: Visual Studio Code 1.0 Release
+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
+---
+
+# 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)
+
+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.
+
+What started as an experiment to build a production quality editor using modern web technologies has blossomed into a new kind of cross-platform development tool, one that focuses on core developer productivity by centering the product on rich code editing and debugging experiences. Visual Studio Code brings the industry-leading experiences of Visual Studio to a streamlined development workflow, that can be a core part of the tool set of every developer, building any kind of application.
+
+Getting to "1.0" over the last few months has been about more than features. We have worked with the community to further improve stability, fixing hundreds of bugs. And we’ve pushed hard on getting the best performance we can out of the editing experience.
+
+VS Code was initially built for developers creating web apps using JavaScript and TypeScript. But in less than 6 months since we made the product extensible, the community has built over [1000 extensions](https://marketplace.visualstudio.com/vscode) that now provide support for almost any language or runtime in VS Code. Today, a broad range of developers from individuals and startups to Fortune 500 companies, including audiences completely new to Microsoft’s tools, are all more productive with a tool that fits comfortably into their current tool chain and workflow, and supports the technologies they use, from Go and Python to React Native and C++. With this great ecosystem in place, we’re now confident in declaring our API as stable, and guaranteeing compatibility going forward.
+
+And we have strived to make VS Code 1.0 a great editor for every developer. VS Code is now fully localizable, and ships in 9 different languages, including French, German, Japanese, and Chinese. And, we have worked to make VS Code the most accessible of modern editors, with full keyboard navigation and support for screen reading and accessible navigation for visually impaired developers.
+
+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)
+
+## The History of VS Code
+
+>*Can we build a code editor fast enough that it doesn’t feel like you’re typing in a browser?*
+
+It was only a few short years ago that we kicked off what we then called the "Monaco" team. At the time, browsers were just beginning to introduce HTML5, and the race to build faster JavaScript runtimes was in full swing.
+
+So we set out to answer the question, "Can we build a browser-based code editor that feels native?" Not just an experience for text editing, but source code editing.  Suggestion lists, error and warning squiggles, Go to Definition, and more.
+
+Today, we believe the answer was a resounding "Yes". The editor we built can now be found on some of the most demanding global websites – OneDrive, Visual Studio Team Services, Bing Code Search, Azure – sites used by millions of people every day. It even ships to 100s of millions of Windows desktops with the F12 tools in Internet Explorer.  And that same editor is at the heart of VS Code.
+
+Of course, to build the editor we needed a development tool. Developers know that one of the best ways to evolve your code quickly is to "dogfood" it: use it the same way your customers will.  It therefore made sense that we would create a local Node.js based service to serve up files and the editor in a lightweight development tool. This tool eventually made its way to the cloud as a part of Azure Websites.
+
+But we strived to go further. We wanted to build a native development tool that developers could install and use anywhere, for any source code. And, from our experience, we believed that it was important to not just have an editor, but one that could help developers accomplish their most common tasks: navigating code, debugging, and working with Git.  And, so, Visual Studio Code was born.
+
+Being built on web technologies made it easy to host the tool in a native cross-platform shell. We decided early on to use, and contribute to, a number of open source technologies – including GitHub’s great Electron shell, which combines web and native UI with a Node.js API. In just a few short months, we were able to release the [first preview](https://blogs.msdn.microsoft.com/somasegar/2015/04/29/introducing-visual-studio-code-visual-studio-2015-rc-application-insights-public-preview-and-net-core-preview-for-linux-and-ma) of Visual Studio Code at //build/ 2015.
+
+The initial response to a code editor running on OS X, Windows, and Linux was overwhelmingly positive, even with two fundamental gaps in the offering – extensibility and open development.
+
+Keeping our principle of using VS Code the way our customers do, we decided that the best way to deliver a rich and stable API was to build VS Code using the same API we would expose to extension developers. In fact, the core language services for JavaScript and TypeScript are actually extensions that just happen to be bundled with the distribution. Today, we use VS Code to build and debug VS Code, its extensions, and Node-based services. The same rich TypeScript editing, navigation, and debugging experiences we enjoy when building VS Code are available to everyone developing an extension for VS Code. Six months after our initial preview release, we declared VS Code to be Beta quality at Connect(); 2015, with a full extensibility model, and support in the new Visual Studio Marketplace.
+
+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)
+
+## Being "1.0"
+
+Today, Visual Studio Code delivers on many of the aspects that we imagined during incubation. VS Code has great editing and navigation [experiences](/docs/editor/editingevolved), streamlined [debugging](/docs/editor/debugging), and built-in [Git support](/docs/editor/versioncontrol).
+
+Developers today love VS Code for its powerful set of built-in features, intuitive editing and debugging experiences, performance and responsiveness, and great language and platform support. The VS Code download is under 40MB including support for 9 additional [languages](/docs/customization/locales) (Simplified Chinese, Traditional Chinese, French, German, Italian, Japanese, Korean, Russian and Spanish) and it installs in seconds.  With the help of developers like [@zersiax](https://twitter.com/zersiax), VS Code is now [accessible](/docs/editor/accessibility) to visually impaired developers on Windows and soon on OS X and Linux.
+
+## Community at its Core
+
+More than anything else, what drives the success of Visual Studio Code is the feedback and interactions from the community. From the beginning, we’ve striven to be as open as possible in our roadmap and vision for VS Code, and in November, we took that a step further by open-sourcing VS Code and adding the ability for anyone to make it better through submitting issues and feedback, making pull requests, or creating extensions.
+
+The community responded, with huge growth in the number of extensions and the way they’re using VS Code. Today we have extensions for [Node.js](https://marketplace.visualstudio.com/search?term=node&target=VSCode&sortBy=Downloads), [Go](https://marketplace.visualstudio.com/search?term=go&target=VSCode&sortBy=Downloads), [C++](https://marketplace.visualstudio.com/search?term=c++&target=VSCode&sortBy=Downloads), [PHP](https://marketplace.visualstudio.com/search?term=php&target=VSCode&sortBy=Downloads), and [Python](https://marketplace.visualstudio.com/search?term=python&target=VSCode&sortBy=Downloads), as well as many more languages, linters, and tools.  And VS Code is being used both by teams of developers, but also in companies like Progressive Insurance, where VS Code is used not just by developers, but analysts and data scientists as well.
+
+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">
+
+## Looking Ahead
+
+While we’re excited about releasing 1.0 today, we are even more excited about the future.
+
+Of course, we will continue to focus on the fundamentals.  Performance, stability, accessibility, and compatibility are of utmost importance to our users, and they are to us as well. We will continue to invest in improving developer productivity, guided by the great user feedback on [UserVoice](http://go.microsoft.com/fwlink/?LinkID=533482). We will continue to work with partners and the community to expand support for new languages, and platforms, and experiences. And we will continue to work with you, our community, to build a great tool for you, and for every developer.
+
+If you haven’t tried out Visual Studio Code yet, please [download](/Download) it and let us know what you think!
+
+Thanks Again!
+
+The VS Code Team, [@code](https://twitter.com/code)
+