Merge branch 'main' into vnext

Author: ntrogh

api/extension-guides/chat.md

@@ -288,22 +288,24 @@ The following code snippet shows how to implement participant detection at the p
 ```json
 "contributes": {
     "chatParticipants": [
-        "id": "chat-sample.cat",
-        "fullName": "Cat",
-        "name": "cat",
-        "description": "Meow! What can I teach you?",
+        {
+            "id": "chat-sample.cat",
+            "fullName": "Cat",
+            "name": "cat",
+            "description": "Meow! What can I teach you?",
 
-        "disambiguation": [
-            {
-                "category": "cat",
-                "description": "The user wants to learn a specific computer science topic in an informal way.",
-                "examples": [
-                    "Teach me C++ pointers using metaphors",
-                    "Explain to me what is a linked list in a simple way",
-                    "Can you explain to me what is a function in programming?"
-                ]
-            }
-        ]
+            "disambiguation": [
+                {
+                    "category": "cat",
+                    "description": "The user wants to learn a specific computer science topic in an informal way.",
+                    "examples": [
+                        "Teach me C++ pointers using metaphors",
+                        "Explain to me what is a linked list in a simple way",
+                        "Can you explain to me what is a function in programming?"
+                    ]
+                }
+            ]
+        }
     ]
 }
 ```
