Skip to content

Commit 0387196

Browse files
authored
Merge pull request #2382 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to master to sync with https://github.com/MicrosoftDocs/visualstudio-docs (branch master)
2 parents 3ebe6b5 + 70daf31 commit 0387196

File tree

2 files changed

+5
-3
lines changed

2 files changed

+5
-3
lines changed

docs/extensibility/vsix-extension-schema-2-0-reference.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -176,7 +176,9 @@ A VSIX deployment manifest file describes the contents of a VSIX package. The fi
176176

177177
You can create your own types, and give them unique names. At run time inside Visual Studio, your code can enumerate and access these custom types through the Extension Manager API.
178178

179-
- Path - the relative path to the file or folder within the package that contains the asset.
179+
- `Path` - the relative path to the file or folder within the package that contains the asset.
180+
181+
- `TargetVersion` - the version range in which the given asset applies to. Used for shipping multiple versions of assets to different versions of Visual Studio. Requires Visual Studio 2017.3 or newer to have effect.
180182

181183
- `AnyAttribute*` - An open-ended set of attributes that'll be exposed at runtime as a name-value pair dictionary.
182184

@@ -211,4 +213,4 @@ A VSIX deployment manifest file describes the contents of a VSIX package. The fi
211213
```
212214

213215
## See Also
214-
[Shipping Visual Studio Extensions](../extensibility/shipping-visual-studio-extensions.md)
216+
[Shipping Visual Studio Extensions](../extensibility/shipping-visual-studio-extensions.md)

docs/test/live-unit-testing.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -151,7 +151,7 @@ There are some differences between Live Unit Testing automatically running and u
151151

152152
## Live Unit Testing and large solutions
153153

154-
If your solution has 10 or more projects, when you start Live Unit Testing and there is no persisted data, or when you select the **Test**, **Live Unit Testing**, **Reset Clean** option from the top-level Visual Studio menu, Visual Studio displays the following dialog to warn you that dynamic execution of large numbers of tests in large projects can severely impact performance. If you select **OK**, Live Unit Testing executes all texts in the solution. If you select **Cancel**, you can select the tests to execute. For information on how to do this, see the following section, [Including and excluding test projects and test methods](#including-and-excluding-test-projects-and-test-methods).
154+
If your solution has 10 or more projects, when you start Live Unit Testing and there is no persisted data, or when you select the **Test**, **Live Unit Testing**, **Reset Clean** option from the top-level Visual Studio menu, Visual Studio displays the following dialog to warn you that dynamic execution of large numbers of tests in large projects can severely impact performance. If you select **OK**, Live Unit Testing executes all tests in the solution. If you select **Cancel**, you can select the tests to execute. For information on how to do this, see the following section, [Including and excluding test projects and test methods](#including-and-excluding-test-projects-and-test-methods).
155155

156156
![Live Unit Testing dialog for large projects](media/lut-large-project.png)
157157

0 commit comments

Comments
 (0)