About Despejo47

You can remove the addon from the handler again, which basically stops it from being called. I wouldn't call this "clean" either, since the Nexeed framework clearly does want you to do that. And depending on what the add-on is doing exactly, it may have some weird consequences. If you do it straight at the end of OnUnitInitialize (after the exported code), it should be fine in most cases though. You can also link this to the unit state if you wanted to, but that requires you to either manually add this to all your handlers or create new handlers that extend the Nexeed version, like we have in our ATMOx handlers anyway. I'll contact you separately how to do this, I don't really want to advertise this solution publically. Maybe the Nexeed developer team picks up on your requirement and adds this to the official framework someday. ... View more

Colleagues also made the experience that "Disable Virtualization based Security" had to be implemented via the IT service portal:   ... View more

Once more you are right. Nexidator nick is not coming for free. Where exactly are you missing the property and what seems to be different to a normal CommandHandler? In the command Handler that is implemented on the CPS What's the nodeType of your object in the OOD file? The was the fault baseType="OpconCmdHandler" is missing. Does your object generate a project-specific derivation for the unit FB? Yes Once baseType="OpconCmdHandler" of the base type is added right, the property can be selected. Aniway we are using rUnit that is allways generated.   Thanks     ... View more

Thanks for your quick answer. We will wait eager newer version that solve the problem with enumerations. ... View more

This is a great new! We will implement this new version as soon as possible to solve our customer requirements. Many thanks! ... View more