Merge master into release #1838
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Merge release into master
Merge release into master
* Update debugger to 1.13.0 package This includes the following changes: 1. Run the debugger on .NET Core 2.0 RTW (instead of preview2) 2. Breakpoint binding disambiguation fix (#1678) 3. Sending 'process' event (requested by VS For Mac team) 4. Entry point event stopping reason * Update changelog for Debugger 1.13.0
* Omnisharp respects "omnisharp.format.enable" option for self-registering as code formatter.
Support for optional formatting.
This change ensures that we only send the name of a Linux distro to the telemetry report if it appears in an approved list of known distros. The idea here is to avoid sending distro names that we don't recognize in case the user might have built the distro themselves and included personally-identifiable information in the distro name.
Only send telemetry for Linux distros that appears on an approved list
Update to latest OmniSharp release
Correctly pass target framework to OmniSharp when running/debugging tests
Add PR to item about error fixed when running/debug xUnit 2.3.0 tests.
Attempt to fix Travis per microsoft/vscode#33998
Fix running and debugging NUnit tests
Update OmniSharp to 1.25.0
…mnisharp-vscode into fileChangeNotification
Support workspace folders in OmniSharp launcher
Rename CodeLens options to match JS/TS option names
Provide more granular file change events based on VS Code file create/delete events
for single character completions, treat the completion list as incomplete
Consume the completion trigger character API
Lots of CHANGELOG updates
It's entirely possible for files to change without being opened and edited by VS Code. We need to watch for such changes.
Ensure that we listen for file changes
…#1801) * Updating tasks.json schema New tasks schema from 0.1.0 to 2.0.0 * Updating tasks.json and initialConfigurations package.json's initialConfiguraitons have been deprecated. It uses DebugConfigurationProvider instead. C# extension uses generate assets initially to create launch.json and tasks.json. However, if a user desides to dismiss the message and generate via f5, the prompt will initiate the DebugConfigurationProvider. * Adding ConfigurationProvider ${workspaceRoot} is now ${workspaceFolder} ConfigurationProvider activates on f5. This will also trigger generating a tasks file. tasks args are now 'build <path>', updating tests for these changes. * API requires October 2017 Drop (1.18) * Fixing version requirement error * Addressing PR issues * Detect older tasks.json Checking if folder.uri.fsPath is a subfolder of GetSolutionPathOrFolder to generate assets. * Fixing PR issues * Upgrading fs-extra for promises * Rewriting package.json for activation events * Reverting start activationEvents Removing empty if and assuming paths have consistent casing.
Update source map example to escape the backslash
Update to latest OmniSharp and prepare for 1.3.0-beta5
Update debugger changelog for 1.13
gregg-miskelly
approved these changes
Nov 6, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.