The main features of this release focus on Chilkat’s Ai class, enabling interactive AI response streaming directly into embedded desktop application browsers. It supports Azure, custom base URLs for OpenAI-compatible providers, and local providers like Ollama. ✨ New Features Ai Real-Time Streaming AI Responses to Embedded Browsers in Desktop Apps — Stream AI responses […]
Previous Version: Chilkat v11.1.0 Release Notes The main addition in v11.2.0 is the Chilkat.Ai class, and the Chilkat.StringBuilder.MarkdownToHtml method. Ai: The Chilkat AI class provides a unified API for interacting with different AI providers: OpenAI, Google, Claude, xAI, Perplexity, and DeepSeek. It provides functionality for conversation management, multimodal inputs, and streaming mode. Markdown to HTML […]
Starting with the v10.0.0 release (end of September 2024), Chilkat moves to standard semantic versioning. Prior to this release, for various technical reasons, Chilkat was stuck with versions 9.5.0.xx, where only xx changed. For this first leap to semantic versioning, where the major version changes to 10 (from 9), there are no backward incompatible changes. […]
The format of email is MIME. A simple MIME message consists of headers followed by a body. For example, here’s a simple text/plain email: From: sender@example.com To: recipient@example.com Subject: Example Email Content-Type: text/plain; charset=”UTF-8″ Hello, This is a simple plain text email. Regards, Sender MIME can be multipart. Here’s a text/plain email with a PDF […]
In rare cases, an email’s MIME might be structured in a way that is highly unusual and doesn’t follow conventions. In other words, the nested MIME structure of an email should follow conventions that make it possible to semantically understand the purpose of each MIME part — such as an attachment, or an image to […]
It was found that in some cases, OpenSSL may produce MIME with a mixture of both bare-LF line-endings and CRLF line-endings. MIME documents *should* always use CRLF line endings. The mixing of both line-ending types in a single MIME document caused the LoadMimeBytes method to skip past the end of the top-level header (terminated by […]
Chilkat v9.3.0, being released this week, now supports the ability to create CAdES-BES and CAdES-EPES digital signatures via the MailMan, Mime, and Crypt2 objects. All three objects/classes now include the following new properties: bool CadesEnabled; string CadesSigPolicyId; string CadesSigPolicyUri; string CadesSigPolicyHash; (base64 encoded representation of hash) To create a CAdES-BES signature, simply set the CadesEnabled […]
Question: Is it possible to “grab“ mime parts directly from incoming HTTP request with Chilkat.Mime object? LoadMimeFile() works like a charm. Answer: Yes, if you are using a ChilkatDotNet2.dll that is more than a few weeks old (from the date of this post), download the latest from http://www.chilkatsoft.com/preRelease/ChilkatDotNet2.zip The latest build has a new feature […]
Question: Is it possible to convert MIME to plain-text? Answer: The Chilkat MIME and/or Email API’s may be used to extract the plain-text body (or bodies) and/or HTML bodies from a MIME message. If a MIME-part is already plain-text, no conversion is necessary. It’s simply a matter of using the Chilkat MIME or Email API […]
