References break in ExcelDna.Registration when using ExcelDna.Integration v1.1.0-beta1
See original GitHub issueMy application requires a signed version of ExcelDNA.Integration so I tried upgrading to the v1.1.0-beta1 release on Nuget.
As soon as I did that I started getting errors. I am using the registration library to manually register functions;
registrations.Where(X => X.FunctionAttribute.Name == “XXXXXXXXX”).RegisterFunctions();
Every reference to ‘FunctionAttribute’ now shows the following error;
Severity Code Description Project File Line Suppression State Error CS0012 The type 'ExcelFunctionAttribute' is defined in an assembly that is not referenced. You must add a reference to assembly 'ExcelDna.Integration, Version=1.0.7056.37028, Culture=neutral, PublicKeyToken=null'. XXXXX.DataConnect.AddIn C:\Users\XXXXX\source\repos\XXXXX-DataConnect\XXXXX.DataConnect.AddIn\Functions.cs 20 Active
I am currently using;
ExcelDna.Registration v1.0.0.0 ExcelDna.IntelliSense v1.2.0.0 ExcelDna.Integration v1.1.0.0
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (4 by maintainers)
Top GitHub Comments
@augustoproiete I have loaded the new assemblies from Nuget and so far everything looks good. I will update if I see any issues.
I wanted to say thanks for you pushing this out so fast. My butt was kind of on the line since the assembly signing issue was blocking a deploy and my director had a lot of focus on this project.
I know you rarely get any insight into how this is used but your fix is allowing me to deploy an Excel Addin that is used to monitor renewables power generation across North America. We expect the Addin to be deployed to roughly 4000 systems company-wide over the next few weeks.
This is good work and we appreciate it.
Pre-release NuGet packages referencing
ExcelDna.Integration
v1.1.0-beta1 with assemblies strong-named (1) published to nuget.org:(1)
ExcelDna.Registration.FSharp
was not strong-name signed due to a bug in the FSharp compiler. See PR Excel-DNA/Registration#29 for details.