-
-
Notifications
You must be signed in to change notification settings - Fork 274
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
upgrading from 1.5.1 to 1.6.0 causes invalid XLL file #576
Comments
Is this the error you refer to - I also post about the solution there.
|
no it is not. i tried your suggestion though but same outcome. |
The XLL file is not an archive. It is a normal Windows .dll file.
Unless your project is called "ExcelDna" there will not be an embedded assembly just called "EXCELDNA". These embedded resources are sometimes compressed too (to make the .XLL file smaller). This compression was removed in some of the 1.6.x versions, leaving the assembly embedded without compression. In addition, we tried some obfuscation too, using a simple encoding on the embedded assemblies. In the end it seemed the encoding made things worse, and so we reverted back to compression only in the latest preview versions. You might try 1.7.0-rc1 as an indication of where we stand now. I don't expect any of these changes to cause an "invalid XLL file" or to give you an "ActiveX component can't create object" error. You might be mixing some observations about the implementation of the embedded resource packing, with other problems you are running into. |
i was upgrading a project from 1.5.1 to 1.6.0 but Excel gave me the (in)famous "ActiveX component can't create object" error. upon investigating i unzipped/extracted the EXCELDNA file from the XLL file.
in 1.5.1 that is also a zip compressed file (containing folder ".rsrc" and files ".reloc" and ".text"), but in 1.6.0 it is not a zip compressed file, but i don't what it is. opening the XLL in Excel will give an unsupported format error.
file attached; EXCELDNA (renamed to EXCELDNA.zip for upload policy reasons)
any idea(s)?
The text was updated successfully, but these errors were encountered: