# BRLibToHelp - Generate CHM Help Files for Your B&R Automation Libraries

**URL:** <https://community.br-automation.com/t/brlibtohelp-generate-chm-help-files-for-your-b-r-automation-libraries/9675>\
**Category:** Others\
**Tags:** automation-studio, toolkit\
**Created:** [January 13, 2026, 8:45am UTC](https://community.br-automation.com/t/brlibtohelp-generate-chm-help-files-for-your-b-r-automation-libraries/9675 "2026-01-13T08:45:31Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![florent.boissadier](https://avatars.discourse-cdn.com/v4/letter/f/FF8800/32.png) [@florent.boissadier](https://community.br-automation.com/u/florent.boissadier)\
**Post date:** [January 19, 2026, 4:12pm UTC](https://community.br-automation.com/t/brlibtohelp-generate-chm-help-files-for-your-b-r-automation-libraries/9675/9 "2026-01-19T16:12:54Z")

</div>

I’m not entirely convinced that this functionality belongs in AS or the AS Code extension, given its reliance on third-party executables and DLLs. While these dependencies are bundled into the executable for this project, they remain mandatory and add complexity.

CHM files feel outdated as a documentation format for code or applications. Instead, I’d advocate for an AS Code extension that generates Markdown documentation directly from a library. This approach aligns better with modern practices—it would allow documentation to live seamlessly in a Git repository alongside the source code, which is how I’d prefer to document my own libraries.

Let me know your thoughts!

Best regards,  
Florent

---

_[View the full topic](https://community.br-automation.com/t/brlibtohelp-generate-chm-help-files-for-your-b-r-automation-libraries/9675)._