login about faq

Hi Matt,

The NuGet package for chilkat-x64 version contains an incorrect version ( of the class library for the 4.6 Framework (and 4.6.1).

It might simply be incorrect file information, since I haven't tried to query the version from any of the internal methods. However the same NuGet package contains the correct version for the other versions of .NET Framework. Hence my guess is that the class library for 4.6 was not updated.

asked Sep 23 '16 at 03:47

roan98dk's gravatar image


It's actually It's only the resource on the DLL itself that didn't get updated.

The actual assembly is v9.5.0.59. There are three places where version information exists in the .NET assembly:

  1. The resource. This is the ".rc" file that is in the Visual Studio project (for the Chilkat assembly) when it's built. This is what you see when you right-click on the DLL in Windows Explorer folder, select Properties, and then examine then select the "Details" tab. This is what didn't get updated.
  2. The Version property in the Chilkat API. This will be the correct version. It's a version embedded within the internal source of Chilkat, in a single place, and is the same for all builds across all operating systems, programming languages, etc. It's what you see in the LastErrorText. Whatever it reports is truly the version. If another "version" disagrees, then the Version property in the API is always to be believed.
  3. There's the version embedded in the AssemblyInfo.cpp internal source that's part of a .NET assembly build. Internally, it looks like this: "[assembly:AssemblyVersionAttribute("")];"

answered Sep 23 '16 at 08:10

chilkat's gravatar image

chilkat ♦♦

I thought that might be the case. I could easily have tested this myself, but in case others had the same experience, it is better to have this information here.

(Sep 26 '16 at 17:08) roan98dk

Thanks! I did find out the reason it did not get updated. When Chilkat updates to the next new version, there is an automated procedure to edit all files that contain the version number in some way. This is for all possible builds across all programming languages, and therefore could involve project files, resource files, source files, etc. There is a master list of files where version numbers exist, and the Chilkat .NET 4.6 resource file was correctly in the list. HOWEVER -- the resource file happens to be stored using utf-16, and the search/replace was using utf-8, and therefore it was missed.. Now it is corrected, and future version changes won't get missed. Also, v9.5.0.60 is a patch that was just released, and this should have the version correct..


answered Sep 26 '16 at 17:18

chilkat's gravatar image

chilkat ♦♦

edited Sep 26 '16 at 17:18

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: Sep 23 '16 at 03:47

Seen: 2,406 times

Last updated: Sep 26 '16 at 17:18

powered by OSQA