Skip to content
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

Incorproate coreclr-debug into omnisharp extension (rebasing @ChuckRies's work against 'dev' branch) #44

Merged
merged 9 commits into from
Feb 26, 2016

Conversation

DustinCampbell
Copy link
Member

The original PR was #40.

Adds coreclr-debug.ts to implement coreclr-debug acquisition and hooks it into omnisharp's activation handler
Adds the coreclr-debug directory containing the project.json, NuGet.config and dummy.cs required dotnet restore/publish
Adds the debugger section to contributes in package.json
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

chuckries and others added 9 commits February 26, 2016 13:47
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.
DustinCampbell added a commit that referenced this pull request Feb 26, 2016
Incorproate coreclr-debug into omnisharp extension (rebasing @chuckries's work against 'dev' branch)
@DustinCampbell DustinCampbell merged commit 3847c9f into dev Feb 26, 2016
@DustinCampbell DustinCampbell deleted the coreclr-debug branch March 17, 2016 18:07
dibarbet added a commit to dibarbet/vscode-csharp that referenced this pull request Jun 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants