About Deprecated Methods Returning Objects

In Chilkat v11.0.0, the bulk of what was marked deprecated falls into one main category:

What changed in v11.0.0

Most deprecated methods are the older-style methods that return an object instance (for example, returning an Email, JsonObject, Cert, PrivateKey, StringBuilder, etc. directly as the return value).

Those methods were replaced with equivalent “modern” methods that:

• Return a boolean (success/fail), and
• Return the “object result” by filling an output object passed as the last parameter (output-only argument).

This avoids returning newly-allocated objects from the API and makes memory/ownership clearer and more consistent across languages/wrappers.

Deprecated does not mean removed

Even though those object-returning methods are marked deprecated in v11.0.0:

• They still exist in v11.0.0 (and continue to work).
• Deprecation is guidance for new code, and a path for gradually updating existing code—not a sudden break.

Where to find them in the docs

In the reference documentation for v11.x:

• The deprecated methods are still documented, but they’re moved into a separate “Deprecated” section.
• That “Deprecated” section is located at the bottom of each reference documentation page for the class/object.

So you’ll typically see the “normal” (current) methods first, and then a “Deprecated” block at the end containing the older object-returning methods.

How to transition: per-method migration links

For each deprecated method shown in that Deprecated section:

• The docs include a link to an example specifically explaining how to transition from the old pattern (method returns an object) to the new pattern (method returns boolean, and the object comes back in the last parameter).

That example is meant to be a direct “before/after” guide so you can quickly update code without guessing which new method replaces the old one.