Excel 365 32 bit version error

44 views
Skip to first unread message

Rich Russell

unread,
Jul 10, 2025, 4:42:49 PMJul 10
to Excel-DNA
I receive the following error message when the my addin is attached 

Initialization [Error] External library could not be registered - Path: packed:XLSYS_MAIN : BadImageFormatException - Could not load file or assembly 'XLSys_Main, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'. This assembly was compiled for a different processor.


Govert van Drimmelen

unread,
Jul 10, 2025, 5:10:49 PMJul 10
to exce...@googlegroups.com

Hi Rich,

 

You should be sure to compile your main add-in assembly for “Any CPU”.

You might have some other settings in your project.

 

-Govert

--
You received this message because you are subscribed to the Google Groups "Excel-DNA" group.
To unsubscribe from this group and stop receiving emails from it, send an email to exceldna+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/exceldna/b14dbd88-2901-4a6c-b976-b68f4ce87c8bn%40googlegroups.com.

Leigh Tilley

unread,
Jul 10, 2025, 5:29:12 PMJul 10
to exce...@googlegroups.com
Hi 

Where I'm working we're doing the O365 migration and for my ExcelDNA as used the 64bit version.

Thanks 

Mr Leigh Tilley 

Govert van Drimmelen

unread,
Jul 10, 2025, 5:31:31 PMJul 10
to exce...@googlegroups.com

Your Excel-DNA can run on 64-bit office (the build normally outputs two version, for 32-bit and 64-bit automatically).

But your main add-in assembly should still be built as a pure managed assembly (targeting ‘Any CPU’).

 

-Govert

Rich Russell

unread,
Jul 11, 2025, 7:01:42 AMJul 11
to Excel-DNA
It was built for 'any cpu'. The 64 bit version works but the 32 bit version generates the error.  I am confident the 32 bit version was loaded on a 32 bit unit.  Any ideas?
Reply all
Reply to author
Forward
0 new messages