Skip to content

Commit 4e5e52d

Browse files
committed
Merged main into live
2 parents e8bf502 + 5ed3462 commit 4e5e52d

13 files changed

+64
-14
lines changed

docs/ide/find-in-files.md

Lines changed: 15 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "Search within Specific Files with 'Find in Files'"
33
description: Explore the Find in Files feature in Visual Studio and discover how to use the feature to search a specific set of files.
4-
ms.date: 1/12/2024
4+
ms.date: 11/1/2024
55
ms.topic: conceptual
66
f1_keywords:
77
- vs.findinfiles
@@ -137,23 +137,34 @@ The **File types** option indicates the types of files to search through in the
137137

138138
:::image type="content" source="media/find-file-types.png" alt-text="Screenshot of the File Types section of the Find In Files dialog box.":::
139139

140-
You can search for multiple file types by separating them with a semicolon (`;`). You can also can exclude folders and files by prefixing any path or file type with an exclamation mark (`!`).
140+
You can search for multiple file types by separating them with a semicolon (`;`). You can also exclude folders and files by prefixing any path or file type with an exclamation mark (`!`).
141141

142142
### Append results
143143

144144
Use this option to append the results from the current search to previous search results.
145145

146146
::: moniker-end
147147

148-
## Search results
149148

150149
:::moniker range=">=vs-2022"
151150

151+
## Search results
152+
152153
When you perform a search for all results, results appear as they become available.
153154

154155
> [!NOTE]
155156
> Visual Studio begins building an index after your code context is loaded, such as when opening a new project, changing branches, or otherwise changing the file list. If you search while Visual Studio is still indexing your source files, you might see a warning that results are incomplete.
156157
158+
With Visual Studio 17.12 and later, if you want to repeat the same search after doing further work, you can click the clockwise arrow icon to refresh the results. This ensures all changes you've made since the last Find are reflected without having to reopen the Find window.
159+
160+
![Screenshot showing the refresh button.](./media/vs-2022/find-in-files-refresh.png)
161+
162+
## Modify find
163+
164+
Use the **Modify Find** button (**Repeat Find** in some versions) in the results window to refine the search criteria without having to recreate the same search criteria in the Find window. Clicking **Modify Find** reopens Find in Files with your prior search criteria for that set of results.
165+
166+
![Screenshot showing the Modify Find button and search criteria you can modify.](./media/vs-2022/find-in-files-modify-find.png)
167+
157168
:::moniker-end
158169

159170
### Keep results
@@ -184,4 +195,4 @@ In Visual Studio 2022 and later, you can set Visual Studio to always keep result
184195

185196
- [Replace in files](../ide/replace-in-files.md)
186197
- [Find and replace text](../ide/finding-and-replacing-text.md)
187-
- [Visual Studio commands](../ide/reference/visual-studio-commands.md)
198+
- [Visual Studio commands](../ide/reference/visual-studio-commands.md)
Loading
Loading
Loading
Loading
Loading
57.5 KB
Loading

