Related: https://github.com/Microsoft/vscode-extension-samples/issues/122

• Create a new topic under api/working-with-extensions for https://github.com/Microsoft/vscode-extension-samples/tree/master/webpack-sample
• Explain benefits of bundling
• Together with the sample, illustrate how to bundle extensions using webpack

After following these steps in the Python Flask tutorial: https://code.visualstudio.com/docs/python/tutorial-flask#_refactor-the-project-to-support-further-development

I can only run the app in the python debug console. I can't run it in powershell, although I am following the same steps, I get this error:

Error: Could not locate a Flask application. You did not provide the "FLASK_APP" environment variable, and a "wsgi.py" or "app.py" module was not found in the current directory.

When using vscode-remote it shows C:\\Users\\username/.ssh/config.

Tried to fix following the doc at https://github.com/microsoft/vscode-docs/blob/master/docs/remote/troubleshooting.md#fixing-ssh-file-permission-errors

But the command seems not work for me:

Reported by @jvesouza

Keyboard navigate onto a user installation 64bit blue link or any other blue link. Hit space or enter -> nothing happens -> I can not download vscode

"

python -m venv venv python : The term 'python' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1

• python -m venv venv

•   + CategoryInfo          : ObjectNotFound: (python:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
  

"

This error is shown after installing and adding python to the path. It is simply there and does not let me work and set the environment. The extensions are added too.

Do you have any suggestions on how to fix it? Thanks in advance,

This proposal is to add a section for PowerShell within this list and not simply a PowerShell page under the Language section. I believe there is enough content needed for PowerShell development that warrants more details than a simply getting started in the language section with Python.

PowerShell being a main language for Microsoft products and with Azure management it warrants building out content so users can see how to get started with PowerShell development. I would propose the initial layout for pages to get started:

PowerShell
├── Extension
├── Editing Code
├── Plaster
├── PSScriptAnalyzer
├── Pester
├── Debugging
├── Settings Reference

I see the current code of intent like this:

The goal of the VS Code documentation is to educate users on VS Code features and how VS Code can be used to enhance their development experience with different programming languages and runtimes.

The documentation is not intended to provide:

• An introduction to coding or software development
• Tutorials on technologies independent from VS Code
• Promotion of third-party tools, plug-ins, or services
• Excessive detail or advanced walkthroughs

The documentation should target developers learning to use VS Code or searching for quick answers to commonly asked questions. Other forums such as blog posts can provide more detailed content elaborating on specific scenarios.

I wonder the introduction to coding or software development should not include how to develope a Visual Studio Code Extension (henceforth referred to as "VSCE")

I made a Chrome Extension, and used AWS & Firebase before and I think we could learn something from their documentations. There are some problems I want to point out but I don't know if this is against the original intention:

1. #4905
2. Is the "visibility": "collapsed" a property of contributes.views? It is not mentioned
3. Where to add the when: "isLinux" in contributes.walkthroughs? I assume we can do it both under walkthroughs and under every step? Can we call it out?
4. I want to see how the initial views look like right after the installation of the VSCE. I don't think F5 can do that. Nor tsc -watch -p ./ does, and the VSCE being developed is not able to uninstall. I think there are some configuration file but I don't know where to remove/modify it.

In conclusion, I think the document can expalin more clearly if we are encouraged to make a more specific explain on each API.

I've created a video playlist on YouTube explaining every single setting in VS Code (except 9 I don't yet understand, but will work on next) and I'd like to share that with the community. I'm guessing it would be most useful to share this in VS Code's documentation, but I'm not sure if that's appropriate. If it is, please let me know and I'll share the playlist link.

Writer: @weinand Reviewer: @roblourens

• Page: https://vscode-ext-docs.azurewebsites.net/api/extension-guides/debug-extension
• File to edit: https://github.com/Microsoft/vscode-docs/blob/ext-docs/api/extension-guides/debug-extension.md

The problems:

• This page does not link to the new DAP website
• This page does not include updated illustrations such as those in this blog post, making it harder to understand the purpose of DAP (solving the ide*runtime debugging problem), and the way DAP works (as illustrated in the message communication image)

Here are some inspirations, from docs I was trying to make for LSP:

• https://vscode-ext-docs.azurewebsites.net/api/language-extensions/overview#programmatic-language-features
• https://vscode-ext-docs.azurewebsites.net/api/language-extensions/smart-editing-lsp-guide

The todo:

