omnisharp-vscode/.gitignore

bin
obj
node_modules
out
.omnisharp/
.omnisharp-*/
.debugger
.razor
.vscode-test
.razor
dist/
*.razor.json

!omnisharp/**/*

install.*

*.vsix


test/**/.vscode/launch.json
test/**/.vscode/tasks.json

.logs/
.nyc_output/
coverage/

\.DS_Store
vsix/

\.vscodeignore
Happy Coding! 2015-12-03 13:25:00 +03:00			`bin`
Ignore virtual files 2020-02-20 00:28:44 +03:00			`obj`
Happy Coding! 2015-12-03 13:25:00 +03:00			`node_modules`
			`out`
Ignore '.omnisharp' folder in .gitignore 2017-08-09 18:56:23 +03:00			`.omnisharp/`
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`
Ignore the .razor folder 2018-10-17 22:33:08 +03:00			`.razor`
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`
Initial Razor support 2018-10-04 12:54:23 +03:00			`.razor`
Set up things in development mode 2019-02-01 06:13:26 +03:00			`dist/`
add the test to check that the telemetry from razor is flowing through 2019-03-22 01:20:30 +03:00			`*.razor.json`
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
Fix git ignore, update omnisharp to include code fix fixes 2020-03-02 18:53:07 +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			`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`
Add integration test infra 2017-11-04 22:36:20 +03:00
Fix: based on comments in PR #2053 - remove isDefualt property from target interface - move is-default logic from resourcesToLaunchTargets() to autostart() - refactor autostart() target logic and comments - rename test .NET solution files 2018-04-07 20:46:40 +03:00
			`test/**/.vscode/launch.json`
			`test/**/.vscode/tasks.json`

Add log folding in Travis CI 2017-11-17 11:07:36 +03:00			`.logs/`
Add product-wide code coverage + codecov.io integration (#2101) Add product-wide code coverage + codecov.io integration Several new scripts were added: npm run cov:instrument: rebuilds your sources, then instruments them for coverage. Subsequent npm run test will generate coverage data into the .nyc_output directory npm run cov:merge-html: merges all reports from .nyc_output and puts a locally viewable coverage report into coverage directory 2018-03-13 00:14:00 +03:00			`.nyc_output/`
			`coverage/`
code clean up (#1917) * moved local functions moved local functions to top for readability and fixed missing semicolon local function at the end tslint exception for chai * use genral tslint chai rules * fix path to custom chai rules * revert type package versions * simplify gulp file * force chai types to 4.0.8 2017-12-12 02:40:32 +03:00
Test the vsix, not the build layout (#2156) The VSCode C# Extension build process follows the VS Code docs and runs tests directly inside of its repo root. This unfortunately gives a false sense of security because bugs can be introduced during VSIX packaging [particularly due to missing content in node_modules or excluded via .vscodeignore]. This change addresses this problem by moving our CI tests to execute the VSIX instead of the build's intermediate artifacts. Specifically: build the vsix unpackage the vsix instrument the unpackaged vsix run tests with VS Code Host pointing to the unpackaged vsix This makes our CI tests ~= to the user's runtime experience and will greatly help us with size reduction efforts. To support this change, I also moved our build system from package.json to Gulp. This makes the build scripts significantly easier to understand, provides intellisense for build scripts, and build-time type checking for their contents. I also strengthened the repo's use of .vscodeignore by creating a copy of the file for each scenario [online packages and offline packages]. The new gulp packaging scripts take advantage of these files to produce packages with predictable contents regardless of when packaging occurs. [small caveat, @akshita31 will be adding a test that validates that net-new content does not start sneaking into the vsix package]. 2018-04-07 00:17:17 +03:00			`\.DS_Store`
			`vsix/`

			`\.vscodeignore`