question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

SA1642 Warnings occur when using .NET Core SDK 2.1.300

See original GitHub issue

I’ve recently updated to the latest version of the .NET Core SDK, version 2.1.300. I’m now seeing SA1642 warnings when running dotnet build on a project which changes the documentationCulture to en-GB. I’ve managed to replicate this with version 2.1.300 on both Ubuntu and Windows.

It also appears that other rules are being respected. For example, I’ve changed the usingDirectivesPlacement from that standard and get no warnings. I’ve also dropped in a global.json into my solution to downgrade the .NET Core SDK version to 2.1.200 and 2.1.201. When I do this, I no longer get any warnings.

I was initially running version 1.1.0-beta006 and thought that might be a cause, but when I also upgraded to 1.1.0-beta007 the issues also occurred.

My stylecop.json looks like:

{
  "$schema": "https://raw.githubusercontent.com/DotNetAnalyzers/StyleCopAnalyzers/master/StyleCop.Analyzers/StyleCop.Analyzers/Settings/stylecop.schema.json",
  "settings": {
    "documentationRules": {
      "documentationCulture": "en-GB"
    },
    "orderingRules": {
      "blankLinesBetweenUsingGroups": "omit",
      "usingDirectivesPlacement": "outsideNamespace"
    }
  }
}

Let me know if you need any other information.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:8 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
sharwellcommented, Nov 22, 2018

@fubar-coder I would prefer to see someone put time into fixing the underlying bug instead. All of the code in question is open source.

1reaction
vweijsterscommented, Jun 15, 2018

@nguerrera No, that works fine.

Read more comments on GitHub >

github_iconTop Results From Across the Web

NETSDK1045: The current .NET SDK does not support ...
This error occurs when the build tools can't find the version of the .NET SDK that's needed to build a project. This is...
Read more >
Warning on dotnet core 2.1.0 API project
Api.csproj : warning NU1701: Package 'Microsoft.AspNet.Cors 5.2.6' was restored using '.NETFramework,Version=v4.6.1' instead of the project ...
Read more >
Irrelevant build warning about EOL .NET core SDKs ...
Recently, a change to the build agents recently causes this warning to appear as the first message in our restore and build DotNetCoreCLI...
Read more >
Chapter 7. Known Issues .NET Core 2.1
.NET Core SDK 2.1.3xx contains an incorrect NETStandard.Library version. Using this SDK version may result in build failures. To correct this issue ...
Read more >
Visual Studio 2019 unable to locate .Net Core SDK
Step 1) First run dotnet --list-sdks from the command line (as in Grzegorz Smulko's answer). Take note of the greatest version number.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found