The class containing MsBuildIssuesAliases.MsBuildXmlFileLoggerFormat should be in Cake.Issues.MsBuild namespace, instead of Cake.Issues.MsBuild.LogFileFormat.

Log file content may contain control characters which should be filtered out.

Update to Cake.Issue 0.4.1 and use log file format infrastructure from Cake.Issues

MSBuild
The MSBuild toolset version has been changed from 15.0 to Current. MSBuild.exe is now in %VSINSTALLDIR%\MSBuild\Current\Bin\MSBuild.exe.
MSBuild (and Visual Studio) now targets .NET Framework 4.7.2. If you wish to use new MSBuild API features, your assembly must also upgrade, but existing code will continue to work.

Add repository metadata to nuspec file

Website should link to cakeissues.net

XmlFileLoggerFileFormat should return column of issue

Update to Cake.Issues 0.9.0

Bump MSBuild.StructuredLogger from 2.0.88 to 2.0.94

This provides some immediate information that a repository is using
Cake.Recipe, and it is a convention now followed by a number of other
repositories.

Release first version based on Cake.Prca.Issues.InspectCode

For latest Cake.Recipe we need to update Cake to 0.23

We performed an automated audit of your Cake addin and found that it does not follow all the best practices.

We encourage you to make the following modifications:

• You are currently referencing Cake.Core 0.28.0. Please upgrade to 0.33.0
• The nuget package for your addin should use the cake-contrib icon. Specifically, your addin's .csproj should have a line like this: <PackageIconUrl>https://cdn.jsdelivr.net/gh/cake-contrib/graphics/png/cake-contrib-medium.png</PackageIconUrl>.

Apologies if this is already being worked on, or if there are existing open issues, this issue was created based on what is currently published for this package on NuGet.

This issue was created by a tool: Cake.AddinDiscoverer version 3.12.1

The following Xml MSBuild log causes an System.ArgumentOutOfRangeException : startIndex cannot be larger than length of string.

<?xml version="1.0" encoding="utf-8"?>
<build started="3/11/2019 22:29:45">
  <warning code="SA1633" file="File.cs" line="1" column="1" started="3/11/2019 22:29:59"><![CDATA[The file header is missing or not located at the top of the file.]]></warning>
</build>

Update to Cake.Issues 0.2.0

Update to Cake.Issues 0.8.0

Update to Cake.Issues 0.4.0

msdn.microsoft.com was replaced with docs.microsoft.com and the rule url should be updated

Build against Cake 0.22

Original issue: https://github.com/cake-contrib/Cake.Prca.Issues.MsBuild/issues/42

The addin should provide a constant containing the value which is used for the ProviderType property of issues from this provider.

Build with Cake 0.28.0 and latest version of Cake.Recipe

XmlFileLoggerFileFormat should return column of issue

Hi,

Although MSBuild XML log contains over 1000+ warnings

  <warnings>1033</warnings>
  <errors>0</errors>
  <starttime>5/19/2018 10:15:28 AM</starttime>
  <endtime>5/19/2018 10:15:54 AM</endtime>
  <timeelapsed>00:00:25.5523060</timeelapsed>

which contains both StyleCop warnings and Code Analysis warnings, only 2 issues are reported by:

    var issuesSettings = MsBuildIssuesSettings.FromFilePath(msBuildLogFile, MsBuildXmlFileLoggerFormat);
    var issues = ReadIssues(MsBuildIssues(issuesSettings), Environment.CurrentDirectory);
    Information(issues.Count());

Which are neither CA or SA warnings.

Is there maybe some parameter that I'm missing?

I can provide the XML log, but I'd rather not upload it on a public location.

Thank you,
Cosmin

Addin should support .NET Core and Cake CoreCLR runner

Build against Cake 0.28.0

Update to Cake.Issues 0.3.0

In my Build script I'm attempting to do this to generate the build output for the Issue tool.

