8dbcff6733
* add publish task * move template out of steps and into jobs * get rid of pool * dont pass 1es pool * add depends on chain * use vsce latest * run package on publi * add approval step: * vsixs are stored in the root, so don't check in the extension folder * Switch to MI instead of a PAT * Fix ps1 issue * Only deploy on internal * Use pool vs vmimage * Try to fix pool condition * Use a different pool * Condition the name of the build based on OS Why is windows the bomb emoji and not the windows emoji? And why did I do this: The windows build goes last because its in alphabetical order based on the behavior of how devops works. This is bad because it should go first and makes the other steps take longer as they depend on only the windows task. The bomb emoji is one of the first emojis thats not an emoticon before the penguin emoji so I picked that one.. * It's pretty silly you cant define a variable in a template but here we are * Maybe it has to be in plaintext * The deployment step is not necessary * wait for wait job * Set the emoji * Move windows to the top * Set 'use 1es pool' to true * Switch to a different ordering so windows runs first, then linux * try to fix bug where version is not passed and publish args is wrong * Try to pass var into another job since we cant have a template in the jobs * Revert "Try to pass var into another job since we cant have a template in the jobs" This reverts commit |
||
|---|---|---|
| .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.shorbuild.cmd). - Open the repo's workspace in VSCode
- Run the
Run Sample Extensionconfiguration 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.