docs/ide/reference/command-prompt-powershell.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -232,7 +232,13 @@ Start the Developer PowerShell for the Community Edition of [Visual Studio 2022
232232

233233
For Developer PowerShell, the starting directory of the shell is the Visual Studio Project Location. This default locale overrides any other paths, such as working directory. This behavior can be turned off by using the command-line argument `-SkipAutomaticLocation`. This can be useful if you want the shell to stay in the current directory after initialization.
234234

235+
::: moniker range="vs-2019"
235236
The Project Location can be adjusted in **Tools** > **Options** > **Projects & Solutions** > **Project Location**.
237+
::: moniker-end
238+
239+
::: moniker range="vs-2022"
240+
The Project Location can be adjusted in **Tools** > **Options** > **Projects & Solutions** > **Locations**.
241+
::: moniker-end
236242

237243
> [!TIP]
238244
> The command-line arguments `-Arch`, `-HostArch`, and `-SkipAutomaticLocation` are supported by both the `Launch-VsDevShell.ps1` script and the `Enter-VsDevShell` cmdlet.

docs/ide/visual-studio-search.md

Lines changed: 33 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Use Visual Studio search to find code & do queries
33
description: Explore the Visual Studio search feature and discover how to find settings, menus, code, and work with filters, queries, and more.
4-
ms.date: 07/02/2024
4+
ms.date: 11/1/2024
55
ms.topic: how-to
66
helpviewer_keywords:
77
- environments [Visual Studio], navigation
@@ -28,6 +28,9 @@ The Visual Studio integrated development environment (IDE) has many menus, optio
2828

2929
If you're using Visual Studio 2022 [version 17.6](/visualstudio/releases/2022/release-notes-v17.6) or later, the search experience is **All-In-One Search**.
3030

31+
> [!TIP]
32+
> To learn more about the new search experience, see both the [Better search in Visual Studio](https://devblogs.microsoft.com/visualstudio/new-better-search-in-visual-studio/) and [All-In-One Search available in 17.6](https://devblogs.microsoft.com/visualstudio/all-in-one-search-available-in-17-6/) blog posts.
33+
3134
### About the All-In-One Search experience
3235

3336
With **All-In-One Search**, not only can you search for features, but you can also search your code elements, such as files and symbols.
@@ -57,14 +60,38 @@ In Visual Studio 17.11 and later, you can set the scope of code search to the cu
5760

5861
:::image type="content" alt-text="Screenshot of code search scope options." source="./media/vs-2022/search-code-scope.png" :::
5962

60-
> [!TIP]
61-
> To learn more about the new search experience, see both the [Better search in Visual Studio](https://devblogs.microsoft.com/visualstudio/new-better-search-in-visual-studio/) and [All-In-One Search available in 17.6](https://devblogs.microsoft.com/visualstudio/all-in-one-search-available-in-17-6/) blog posts.
62-
63-
The text filter (**Shift**+**Alt**+**F**) in Code Search is available in preview in Visual Studio 17.9 and later. See [17.9 Preview 3 brings exciting changes to Code Search
64-
](https://devblogs.microsoft.com/visualstudio/17-9-preview-3-brings-exciting-changes-to-code-search/). Search for a text string, with options to match the case, match whole words, or use a regular expression. The regular expression format is described at [Regular expressions](/dotnet/standard/base-types/regular-expression-language-quick-reference).
63+
The text filter (**Shift**+**Alt**+**F**) in Code Search is available in preview in Visual Studio 17.9 and later. See [17.9 Preview 3 brings exciting changes to Code Search](https://devblogs.microsoft.com/visualstudio/17-9-preview-3-brings-exciting-changes-to-code-search/). Search for a text string, with options to match the case, match whole words, or use a regular expression. The regular expression format is described at [Regular expressions](/dotnet/standard/base-types/regular-expression-language-quick-reference).
6564

6665
:::image type="content" alt-text="Screenshot of text search with various options." source="./media/vs-2022/search-text-search-text-options-highlighted.png" :::
6766

67+
#### Navigate to a specific line in Code Search
68+
69+
With Visual Studio 17.12 and later, you can now navigate to a specific line in the current document or other specified document.
70+
71+
To go to a line in the *current* document, type colon (`:`) followed by the line number. For example, `:39` navigates to line 39 in the active file.
72+
73+
![Screenshot showing Go to line in current document.](./media/vs-2022/all-in-one-search-go-to-line-same-document.png)
74+
75+
You can also go to a line in a different document by typing the filename, colon, and then the line number. For example, `Order:43` navigates to line 43 in *Order.cs*. If you don't specify the exact file name, then the search will try to find the best match.
76+
77+
![Screenshot showing Go to line in different document.](./media/vs-2022/all-in-one-search-go-to-line-different-document.png)
78+
79+
#### Dock as a tool window
80+
81+
With Visual Studio 17.12 or later, you can dock the search window instead of having it floating in front. This can be helpful to avoid interrupting your code editing. Use the icon near the top right of the window to enable docking as a tool window.
82+
83+
![Screenshot showing docking icon on the search window.](./media/vs-2022/all-in-one-search-docking-icon.png)
84+
85+
You can use a similar icon on the tool window to revert back to the floating window.
86+
87+
#### Toggle preview pane
88+
89+
With Visual Studio 17.12 or later, you can toggle the preview pane. Use the eye icon to disable or enable the preview pane.
90+
91+
![Screenshot showing the icon to toggle the preview pane in the search window.](./media/vs-2022/all-in-one-search-toggle-preview.png)
92+
93+
Also new with Visual Studio 17.12, the preview panel's position automatically adjusts based on the dimensions of the search window.
94+
6895
::: moniker-end
6996

7097
## Search in Visual Studio 2022 version 17.5 or earlier

docs/javascript/javascript-project-system-msbuild-reference.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "MSBuild properties for JavaScript Project System (JSPS)"
33
description: Reference for the MSBuild properties and items that are understood by JSPS projects.
4-
ms.date: 10/19/2023
4+
ms.date: 11/07/2024
55
ms.custom: updateeachrelease
66
ms.topic: reference
77
ms.devlang: javascript
@@ -49,11 +49,11 @@ The `ShouldRunBuildScript` property specifies whether or not to run `npm run bui
4949

5050
```xml
5151
<PropertyGroup>
52-
<ShouldRunNpmBuildScript>false</ShouldRunNpmBuildScript>
52+
<ShouldRunBuildScript>false</ShouldRunBuildScript>
5353
</PropertyGroup>
5454
```
5555

56-
For projects containing only JavaScript that do not require building, set this property to `false`. Newly created React, Vue, and Angular projects usually fall in this category. In this scenario, build is used for production and not for debugging. Note that the `Build` and `Publish` commands are separate in JSPS projects, and `Publish` still runs even if this property is set.
56+
For projects containing only JavaScript that don't require building, set this property to `false`. Newly created React, Vue, and Angular projects usually fall in this category. In this scenario, build is used for production and not for debugging. Note that the `Build` and `Publish` commands are separate in JSPS projects, and `Publish` still runs even if this property is set.
5757

5858
## Command Properties
5959

@@ -119,7 +119,7 @@ If you modify the command, include `npm run` when using `npm`.
119119

120120
### PublishCommand
121121

122-
The `PublishCommand` property specifies the behavior for the `publish` target. If the associated `package.json` contains a `publish` script, the default `PublishCommand` value is already set to run this script. In npm, it is common to have pre- and post- publish scripts, which will also run.
122+
The `PublishCommand` property specifies the behavior for the `publish` target. If the associated `package.json` contains a `publish` script, the default `PublishCommand` value is already set to run this script. In npm, it's common to have pre- and post- publish scripts, which will also run.
123123

124124
If you modify the command, include `npm run` when using `npm`.
125125

docs/javascript/tutorial-asp-net-core-with-angular.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -142,6 +142,8 @@ Starting in Visual Studio 2022 version 17.3, you can publish the integrated solu
142142

143143
The publish process takes more time than it does for just an ASP.NET Core project, since the `npm run build` command gets invoked when publishing. The [BuildCommand](../javascript/javascript-project-system-msbuild-reference.md#buildcommand) runs `npm run build` by default.
144144

145+
If you publish to a folder, see [ASP.NET Core directory structure](/aspnet/core/host-and-deploy/directory-structure) for more information on the files added to the *publish* folder.
146+
145147
## Troubleshooting
146148

147149
### Proxy error

docs/javascript/tutorial-asp-net-core-with-react.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -133,6 +133,8 @@ The React app appears and is populated via the API. If you don't see the app, se
133133

134134
The publish process takes more time than it does for just an ASP.NET Core project, since the `npm run build` command gets invoked when publishing. The [BuildCommand](../javascript/javascript-project-system-msbuild-reference.md#buildcommand) runs `npm run build` by default.
135135

136+
If you publish to a folder, see [ASP.NET Core directory structure](/aspnet/core/host-and-deploy/directory-structure) for more information on the files added to the *publish* folder.
137+
136138
## Troubleshooting
137139

138140
### Proxy error

docs/javascript/tutorial-asp-net-core-with-vue.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -136,6 +136,8 @@ Starting in Visual Studio 2022 version 17.3, you can publish the integrated solu
136136

137137
The publish process takes more time than it does for just an ASP.NET Core project, since the `npm run build` command gets invoked when publishing. The [BuildCommand](../javascript/javascript-project-system-msbuild-reference.md#buildcommand) runs `npm run build` by default.
138138

139+
If you publish to a folder, see [ASP.NET Core directory structure](/aspnet/core/host-and-deploy/directory-structure) for more information on the files added to the *publish* folder.
140+
139141
## Troubleshooting
140142

141143
### Proxy error

0 commit comments

Comments
 (0)