Issue with ExcelDna.Integration.dll Version 1.8.0 Referencing Assembly Version 1.1.0.0

68 views
Skip to first unread message

Rugs Excel

unread,
May 14, 2025, 12:00:04 PM5/14/25
to Excel-DNA

Hi everyone,

I'm encountering a versioning issue with the ExcelDna.Integration DLL after installing the ExcelDna.AddIn NuGet package (v1.8.0).

Project Setup:

  • Target Framework: .NET Framework 4.8

  • NuGet Package: ExcelDna.AddIn v1.8.0

  • ExcelDna.Integration.dll Path: packages\ExcelDna.Integration.1.8.0\lib\net452\ExcelDna.Integration.dll

Problem:

Although I’m using version 1.8.0 of the package, the referenced ExcelDna.Integration.dll has an internal AssemblyVersion of 1.1.0.0 (confirmed in the file properties and through ILSpy).

As a result, the compiler throws an error when I try to use:

ExcelAsyncUtil.QueueAsMacroAsync(...)

It appears the method doesn’t exist in the referenced version (or is inaccessible).

My Questions:

  1. Is this version mismatch expected?

  2. Is there a different reference or binding redirect I should use?

  3. What’s the recommended way to get access to the latest ExcelAsyncUtil APIs in this setup?

Any clarification or guidance would be much appreciated. Thank you!



Govert van Drimmelen

unread,
May 15, 2025, 8:47:26 AM5/15/25
to Excel-DNA
The AssemblyVersion that you see as 1.1.0.0 is correct (at least it's 'by design') and has to do with assembly signing where changing the assembly version is somehow bad, so that number does not update for new versions. The ExcelDna.Integration.dll file you are picking up looks right.

I don't think the problem you see is related.

I'm also not sure whether ExcelAsyncUtil.QueueAsMacroAsync(...) was ever part of Excel-DNA.
I can't say where this type was coming into your project before, maybe you were using some other helper library or code?

The only reference I find to a method called QueueAsMacroAsync is here, with an implementation that looks fine to me:

This sample may also give you some ideas for doing Task-based async / await work in macro context, though it's not exactly the same pattern.
Reply all
Reply to author
Forward
0 new messages