@@ -473,7 +475,7 @@ const logger = vscode.env.createTelemetryLogger({
 });
 
 cat.onDidReceiveFeedback((feedback: vscode.ChatResultFeedback) => {
-    // Log chat result feedback to be able to compute the success matric of the participant
+    // Log chat result feedback to be able to compute the success metric of the participant
     logger.logUsage('chatResultFeedback', {
         kind: feedback.kind
     });

api/extension-guides/web-extensions.md

@@ -460,7 +460,7 @@ To make sure as much source code as possible can be reused, here are a few techn
 
 * To polyfill a Node.js core module such as `path`, add an entry to [resolve.fallback](https://webpack.js.org/configuration/resolve/#resolvefallback).
 * To provide a Node.js global such as `process` use the [DefinePlugin plugin](https://webpack.js.org/plugins/define-plugin).
-* Use node modules that work in both browser and node runtime. Node modules can do that by defining both `browser` and `main` entry points. Webpack will automatically use the one matching its target. Examples of node modules that do this are [request-light](https://github.com/microsoft/node-request-light) and [vscode-nls](https://github.com/Microsoft/vscode-nls).
+* Use node modules that work in both browser and node runtime. Node modules can do that by defining both `browser` and `main` entry points. Webpack will automatically use the one matching its target. Examples of node modules that do this are [request-light](https://github.com/microsoft/node-request-light) and [@vscode/l10n](https://github.com/microsoft/vscode-l10n).
 * To provide an alternate implementation for a node module or source file, use [resolve.alias](https://webpack.js.org/configuration/resolve/#resolvealias).
 * Separate your code in a browser part, Node.js part, and common part. In common, only use code that works in both the browser and Node.js runtime. Create abstractions for functionality that has different implementations in Node.js and the browser.
 * Look out for usages of `path`, `URI.file`, `context.extensionPath`, `rootPath`. `uri.fsPath`. These will not work with virtual workspaces (non-file system) as they are used in VS Code for the Web. Instead use URIs with `URI.parse`, `context.extensionUri`. The [vscode-uri](https://www.npmjs.com/package/vscode-uri) node module provides `joinPath`, `dirName`, `baseName`, `extName`, `resolvePath`.

api/extension-guides/webview.md

@@ -721,7 +721,7 @@ function getWebviewContent() {
 
 ![A script running in a webview](images/webview/scripts-basic.gif)
 
-Wow! that's one productive cat.
+Wow! That's one productive cat.
 
 Webview scripts can do just about anything that a script on a normal webpage can. Keep in mind though that webviews exist in their own context, so scripts in a webview do not have access to the VS Code API. That's where message passing comes in!
 

api/ux-guidelines/quick-picks.md

@@ -16,6 +16,7 @@ MetaDescription: UX guidelines for quick picks used in a Visual Studio Code exte
 **✔️ Do**
 
 * Use icons for clear metaphors
+* Use thoughtful icons that add clarity and help differentiate items
 * Use the description for displaying the current items (if applicable)
 * Use the detail for providing (brief) additional context
 * Use the multi-step pattern for a series of basic inputs
@@ -28,8 +29,6 @@ MetaDescription: UX guidelines for quick picks used in a Visual Studio Code exte
 ❌ Don't
 
 * Repeat existing functionality
-* Use the same icon for multiple items
-* Use more than six icons in a list
 * Use a title when the placeholder can describe the purpose on its own
 * Use inputs without a placeholder
 

docs/csharp/cs-dev-kit-faq.md

@@ -193,6 +193,22 @@ C# Dev Kit requires that it has built your project successfully before tests wil
 
 Build your solution by right-clicking on the solution in the Solution Explorer and select **Build** or `kb(workbench.action.tasks.build)`. Once the build has been completed, your tests will appear in the Test Explorer panel.
 
+### How do I collect logs for troubleshooting issues with Test Explorer?
+
+If you are encountering issues with Test Explorer, you can enable diagnostic logging to gather more information for troubleshooting:
+
+1. Increase Test Explorer verbosity:
+    Navigate to the C# Dev Kit settings and increase the Test Explorer Verbosity setting from `minimal` to `diagnostic`. This will generate more detailed logs.
+2. Check the Output Window:
+    Open the Output window in Visual Studio Code, and select **C# Dev Kit - Test Explorer** from the dropdown. Diagnostic messages will appear with a `[dev]` prefix.
+3. Collect the following information:
+   When reporting an issue, ensure you include:
+   - The diagnostic logs from the Output window.
+   - Your operating system and version (for example, Windows 10, macOS 13).
+   - The version of the C# Dev Kit extension you are using. Go to the Extensions view, and hover over the extension to view the version information.
+
+This information will help in diagnosing and resolving the issue more efficiently.
+
 ## Debugger
 
 ### When I F5, nothing happens

docs/csharp/debugging.md

@@ -71,6 +71,16 @@ In the dropdown, it lists all your existing debug configurations. If you hover o
 
 ![Remove dynamic configuration](images/debugging/delete-dynamic-config.gif)
 
+### Debug with editor debug/run buttons
+
+When a `.cs` file is open in the editor, run and debug options are accessible via the buttons located in the upper-right corner of the editor window. These actions will use the current file to query the project system and determine the associated project to launch.
+
+The two options are:
+- <span class="codicon codicon-debug-start"></span> `Run project associated with this file`: This will launch your program with `noDebug: true` with the debug adapter.
+- <span class="codicon codicon-debug-alt"></span> `Debug project associated with this file`: This will launch your program under the debugger.
+
+![Editor Run or Debug](images/debugging/editor-run-debug.png)
+
 ### Debug with launch.json
 
 If you are using the C# Dev Kit, we recommend not using this option. However, if you have the need to modify the debug configuration directly, see [Configuring launch.json for C# debugging](/docs/csharp/debugger-settings.md).

docs/csharp/images/debugging/editor-run-debug.png

@@ -98,6 +98,16 @@ For more control over `Auto Save`, open User or Workspace [settings](/docs/getst
   * `onWindowChange` - to save files when the focus moves out of the VS Code window.
 * `setting(files.autoSaveDelay)`: Configures the delay in milliseconds when `setting(files.autoSave)` is configured to `afterDelay`. The default is 1000 ms.
 
+If you want to customize the `Auto Save` functionality for specific languages or file types, you can do so from the `settings.json` file by adding language-specific rules. 
+
+For example, to disable `Auto Save` for LaTeX files:
+
+```json
+    "[latex]": {
+        "files.autoSave": "off",
+    },
+```
+
 ## Hot Exit
 
 By default, VS Code remembers unsaved changes to files when you exit. Hot exit is triggered when the application is closed via **File** > **Exit** (**Code** > **Quit** on macOS) or when the last window is closed.

docs/editor/codebasics.md

@@ -194,52 +194,50 @@ VS Code comes with a predefined set of profile templates that you can use to cus
 The Python profile is a good starting point for Python development. It comes with Python specific snippets and has the following extensions:
 
 * [autoDocstring](https://marketplace.visualstudio.com/items?itemName=njpwerner.autodocstring) - Generate Python docstrings automatically.
-* [Black Formatter](https://marketplace.visualstudio.com/items?itemName=ms-python.black-formatter) - Formatting support using the [black](https://github.com/python/black) formatter.
 * [Docker](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-docker) - Create, manage, and debug containerized applications.
-* [Even Better TOML](https://marketplace.visualstudio.com/items?itemName=tamasfe.even-better-toml) - Fully-featured TOML support.
-* [Python](https://marketplace.visualstudio.com/items?itemName=ms-python.python) - IntelliSense, linting, formatting, debugging, refactoring.
+* [Even Better TOML](https://marketplace.visualstudio.com/items?itemName=tamasfe.even-better-toml) - Fully-featured TOML support for e.g. `pyproject.toml` files.
+* [Python](https://marketplace.visualstudio.com/items?itemName=ms-python.python) - IntelliSense, environment management, debugging, refactoring.
 * [Python Environment Manager](https://marketplace.visualstudio.com/items?itemName=donjayamanne.python-environment-manager) - Manage Python environments and packages.
 * [Remote Development](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.vscode-remote-extensionpack) extension pack - Supports SSH, WSL, and Dev Containers.
-* [Ruff](https://marketplace.visualstudio.com/items?itemName=charliermarsh.ruff) - Integrates the [Ruff](https://github.com/charliermarsh/ruff) Python linter.
+* [Ruff](https://marketplace.visualstudio.com/items?itemName=charliermarsh.ruff) - Integrates the [Ruff](https://github.com/charliermarsh/ruff) Python linter and formatter.
 
 This profile also sets the following settings:
 
 ```json
     "python.analysis.autoImportCompletions": true,
     "python.analysis.fixAll": ["source.unusedImports"],
-    "editor.defaultFormatter": "ms-python.black-formatter"
+    "editor.defaultFormatter": "charliermarsh.ruff"
 ```
 
 ### Data Science Profile Template
 
 The Data Science profile is a good starting point for all data and notebook work. It comes with specific snippets and has the following extensions:
 
 * [Data Wrangler](https://marketplace.visualstudio.com/items?itemName=ms-toolsai.datawrangler) - Data viewing, cleaning and preparation for tabular datasets and Excel/CSV/Parquet files.
-* [Black Formatter](https://marketplace.visualstudio.com/items?itemName=ms-python.black-formatter) - Formatting support using the [black](https://github.com/python/black) formatter.
-* [Jupyter](https://marketplace.visualstudio.com/items?itemName=ms-toolsai.jupyter) - Use Jupyter notebooks within VS Code.
-* [Python](https://marketplace.visualstudio.com/items?itemName=ms-python.python) - IntelliSense, linting, formatting, debugging, refactoring.
-* [Dev Containers](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) - Create custom development environments inside a Docker container.
 * [GitHub Copilot](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot) - Your AI pair programmer.
+* [Jupyter](https://marketplace.visualstudio.com/items?itemName=ms-toolsai.jupyter) - Use Jupyter notebooks within VS Code.
+* [Python](https://marketplace.visualstudio.com/items?itemName=ms-python.python) - IntelliSense, environment management, debugging, refactoring.
+* [Remote Development](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.vscode-remote-extensionpack) extension pack - Supports SSH, WSL, and Dev Containers.
+* [Ruff](https://marketplace.visualstudio.com/items?itemName=charliermarsh.ruff) - Integrates the [Ruff](https://github.com/charliermarsh/ruff) Python linter and formatter.
 
 This profile also sets the following settings:
 
 ```json
     "[python]": {
-        "editor.defaultFormatter": "ms-python.black-formatter",
+        "editor.defaultFormatter": "charliermarsh.ruff",
         "editor.formatOnType": true,
         "editor.formatOnSave": true
     },
     "editor.inlineSuggest.enabled": true,
     "editor.lineHeight": 17,
     "breadcrumbs.enabled": false,
     "files.autoSave": "afterDelay",
+    "notebook.output.scrolling": true,
     "jupyter.themeMatplotlibPlots": true,
     "jupyter.widgetScriptSources": [
         "unpkg.com",
         "jsdelivr.com"
     ],
-    "notebook.experimental.outputScrolling": true,
-    // "notebook.outline.showCodeCells": true,
     "files.exclude": {
         "**/.csv": true,
         "**/.parquet": true,