Automation MadCap Flare Technical communication

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

Posted on Author msander Comments(5)

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 http://techwritingengineer.com/automated-qa-checking-for-broken-links-in-your-flare-output/

msander

Related Articles
Kanban Lean Productivity Technical communication Uncategorized

Keep it Lean – Become more productive and motivated

Posted on Author msander

This article was originally published in ISTC Communicator, Summer 2016. Lean started in the automotive industry with Toyota’s Production System, but the ideas and principles are universal, and can be applied to any industry. The idea of Lean is to maximize customer value while minimizing waste, thus creating more value for customers with fewer resources. […]
Lean Technical communication Uncategorized

Getting Started with Lean Manufacturing Principles

Posted on Author msander

Here’s a collection of videos, articles, books, and courses to help you learn more about lean manufacturing, and help you come up with some great ideas on how to implement lean in the field of technical communication. Enjoy! 🙂 PS. Don’t miss the opportunity to learn how to use a Kanban TOC  at my TCUK presentation in […]
Kanban Lean MadCap Flare Uncategorized

How to get started with Lean Thinking in Techcomm

Posted on Author msander

Do you want to know more about lean ideas, and how you can start implementing them using your favorite authoring tool? Keep reading! Lean principles These are some of the main principles in lean thinking: Define value from your customers’ perspective Map the value stream for each product that provides that value, and challenge all non-value-adding […]

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?

    Reply

    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.

      Reply

      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.

        Reply

Leave a Reply

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