https://forge.codesys.com/forge/talk/Engineering/thread/7d678af7bd/2020-02-27T14:57:03.064000ZRecent posts to Library Documentation check with script2020-02-27T14:57:03.064000Z2020-02-27T14:57:03.064000ZAnonymoushttps://forge.codesys.com/u/*anonymous/https://forge.codesys.com6619f855e80f537a946ce565b3972383e784a127

<div class="markdown_content"><p><em>Originally created by:</em> M.Schaber</p> <p>The online help for the library documentation should describe how the json file is exported and how the libdoc.exe is used for transformation. It returns an error code if something goes wrong.</p> <p>This chain of tools can also be triggered via python scripts, you can use the .NET System.Diagnostics.Process API or the python process apis to control the libdoc.exe.</p> <p>We have some scripts in-house, but they need to be a bit polished before being published, we expect to have one available next week.</p></div>

2020-02-27T14:57:02.205000Z2020-02-27T14:57:02.205000Zesskaeyhttps://forge.codesys.com/u/esskaey/https://forge.codesys.combca58fd1189bd15c582b64a04335aabae9ae5602

<div class="markdown_content"><p>Hello, </p> <p>I am currently using Codesys v3.5 sp8 to build libraries and subsequently *.compiled-library files with DocFormat property as reStructuredText. Along with the POUs, the documentation is also compiled for Errors ( during save Project as compiled library). Is there any means to check the "library documentation" for Errors using script before starting to save it as compiled library?. </p> <p>An example script will help me a Long way. Thanks in advance.</p> <p>BR,</p> <p>SK</p></div>