56b1833309
* switch from public to intl * Dont wait for eslint to package * Try to install eslint global * Remove rimraf from gitignore, it doesnt make sense why its there? this shouldnt make any folder called rimraf * add rimraf globally * Dont install -g as -g doesnt work on eslint /shrug * Try installing -g and -l for separate components * use save-dev * Call npx to run eslint local as global since global cant resolve local packages well * Tell NPX to use eslint that supports TS * Move Lint and Upstream Verification onto OSX This will make it faster since more of those agents are available and also free up more of the high demand windows agents that are needed to run the windows leg. * Fix build * Leverage npm ci to lock the version This is to hopefully prevent E401 from trying to update new versions onto the base from an unauth'd machine * Remove batch true This is so multiple commits can run PRs at the same time. This has been turned on for a long time and I'm not sure why it was. Thank you @miyanni for helping figure this out, it was a weird an unexpected thing to dig through from the initial problem set. |
||
---|---|---|
.config | ||
.github/ISSUE_TEMPLATE | ||
.vscode | ||
Documentation | ||
images | ||
msbuild | ||
packages | ||
pipeline-templates | ||
sample | ||
signing | ||
vscode-dotnet-runtime-extension | ||
vscode-dotnet-runtime-library | ||
vscode-dotnet-sdk-extension | ||
.eslintrc.js | ||
.gitattributes | ||
.gitignore | ||
.npmrc | ||
.vscodeignore | ||
1es-azure-pipeline.yml | ||
1pr-azure-pipeline.yml | ||
CODE-OF-CONDUCT.md | ||
CODE_OWNERS.txt | ||
CONTRIBUTING.md | ||
LICENSE.txt | ||
PoliCheckExclusions.xml | ||
README.md | ||
SUPPORT.md | ||
THIRD-PARTY-NOTICES.txt | ||
build.cmd | ||
build.ps1 | ||
build.sh | ||
dependency-verifier.py | ||
global.json | ||
mock-webpack.ps1 | ||
mock-webpack.sh | ||
nuget.config | ||
package-lock.json | ||
package.json | ||
test.cmd | ||
test.ps1 | ||
test.sh | ||
tsconfig.eslint.json | ||
vscode-dotnet-runtime.code-workspace | ||
yarn.lock |
README.md
.NET Runtime and SDK Installation Tools
This repo contains two VS Code extensions, vscode-dotnet-runtime and vscode-dotnet-sdk. The vscode-dotnet-runtime can be used to install the .NET runtime and is meant to be leveraged by other extensions which depend on the runtime. The vscode-dotnet-sdk is a special install for internal features and not designed to be used by other extensions because it will conflict with existing SDK installations on the users machine.
Contributing to Repository
Looking for something to work on? The list of up-for-grabs issues is a great place to start.
Please read the following documents to get started.
This project has adopted the code of conduct defined by the Contributor Covenant to clarify expected behavior in our community. For more information, see the .NET Foundation Code of Conduct.
Building
Requirements
- Node.js + npm
- VSCode
Running the sample
- Run the build script at the root of the repo (
build.sh
orbuild.cmd
). - Open the repo's workspace in VSCode
- Run the
Run Sample Extension
configuration in VSCode - In the launched experimental instance open the command pallete and run the
Sample: Run a dynamically acquired .NET Core Hello World App
.
.NET Foundation
.NET Core for VSCode is a .NET Foundation project.
See the .NET home repo to find other .NET-related projects.
License
.NET Core (including this repo) is licensed under the MIT license.