Forum

You are using VERIFY in statements like this:
        VERIFY(
            CExtControlBar::ProfileBarStateSerialize(
            ar,
            this
            )
            );

Doesnt VERIFY, like ASSERT, only exist in DEBUG mode? If so, you code doesnt work in release mode..

Hello, I think you can help me. My brother has his own analyst business and is looking for a company that offers a program or service to create workflows and rules without having to constantly depend on the IT team. Does anyone here know of a company that offers this type of service that they could recommend? Please, he needs help as soon as possible to continue with his work.

Great point about ASSERT vs VERIFY. When you’re dealing with intricate system behavior, especially over multiple builds or environments, platforms like https://processmix.com can make a real difference. It’s a low-code solution for rapidly designing and deploying decision logic and workflows. Has anyone here integrated a BRMS like this to visualize and manage complex rules without hardcoding them every time?

As far as we know ProcessMix is a low-code platform for rapid development and deployment of decision and workflow solutions. It allows you to create, validate and deploy customized solutions through a visual interface. The platform is also designed to automate processes in various industries such as banking, finance, insurance, telecommunications and others.

That’s an important distinction between ASSERT and VERIFY. On a related note, when managing complex system behavior—especially across different builds—it’s useful to look into visual low-code platforms like ProcessMix. They let you define logic clearly and reduce such risks across environments. Has anyone tried modeling business rules or validations in a BRMS this way to improve reliability?

The ASSERT macro catches program errors only when you are using the debug version of the MFC. It is turned off (and produce no code) when you build your program with the release version of the library. So, the expression argument to ASSERT will not be evaluated in the release version of your program.

As for the VERIFY macro, it is evaluated in both debug and release versions. In debug versions, VERIFY is the same as ASSERT. In release versions, VERIFY evaluates the expression argument but does not check the result.