• Update the page so it points to DAP website
• Use the updated illustration from the blog post to better explain DAP and the way it works
• Update the Debugger section of Extension Capabilities Overview page too. Include a short passage that explains what Debug Extension is capable of and point them to the more detailed guide. File to edit is: https://github.com/Microsoft/vscode-docs/blob/ext-docs/api/extension-capabilities/overview.md

From only two days with the team in Zurich, I have been exposed to a handful of tips and tricks in the editor I didn't know existed.

This is an idea for a doc page - "Editor Tips & Tricks". The idea is to have a page (I'm imagining with lots of animated gifs to demonstrate) to show cool things within the editor.

A couple I have already seen.

• vertical text selection
• staging portions of a commit

I'm sure @joaomoreno could add a lot to this page.

Hi,

This is my first time posting an issue, please let me know if I do it wrong or anything.

I am currently following the instructions in Data Science in Visual Studio Code. Got the error until "(Optional) Use a neural network to increase accuracy":

ModuleNotFoundError Traceback (most recent call last) in ----> 1 from keras.models import Sequential 2 from keras.layers import Dense 3 4 model = Sequential()

ModuleNotFoundError: No module named 'keras'

Note: I ran "conda create -n myenv python=3.7 pandas jupyter seaborn scikit-learn keras tensorflow" and changed my "Python: Select Interpreter" accordingly

This PR enhances the documentation about the configurationProvider option specified inside c-cpp-properties.json by introducing the requirement for an extension to become a configurationProvider candidate.

Not sure how to name https://github.com/microsoft/vscode-cpptools-api properly, so I just call it vscode-cpptools-api.

Fixes #5816

Hello, I am having a problem compiling c++ code in vscode on my mac. I was following this tutorial : https://code.visualstudio.com/docs/cpp/config-clang-mac Except when I try the first compilation I get an error :" launch: program '/Users/Agathe/projects/helloworld/helloworld' does not exist ".

This is the launch.json file : { // Utilisez IntelliSense pour en savoir plus sur les attributs possibles. // Pointez pour afficher la description des attributs existants. // Pour plus d'informations, visitez : https://go.microsoft.com/fwlink/?linkid=830387 "version": "0.2.0", "configurations": [ { "name": "C/C++: clang++ build and debug active file", "type": "cppdbg", "request": "launch", "program": "${fileDirname}/${fileBasenameNoExtension}", "args": [], "stopAtEntry": true, "cwd": "${workspaceFolder}", "environment": [], "externalConsole": false, "MIMode": "lldb", "preLaunchTask": "C/C++: clang++ build active file" } ] }

I was able to compile using the command g++ -std=c++11 helloworld.cpp -o helloworld but how don't know how to apply this method in the case where I have a CMakeLists file.

I also have a warning warning: range-based for loop is a C++11 extension [-Wc++11-extensions] for (const string& word : msg) and part of my c_cpp_properties.json file is "cStandard": "c17", "cppStandard": "c++11",

There is a duplicate "reportPropertyTypeMismatch" in Value. "reportFunctionMemberAccess" was not in the documentation, but seems to fit there.

I am not able to get code completion to work without pressing CTRL+SPACE on the Mac, as described (with helpful screenshots/videos) here:

https://stackoverflow.com/questions/74837030/why-isnt-code-completion-working-for-my-custom-programming-language-in-vscode

Any ideas why it's not working and how to fix it? I would like it to work like the JavaScript/TypeScript example in the linked screenshot, where as you type it gives you a list of code completions.

From @Colengms

Scope | VS Code description | Overridable in workspace (or workspace folder in a single root scenario) | Overridable in workspace folder (in a multiroot scenario which has one or more folders) | Remote will inherit local user settings | Overridable remotely | Overridable at language level -- | -- | -- | -- | -- | -- | -- application | Settings that apply to all instances of VS Code and can only be configured in user settings. | no | no | yes | no | no window | Windows (instance) specific settings which can be configured in user, workspace, or remote settings. | yes | no | yes | yes | no resource | Resource settings, which apply to files and folders, and can be configured in all settings levels, even folder settings. | yes | yes | yes | yes | no machine | Machine specific settings that can be set only in user settings or only in remote settings. For example, an installation path which shouldn't be shared across machines. | no | no | no | yes (implicitly, as it's not inherited) | no machine-overridable | Machine specific settings that can be overridden by workspace or folder settings. | yes | yes | no | yes (implicitly, as it's not inherited) | no language-overridable | Resource settings that can be overridable at a language level. | yes | yes | yes | yes | Yes