Chilkat for .NET — Downloads & Installation
One place to get Chilkat for both .NET Core / modern .NET (.NET 6, 7, 8, 9… on Windows, Linux, and macOS) and the classic .NET Framework (2.0–4.8 on Windows). All components are fully functional for a 30-day evaluation.
Jump to: .NET Core / Modern .NET .NET Framework Install Instructions Common Errors Docs & Examples
Which package do I need?
.NET Core / Modern .NET
Choose this if your project targets .NET 6.0 or higher (also .NET 7/8/9) or .NET Core 3.1, and especially if you deploy to Linux or macOS.
- Cross-platform: Windows, Linux, macOS
- Delivered via NuGet — no manual DLL reference
- Single package works for x64 & ARM64
.NET Framework
Choose this if your project targets the classic .NET Framework (2.0, 3.5, 4.0, 4.5, 4.6, 4.7, or 4.8) on Windows.
- Windows only
- Available via NuGet or direct ZIP download
- Pick the bitness (x64 / win32) that matches your process
Chilkat for .NET Core / Modern .NET
For Windows, Linux, and macOS. Distributed as NuGet packages.
.NET 6.0 and higher
NuGet package: ChilkatDnCore (.NET 6.0 and higher). This is the right choice for .NET 6, 7, 8, and 9 projects.
.NET Core 3.1
NuGet package: ChilkatDnCore31 (.NET Core 3.1).
dotnet add package ChilkatDnCoreThere is no manual DLL reference and no separate x86/x64 choice — NuGet restores the correct native binaries for your target platform automatically.
Browse all packages: see every Chilkat package (Core and Framework) on the Chilkat NuGet profile.
Chilkat for .NET Framework
For Windows, targeting the classic .NET Framework (2.0 – 4.8). All Chilkat .NET classes are contained in a single assembly (DLL).
Option A — Install via NuGet (recommended)
The fastest way to get started: the .NET Framework assemblies are published on NuGet, so Visual Studio downloads and references the correct DLL for you — no manual unzipping or DLL hunting. Browse them on the Chilkat NuGet profile.
Pick the package that matches your build's bitness:
chilkat-x64
Use for x64, or for “Any CPU” with
“Prefer 32-bit” unchecked.
chilkat-win32
Use for x86, or for “Any CPU” with
“Prefer 32-bit” checked.
Picked the wrong one? An “incorrect format” error simply means the package bitness doesn't match your process — switch packages, or see Common Error #1.
Option B — Direct ZIP download
The downloads below are the full versions. Pick the row matching your .NET Framework version and process bitness (x64 or win32). There is no installer — just unzip and reference the DLL (see Install Instructions).
Install Instructions (.NET Framework direct download)
There is no installer — just unzip, reference the DLL, and start coding. Follow the three steps below.
-
Unzip the download
Extract the ZIP to any directory you like. The Chilkat .NET assembly is a single DLL (for example,
ChilkatDotNet48.dll). -
Add a reference in Visual Studio
In your project, add a reference to the Chilkat DLL: right-click References → Add Reference → Browse, then locate and select the DLL.
-
Use it in your code
Add the namespace and you're ready to go:
using Chilkat;
Deploying your application
When you build, Visual Studio copies the Chilkat DLL into your output
bin folder automatically (“Copy Local” is on by default).
On the target machine, make sure the matching VC++ runtime is installed and
the bitness matches the Chilkat build you referenced.
Unlocking Chilkat
Chilkat runs as a fully functional 30-day trial right out of the box —
no license code needed to evaluate. After purchase, unlock Chilkat by calling
Global.UnlockBundle once with your license code at the start of
your program, each time it runs.
Common Errors (.NET Framework)
Nearly every first-time issue is one of these two — both stem from Chilkat being a native DLL. Here's how to recognize and fix each.
The bitness of the Chilkat DLL doesn't match your process: a 32-bit process must load the 32-bit DLL, and a 64-bit process must load the 64-bit DLL.
Could not load file or assembly 'ChilkatDotNet**' or one of its dependencies. An attempt was made to load a program with an incorrect format.
- Match the assembly to your process. Reference the x64 build for 64-bit processes and the win32 build for 32-bit.
- Force 32-bit (simplest). Set the build platform to x86, or tick “Prefer 32-bit” in Project Properties → Build (available in Visual Studio 2012 and later, for .exe projects targeting “Any CPU”). Your app then always runs as 32-bit, so always reference the 32-bit assembly.
- “Any CPU”. The app runs 64-bit on 64-bit Windows and 32-bit on 32-bit Windows (with “Prefer 32-bit” unchecked), so deploy the matching assembly to each. In practice 32-bit Windows is now rare — if every target machine is 64-bit, just use the x64 build with “Any CPU” and “Prefer 32-bit” unchecked.
- ASP.NET or Windows Service (bitness unclear)? Install both the 32-bit and 64-bit assemblies into their respective GACs — the .NET runtime loads the one that matches the process automatically.
The required Visual C++ runtime redistributable is not installed on the machine. (Despite the message, this is about a missing native dependency, not the Chilkat DLL itself.)
Could not load file or assembly 'ChilkatDotNet**.dll' or one of its dependencies. The specified module could not be found.
Install the VC++ runtime that matches your Chilkat build, from Microsoft’s VC++ Runtime Redist downloads. Be sure to install the same bitness (x64 and/or x86) as your process:
| Your Chilkat build | VC++ runtime to install |
|---|---|
| .NET 4.6 / 4.7 / 4.8 | Visual Studio 2015–2022 (one download covers all) |
| .NET 4.5 (VS2013) | Visual Studio 2013 — VC++ 12.0 |
| .NET 4.5 (VS2012) | Visual Studio 2012 — VC++ 11.0 |
| .NET 4.0 | Visual Studio 2010 SP1 — VC++ 10.0 |
| .NET 2.0 | VC++ 2005 runtime redist |
Reference Documentation & Sample Code
- Reference Documentation: Chilkat Documentation (C# reference)
- Sample Code: Chilkat Example Code (C# examples)