I figured as much and I must say that I never noticed any performance issues (without ever benchmarking it) but I was wondering since our doxygen comments are important. Thanks for the reply and the test you ran. I honestly did not think of testing it that way myself.

Regards,
Jan

We use doxygen to document much of our shared CTRL/CTRL++ code base. These comments can become pretty verbose. Since CTRL is a interpreted language, is there a performance impact when having many comments and sometimes pretty long ones? I can imagine that initially loading and parsing the file will ...

I suspected as much.
Thanks for the reply!

Regards,
Jan

Hello,

A client of ours asked the question if it is possible to use SAML 2.0 (https://en.wikipedia.org/wiki/SAML_2.0 ) for SSO using the ULC UX.

Since I do not know the answer to this question does someone here know whether or not this is possible?

Regards,
Jan

We have been asked by a client if it is possible to license WinCC OA not using a physical license dongle or external license services (I.E. a software license on the local machine). Reading through the documentation that should be possible but I would like to know if there are any issues to consider...

Just downloaded P13 and it seems to be working again. Thanks for the heads up!

If you could then yes please. If you are running P10 or lower then maybe be careful updating to the later patches. If you are running P11 or higher then I will have to take a look at my environment.

Regards,
Jan

Just created a new empty API manager using the supplied templates (WinCC OA 3.19 P12). Running that manager exhibits the same behavior. The output of that manager is: WCCOAWCCOAmanager1(6), 2024.06.24 14:41:54.947, IMPL, INFO, 0, , Microsoft.Hosting.Lifetime, Application started. Press Ctrl+C to shu...

Just a question... Has anybody created an API manager for WinCC OA 3.19 using the .NET API? I have noticed that when updating to Patch 11 or 12 and recompiling my API managers to use the ETM.WINCCOA.Manager package of P11 or P12 result in the API manager crashing with a System.AccessViolationExcepti...

I'm afraid the packages in 3.19 P9 are broken again. The ETM.WCCOA.Manager.3.19.9 package depends on ETM.WCCOA.Basics >= 1.3.0 but version 1.2.3 is installed with the patch. This is becoming a serious issue since managers compiled against the older packages do no longer work properly when P8 or P9 i...