DotNetCorePublish(".", new DotNetCorePublishSettings
        {
            Configuration = configuration,
            NoRestore = true,
            MSBuildSettings = new DotNetCoreMSBuildSettings()
                .WithLogger(
                    Context.Tools.Resolve("MSBuild.ExtensionPack.Loggers.dll").FullPath,
                    "XmlFileLogger",
                    $"logfile=\"{msBuildLogFile}\";verbosity=Detailed;encoding=UTF-8"
                )
        });

This does not work as the MSBuild.ExtensionPack.Loggers.dll doesn't work in the dotnet core msbuild Per dotnet/msbuild#2111.

Is there a work around? I see #38 which might also work but doesn't seem to be an active case.

Update to Cake.Issues 0.6.0

BinaryLogFileFormat should return range of line and column

Update to Cake.Issues 0.5.0

Build against Cake 1.0

Bump MSBuild.StructuredLogger to latest version. This bumps requirements from MsBuild 14 to MsBuild 15.1.0

We performed an automated audit of your Cake addin and found that it does not follow all the best practices.

We encourage you to make the following modifications:

• You are currently referencing Cake.Core 0.26.0. Please upgrade to 0.28.0
• The Cake.Core reference should be private. Specifically, your addin's .csproj should have a line similar to this: <PackageReference Include="Cake.Core" Version="0.28.0" PrivateAssets="All" />

Cake 0.26.0 introduced breaking changes. To support Cake versions >= 0.26.0 this addin should be built against Cake 0.26.0

If a warning doesn't contain a message currently an exception is thrown (see cake-contrib/Cake.Recipe#269). Instead we should ignore these warnings.

It would be great to have support for the latest binlog version 9 that gets outputted when using /binarylogger together with dotnet build (Assuming the latest version of MSBuild as well).

I am guessing this support would be included with the update with the PR #158.

We should build and run tests also on macOs

Build against Cake 0.33.0

Update to Cake.Issues 0.7.0

Original issue: https://github.com/cake-contrib/Cake.Prca.Issues.MsBuild/issues/43

Add support for Binary Logs. See Reading MSBuild .binlogs programmatically for example.

Parse errors from log files in MsBuildBinaryLogFileFormat and MsBuildXmlFileLoggerFormat

• Support parsing of errors in MsBuildXmlFileLoggerFormat (GH-199)
• Support parsing of errors in MsBuildBinaryLogFileFormat (GH-205)
• Update feature documentation (GH-204)

I spend a long time debugging why Issues didn't have the correct paths set. It turns out that using a logger where the verbosity is set to Quiet does not contain the <project... element that contains the project path. The issue is that XmlFileLoggerLogFileFormat is silent about it and you have to debug a lot to discover it.

I suggest adding a disclaimer somewhere or make XmlFileLoggerLogFileFormat throw. What do you think?

Set IIssue.Project to name of the assembly

We should build and run unit tests also on Linux

There's currently a Cake alias property for retrieving the name of the issue provider type (MsBuildIssuesProviderTypeName). This requires a Cake context and there might be situations where no context is available. There should be a way to retrieve the issue provider type name without requiring a context.

Support version 8 of binlog file format

We performed an automated audit of your Cake addin and found that it does not follow all the best practices.

We encourage you to make the following modifications:

• The Cake.Core reference should be private. Specifically, your addin's .csproj should have a line similar to this: <PackageReference Include="Cake.Core" Version="0.28.0" PrivateAssets="All" />

Apologies if this is already being worked on, or if there are existing open issues, this issue was created based on what is currently published for this package on NuGet.org and in the project on github.

I'd love to buy you a 🍺

Several other projects I've worked with use Open Collective, but I'd be willing to contribute a bit financially to any way that works for you

Original issue: https://github.com/cake-contrib/Cake.Prca.Issues.MsBuild/issues/44

For Sandcastle Help File Builder warnings are created for a file, but with line 0:

<warning code="BE0006" file="SHFB" line="0" column="0" started="9/7/2017 7:22:31 AM"><![CDATA[Unable to locate any documentation sources for 'C:\src\MyProject.csproj' (Configuration: Debug Platform: AnyCPU)]]></warning>

CodeAnalysisIssue doesn't allow issues to be created with line 0

We should use an embedded icon in the NuGet package