✨ 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. […]
“Could not load file or assembly ‘ChilkatDotNet2, Version=9.3.0.0, Culture=neutral, PublicKeyToken=eb5fc1fc52ef09bd’ or one of its dependencies. An attempt was made to load a program with an incorrect format.” The “incorrect format” error is a 32-bit vs. 64-bit mismatch. It means the application is trying to load a 64-bit .NET assembly into a 32-bit process, or the […]
A 64-bit Windows system has two separate registries — one for 32-bit processes, and one for 64-bit processes. The reason for this is simple: Let’s say your application instantiates an instance of an ActiveX component by calling CreateObject(“Chilkat.Ssh”). If your application is running in a 32-bit address space, the registry entries for “Chilkat.Ssh” should point […]
64-bit Windows is capable of running applications in both 32-bit mode and 64-bit mode. If the application process is running in a 32-bit address space, the DLL must also use a 32-bit address space. (In other words, it should be a DLL compiled for the Win32 platform.) If the application process is running in a […]
This Chilkat blog post explains the following error: “Could not load file or assembly ‘ChilkatDotNet2, Version=9.0.8.0, Culture=neutral, PublicKeyToken=eb5fc1fc52ef09bd’ or one of its dependencies. An attempt was made to load a program with an incorrect format.” When a DLL is loaded, it is mapped into the process’s address space. If the process is running in a […]
Question: Help clarify something for me please. I develop in a 32bit environment, but deploy to windows 2003/2008 64bit servers. Do I install the 64bit or the 32bit ActiveX on the servers? Answer: In Visual Studio C/C++ applications, you may target either win32 or x64. If your application targets win32, you should register (using regsvr32) […]
I recently discovered this crucial bit of information: I compile my project for x86 systems (vs Any CPU or x64). Just wanted you to be aware of this. Your last email stated “You must deploy the x64 ChilkatDotNet2.dll to x64 systems” which is not correct. This is an important consideration for “Click Once” deployments which […]
For the most part, a 32-bit Chilkat ActiveX DLL will run on a 64-bit computer. However, there is an issue (to be explained here) that requires the ActiveX to be built specifically for x64. Chilkat provides separate 64-bit ActiveX’s on it’s downloads web page, and these should be used on x64 systems. The problem occurs […]
Here’s the secret to getting the .NET runtime to load the ChilkatDotNet2.dll from a Windows Service: It must be installed in the GAC, but there’s a separate GAC for 64-bit assemblies: (with permission from the Chilkat customer) I was able to find a solution to this. I’m running a 64-bit version of Vista, and there […]
Question: I get an error when trying to load ChilkatDotNet2.dll on Vista x64: An attempt was made to load a program with an incorrect format. Does Chilkat have an x64-compatible .NET assembly? Answer: Yes, download the x64-compatible DLL from this URL: x64 compatible ChilkatDotNet2.dll Make sure you deploy the x64 DLL to the 64-bit Vista […]
