Skip to content

Commit 763fd81

Browse files
committed
Updated documentation to refer to Visual Studio 2017
1 parent f2a4f0d commit 763fd81

2 files changed

Lines changed: 4 additions & 6 deletions

File tree

CONTRIBUTING.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,4 @@ You can also help by filing issues, participating in discussions and doing code
2626

2727
## Building
2828

29-
Visual Studio 2015 RC is required for building this repository.
30-
The Visual Studio 2015 RC SDK is required for building the vsix extension project and for
31-
debugging in an experimental visual studio hive.
29+
Visual Studio 2017 (Community Edition or higher) is required for building this repository.

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,8 +14,8 @@ The preferable way to use the analyzers is to add the nuget package [StyleCop.An
1414
to the project where you want to enforce StyleCop rules.
1515

1616
The severity of individual rules may be configured using [rule set files](https://msdn.microsoft.com/en-us/library/dd264996.aspx)
17-
in Visual Studio 2015. **Settings.StyleCop** is not supported, but a **stylecop.json** file may be used to customize the
18-
behavior of certain rules. See [Configuration.md](documentation/Configuration.md) for more information.
17+
in Visual Studio 2015 or newer. **Settings.StyleCop** is not supported, but a **stylecop.json** file may be used to
18+
customize the behavior of certain rules. See [Configuration.md](documentation/Configuration.md) for more information.
1919

2020
For users upgrading from StyleCop Classic, see [KnownChanges.md](https://github.com/DotNetAnalyzers/StyleCopAnalyzers/tree/master/documentation/KnownChanges.md)
2121
for information about known differences which you may notice when switching to StyleCop Analyzers.
@@ -34,7 +34,7 @@ Install-Package StyleCop.Analyzers
3434

3535
## Team Considerations
3636

37-
If you use older versions of Visual Studio in addition to Visual Studio 2015, you may still install these analyzers. They will be automatically disabled when you open the project back up in Visual Studio 2013 or earlier.
37+
If you use older versions of Visual Studio in addition to Visual Studio 2015 or Visual Studio 2017, you may still install these analyzers. They will be automatically disabled when you open the project back up in Visual Studio 2013 or earlier.
3838

3939
## Contributing
4040

0 commit comments

Comments
 (0)