Hi,
I have an addin that is composed of a vsto (for front end) and an xll created using ExcelDna for pulling data from api's and such. Both projects have the ExcelDna.Integration package installed on them. They are running 1.1.0 currently. I was trying to upgrade to the newest version, 1.5.1, when I kept running into an error saying that my xll was not able to find the assembly for ExcelDna.Integration 1.1.0. I did a quick google and found that having the option "Register for com" would prevent my xll from building. Is there a way around this? I am currently using ExcelDna and the "Register for com" option at the same time and everything works in ver 1.1.0, what changed in ver 1.5.1? I am trying to generate the .tlb file to use in Excel's vba editor. if there is another, better, way to generate that file, that knowledge would be much appreciated. while googling today, I did find another way to generate a .tlb file using a command prompt (sadly this method will not happen every time you compile like the "Register for com" selection will) however, I was not able to generate the file needed due to another assembly error with ExcelDna.Integration.
Another potentially unrelated question.. I was having trouble with CsvHelper and Microsoft.Bcl.AsyncInterfaces. CsvHelper (nuget package) has a dependency for Microsoft.Bcl.AsyncInterfaces ver >=1.0.0. I have ver 6.0.0 installed everywhere. I have been getting all kinds of assembly errors for Microsoft.Bcl.AsyncInterfaces.dll. I was able to look at some fusion logs and it seems to be that CsvHelper is the calling assembly and is looking for ver 1.0.0. I have app.config files in my addins with binding redirects to version 6.0.0 and even have manual ones in my vb code. Nothing is seeming to fix this issue. Are there anymore places I can place binding redirects that excel might be able to pick up and use for an error similar to this? any suggestions on what I should do?