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. […]
Next Version: Chilkat v11.2.0 Release Notes Previous Version: Chilkat v11.0.0 Release Notes Regular Expressions: Added PCRE2 (Perl Compatible Regular Expressions, version 2) regular expression capabilities to the StringBuilder class in the RegexMatch and RegexReplace methods.This is the first time Chilkat is utilizing third-party open-source software by incorporating PCRE2, which can be found at https://github.com/PCRE2Project/pcre2. Due […]
Starting in Chilkat v11.0.0, applications using CreateObject (or similar) should pass an identifier beginning with “Chilkat.”. If your application uses “Chilkat_9_5_0.”, then strings must be updated to use “Chilkat.”. For example: The reference documentation web page for each Chilkat ActiveX object shows the object creation statements for various programming languages. For example: (ASP) set obj […]
Next Version: Chilkat v11.1.0 Release Notes Previous Version: Chilkat v10.1.3 Release Notes Backward Compatibility: This is a major version release that includes some backward incompatible changes. The web pages at Chilkat v11.0.0 Backward Incompatible Changes provide details. New Methods and Properties: There are a many new methods and properties that have been added. Almost all […]
Next Version: Chilkat v11.0.0 Release Notes Previous Version: Chilkat v10.1.2 Release Notes This minor release was made shortly after v10.1.2, mainly to fix the Email FROM header bug introduced in v10.1.2. Socket: Added the GetAdaptersAddresses method to get the local LAN IP address and MAC address for each network adapter. Email: Fixed a problem relating […]
You made a mistake and set an AES encryption key in the wrong way like this: Chilkat.Crypt2 crypt = new Chilkat.Crypt2(); crypt.KeyLength = 256; crypt.CryptAlgorithm = “aes”; // This is the error. We passed base64 (or anything that is NOT a hexidecimal string) // And then asked Chilkat to decode it as hex. crypt.SetEncodedKey(“rZFNAfY7CirLtWxKiRU187k9mqcGCBZnV4QrmBvsboE”,”hex”); And […]
Next Version: Chilkat v10.1.3 Release Notes Previous Version: Chilkat v10.1.0 Release Notes XmlDSigGen: In v10.0.0 Chilkat started automatically using and fixing for SigningCertificateV2 for cases where the xmlns:xades=”http://uri.etsi.org/01903/v1.3.2#” (and also v1.4.1 and v1.4.2), which is technically correct. However many govt validators, specifically Poland, Saudia Arabia, and others, reject XML signatures using SigningCertificateV2. Chilkat backed out […]
To prevent the password dialog from being shown when you use a private key in the Apple Keychain, you need to adjust the key’s access control settings. Specifically, you can configure the key to allow applications to access it without prompting the user. Here’s how to achieve this: Steps to Prevent Password Dialogs 1. Open […]
To add a reference to a “.nupkg” file (a NuGet package) in a .NET 6.0 project, you can follow these steps: Option 1: Add the .nupkg File to a Local NuGet Source Create a Local NuGet Source: Place your “.nupkg” file in a folder, e.g., “C:\NuGetPackages”. Configure the Local Source in NuGet: Open a terminal […]
