-
Notifications
You must be signed in to change notification settings - Fork 679
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
**Review Only** Incorproate coreclr-debug into omnisharp extension #40
Conversation
I don't think this should be merged yet but I was hoping to get some feedback. |
@gregg-miskelly for discussion |
For the minimum supported VSCode version in the package.json, we would like to bump this up to whatever the next release of VSCode is. Do you have any issue with this? |
function getPlatformLibExtension() : string { | ||
switch (process.platform) { | ||
case 'win32': | ||
return '.lib'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this should be .dll
_channel.appendLine("Downloading and configuring the .NET Core Debugger..."); | ||
_channel.show(vscode.ViewColumn.Three); | ||
|
||
vscode.window.setStatusBarMessage("Downloading and configuring the .NET Core Debugger..."); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove.
1. Adds coreclr-debug.ts to implement coreclr-debug acquisition and hooks it into omnisharp's activation handler 2. Adds the coreclr-debug directory containing the project.json, NuGet.config and dummy.cs required dotnet restore/publish 3. Adds the debugger section to contributes in package.json 4. Adds .vscodeignore to exclude items not needed at runtime from being packaged TODO: 1. Update project.json references 2. Update NuGet.config to not point to http://dbgnuget (switch to nuget.org once pacakges are published publicly) 3. Create some completion file that we can check for correct complete installation 4. Improve reporting status of acquisition to end user
With this commit, the packages pulled in actually work.
1. Add an install log log all output to our vscode OutputChannel 2. Create an install.complete file that is created only on succesfull installation of the tools. Check for the existence of this file to trigger installation
The new packages use copyFiles so dotnet publish will now copy all files we need from the packages. This requires dotnet cli tools at least as new as 1.0.0.001528 (this is the windows version number at least). With contentFiles packages, we no longer need the copy routine and it's helpers.
Pull packages from the public myget and update the dotnet invocations to use verbose output.
"program": { | ||
"type": "string", | ||
"description": "Path to the program (executable file) to launch. On Windows, a '.exe' suffix is appended if not specified already.", | ||
"default": "${workspaceRoot}/bin/Debug/dnxcore50/<My-Project-Name>" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should merge in the most recent changes that @caslan made to this (removal of 'dnxcore50').
Closing in favor of #44. |
Instantiate the roslyn LSP server with text sync support
it into omnisharp's activation handler
NuGet.config and dummy.cs required dotnet restore/publish
packaged
TODO:
nuget.org once pacakges are published publicly)
installation