Для этого сайта требуется поддержка JavaScript.
Обзор
Помощь
Регистрация
Вход
github
/
omnisharp-vscode
зеркало из
https://github.com/github/omnisharp-vscode.git
Следить
1
В избранное
0
Форкнуть
Вы уже форкнули omnisharp-vscode
0
Код
Задачи
Пакеты
Проекты
Релизы
Вики
Активность
52aea16204
omnisharp-vscode
/
.gitignore
11 строки
77 B
Plaintext
Исходник
Обычный вид
История
Убрать экранирование
Экранировать
Happy Coding!
2015-12-03 13:25:00 +03:00
bin
node_modules
out
Revert to .NET Core OmniSharp packages
2016-11-02 16:27:49 +03:00
.omnisharp-*/
Reimplement debugger acquisition to use Package Manager 1. Remove all code related to calling dotnet restore/dotnet publish 2. Remove coreclr-debug directory 3. Add debugger runtime packages to package manifest 4. Add an install.Begin file to the package manager so we can detect that it is in progress 5. Rework the debugger proxy so that it understands the package manager 6. Add knowledge of the dotnet cli on the path to the debugger proxy TODO: 1. Lots and lots of testing 2. Offline package creation
2016-11-05 00:04:20 +03:00
.debugger
Migrates the extension to latest VS Code and TypeScript This change updates the extension and several dependencies to the latest VS Code and TypeScript per the instructions at https://code.visualstudio.com/upgrades/v1_6#_extension-authoring.
2016-12-19 19:20:50 +03:00
.vscode-test
Incorproate coreclr-debug into omnisharp extension 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
2016-02-23 03:45:42 +03:00
Reimplement debugger acquisition to use Package Manager 1. Remove all code related to calling dotnet restore/dotnet publish 2. Remove coreclr-debug directory 3. Add debugger runtime packages to package manifest 4. Add an install.Begin file to the package manager so we can detect that it is in progress 5. Rework the debugger proxy so that it understands the package manager 6. Add knowledge of the dotnet cli on the path to the debugger proxy TODO: 1. Lots and lots of testing 2. Offline package creation
2016-11-05 00:04:20 +03:00
install.*
Punch through getting download and unzip working properly
2016-10-28 02:40:39 +03:00
Incorproate coreclr-debug into omnisharp extension 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
2016-02-23 03:45:42 +03:00
*.vsix