✨ New Features HttpCurl A new Chilkat class has been added: HttpCurl The Chilkat.HttpCurl class executes curl commands and can automatically resolve dependent values needed by a request. Variables such as {{access_token}}, {{site_id}}, or {{drive_id}} may appear in URLs, headers, query parameters, or request bodies. If a variable is not yet known, HttpCurl builds […]
✨ New Features Js A new Chilkat class has been added: Js is a minimal, standards-compliant JavaScript engine designed to embed JavaScript inside applications with very small footprint and fast startup. It executes JavaScript code inside an application without requiring a browser or large runtime. See About the Chilkat.Js JavaScript Engine Ai Provider — […]
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 GitHub C# Project to Check ActiveX Registration and Which VC++ Redistributables are Installed has been updated. Note: It should contain a pre-compiled executable located in bin\x86\Release (for non .NET programmers).
The Chilkat C/C++ library downloads marked as “XP” for VC++ 2012 and 2013 are compiled using the “XP” platform toolset. In Visual Studio, the toolset is chosen as shown here:
Regarding the following VC++ link problem: “fatal error C1047: The object or library file ‘c:\Chilkat\libs\x64\ChilkatRel_x64.lib’ was created with an older compiler than other objects; rebuild old objects and libraries” This can be resolved by building without the /LTCG flag turned on. Unfortunately, it is not possible to use the /LTCG flag if you are using […]
In VC++ 7.0, 8.0, 9.0, and 10.0, make sure the C++ Language option ‘Treat WChar_t as Built In Type’ is set to Yes. Otherwise, you may get this link error: error LNK2019: unresolved external symbol “public: void __cdecl CkString::appendU(unsigned short const *)
The Chilkat VC++ static libraries are for unmanaged C++ applications. A Managed C++ application (using Microsoft’s Managed Extensions for C++) runs within the .NET Framework and therefore must use the Chilkat .NET assembly. The Chilkat C++ online reference documentation and online examples are for unmanaged C++ applications. For Managed C++, the best choice is to […]
When a C++ compiler compiles a C++ source file, it must process the bytes according to a character encoding and that is typically ANSI. ANSI is not a character encoding, it is simply a keyword that says “Use the default multi-byte character encoding for this computer based on its current locale.” Therefore, if your program […]
All Chilkat C++ classes have a Utf8 property. For example: class CkEmail : public CkObject { public: CkEmail(); virtual ~CkEmail(); … bool get_Utf8(void) const; void put_Utf8(bool b); … const char *addFileAttachment(const char *fileName); … }; The Utf8 property controls how the bytes pointed by “const char *” arguments are interpreted. By default, “const char *” […]
