Hi there,

      as statet in this MSDN blog post a MSBuild-Warning may contain a subcategory, like in this real warning (note the additional word "Hint")

      E:\workspace\project\subdir\file.sub1.sub2.pas(4522): Hint warning H2164: Variable 'lTaskDialog' is declared but never used in 'TDialog.ShowTaskDialog' [E:\workspace\projext\subdir\project.dproj]

      Unfortunately the pre-shipped parser MSBuild does not recognise those kind of warning (or error, info,...)

      The regular expression attached in MSBuild_pattern_subcategory.txt solved that problem for us.

      We are using a custom parser for now, but it might be desirable to change
      the pattern in default MSBuild Parser as the one attached is more close to the default behaviour in msbuild (see blog post).

      Links: MSDN blog post on VisualStudio error Messages

          [JENKINS-27914] MSBuild-Parser ignores optional Subcategory

          JAM Software created issue -
          JAM Software made changes -
          Attachment New: MSBuild_pattern_subcategory.txt [ 29444 ]
          JAM Software made changes -
          Description Original: Hi there,

          as statet in [this MSDN blog post|http://blogs.msdn.com/b/msbuild/archive/2006/11/03/msbuild-visual-studio-aware-error-messages-and-message-formats.aspx] a MSBuild-Warning may contain a subcategory, like in this real warning (note the additional word "Hint")
          {quote}
          E:\workspace\project\subdir\file.sub1.sub2.pas(4522): *Hint* warning H2164: Variable 'lTaskDialog' is declared but never used in 'TDialog.ShowTaskDialog' [E:\workspace\projext\subdir\project.dproj]
          {quote}

          Unfortunately the pre-shipped parser MSBuild does not recognise those kind of warning (or error, info,...)

          The regular expression attached in[^MSBuild_pattern_subcategory.txt] solved that problem for us.

          We are using a custom parser for now, but it might be desirable to change
          the pattern in default MSBuild Parser as the one attached is more close to the default behaviour in msbuild (see blog post).

          Links: [MSDN blog post on VisualStudio error Messages|http://blogs.msdn.com/b/msbuild/archive/2006/11/03/msbuild-visual-studio-aware-error-messages-and-message-formats.aspx]
          New: Hi there,

          as statet in [this MSDN blog post|http://blogs.msdn.com/b/msbuild/archive/2006/11/03/msbuild-visual-studio-aware-error-messages-and-message-formats.aspx] a MSBuild-Warning may contain a subcategory, like in this real warning (note the additional word "Hint")
          {quote}
          E:\workspace\project\subdir\file.sub1.sub2.pas(4522): *Hint* warning H2164: Variable 'lTaskDialog' is declared but never used in 'TDialog.ShowTaskDialog' [E:\workspace\projext\subdir\project.dproj]
          {quote}

          Unfortunately the pre-shipped parser MSBuild does not recognise those kind of warning (or error, info,...)

          The regular expression attached in [^MSBuild_pattern_subcategory.txt] solved that problem for us.

          We are using a custom parser for now, but it might be desirable to change
          the pattern in default MSBuild Parser as the one attached is more close to the default behaviour in msbuild (see blog post).

          Links: [MSDN blog post on VisualStudio error Messages|http://blogs.msdn.com/b/msbuild/archive/2006/11/03/msbuild-visual-studio-aware-error-messages-and-message-formats.aspx]
          SCM/JIRA link daemon made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 162508 ] New: JNJira + In-Review [ 196969 ]

            drulli Ulli Hafner
            jamsw JAM Software
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: