Skip to content

Commit 22fae9f

Browse files
authored
Merge pull request #6345 from Mikejo5000/mikejo-br17
GitHub issue fixes
2 parents 4d854b5 + ac76cf1 commit 22fae9f

File tree

3 files changed

+7
-2
lines changed

3 files changed

+7
-2
lines changed

docs/javascript/quickstart-ide-orientation-js.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ If you haven't already installed Visual Studio, go to the [Visual Studio downloa
1919

2020
::: moniker-end
2121

22-
::: moniker range="vs-2019"
22+
::: moniker range=">=vs-2019"
2323

2424
If you haven't already installed Visual Studio, go to the [Visual Studio downloads](https://visualstudio.microsoft.com/downloads) page to install it for free.
2525

197 KB
Loading

docs/test/troubleshooting-code-coverage.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Troubleshooting Code Coverage
3-
ms.date: 11/04/2016
3+
ms.date: 03/31/2020
44
ms.topic: troubleshooting
55
ms.author: mikejo
66
manager: jillfra
@@ -16,7 +16,12 @@ The code coverage analysis tool in Visual Studio collects data for native and ma
1616

1717
If you choose an **Analyze Code Coverage** command on the **Test** menu, and if the build and tests run successfully, then you should see a list of results in the **Code Coverage** window. You might have to expand the items to see the detail.
1818

19+
::: moniker range=">=vs-2019"
20+
![Code coverage results with coloring](../test/media/vs-2019/codecoverage1.png)
21+
::: moniker-end
22+
::: moniker range="vs-2017"
1923
![Code coverage results with coloring](../test/media/codecoverage1.png)
24+
::: moniker-end
2025

2126
For more information, see [Use code coverage to determine how much code is being tested](../test/using-code-coverage-to-determine-how-much-code-is-being-tested.md).
2227

0 commit comments

Comments
 (0)