Merge dev branch into master #151
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 master into dev
Note: This relies on pre-release OmniSharp bits that have not yet been released. To produce these bits, clone https://github.com/OmniSharp/omnisharp-roslyn, sync the "dev" branch and run the build script.
Add helper to retrieve project info from OmniSharp
In addition, I noticed a bug in the implementation of the command for 'dotnet restore'. It was getting directory of `OmnisharpServer.getSolutionPathOrFolder()` but not actually using it.
Lots of code clean up
Factor code to download OmniSharp out of gulpfile.js
This is related to dotnet#64.
Download and install OmniSharp during extension activation if necessary
Don't blindly construct signature help if OmniSharp returns null
Improve debugger install error messages
With the .NET CLI shared framework changes, 'program' should now be set to the built application dll in most cases. This updates the template and description.
…ption Update launch.json 'program' description
…magically Prompt user to add build task if missing
Merge 'master' into 'dev'
This is necessary to take advantage of additional information provided by the DotNetProjectSystem.
Update to OmniSharp v1.9-alpha6
This change refactors that code that adds or updates the user's tasks.json file to include a build task, to also add a launch.json file if it is missing.
Update to OmniSharp v1.9-alpha7
…omagically Add launch.json automagically
Add gulp task to package the extension with vsce.
This adds a debug proxy that acts as the debug adapter program before the coreclr-debug are fully downloaded. If the user tries to start debugging before download is finished, the proxy displays a sane error message. Once the download is complete, we rewrite the manifest to no longer call the proxy. During the VS Code session that downloads the components, the manifest is rewritten but not reloaded. In this case the proxy spawns the real debugger as a child process and proxies its stdin/stdout. Once vs code is restarted the new manifest is loaded and the proxy is no longer called. Also adds an empty command that can be run to force activation of the C# extension, which will kick off debugger acquisition.
Implement debug proxy to display error message before install completes
This allows us to dynamically inject the runtime id at activation time.
Update coreclr-debug nuget package references and dynamically generate project.json
Update to support new OmniSharp release
This checkin updates the version of OpenDebugAD7 used by the C# extension to the lastest build. This has a fix for dotnet#143. This also updates the package version to 1.0.0-rc2.
Fix launch on Windows with forward slashes in program (dotnet#143)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.