Automation MadCap Flare Technical communication

Automated QA: Checking for broken links in your Flare output – now also for HTTP links

The CheckLinks tool now also finds broken http and https links in addition to finding broken local relative links.

The syntax for running the tool is, for example:

C:\> Checklinks2 "C:\OutputFolder" "C:\LogFolder"

For info about the existing tool, see

5 Replies to “Automated QA: Checking for broken links in your Flare output – now also for HTTP links

  1. This sounds good. But when I run it nothing happens: no error message but no text file either.

    Any ideas what the problem might be?

    1. Great, thanks. That works fine. It doesn’t like it if you leave trailing backslashes in the paths though. I get:

      Unhandled Exception: System.ArgumentException: Illegal characters in path.
      at System.IO.Path.CheckInvalidPathChars(String path, Boolean checkAdditional)
      at System.IO.Path.GetFileName(String path)
      at System.IO.StreamWriter.CreateFile(String path, Boolean append, Boolean checkHost)
      at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize, Boolean checkHost)
      at System.IO.File.InternalWriteAllText(String path, String contents, Encoding encoding, Boolean checkHost)
      at System.IO.File.WriteAllText(String path, String contents)
      at HREF_CHECKER.Module1.WriteLogFile(String logText, String logPath)
      at HREF_CHECKER.Module1.Main()

      Feature request: print some output on the command line – e.g.
      “x broken links found. See log file ”

      Thanks again. That’s a really useful little tool.

      1. In my previous comment I used angle-bracketed text which disappeared on submit.
        After “See log file” add the path/name of the log file.

Leave a Reply

Your email address will not be published. Required fields are marked *