First, I have an Add-in that I developed through the VBE in Excel. Recently I found out about ExcelDNA and have updated the Add-In to reference a couple of functions from
VB.NET and placed them in a .xll file and packed the file. The file works fine when I double-click on the file and load it into Excel before running the VBE developed Add-In. But, if I want to distribute the Add-In along with the .xll what is the best way to write a script to register the .xll for the end user?
I have tried using the v2 and the v4 versions of RegAsm on the packed .xll and on the default (renamed) .xll and each time I receive an error that the ".xll is not a valid .NET assembly". I have tried it on several different systems - XP, Vista, and Win 7 64 and I get the same error...
If I develop a script using regsrv32 would that work to register the .xll for the end user?
I am trying to figure the easiest way so that the end user does not have to do any further installation...
Second, when trying to run the .xll I can sometimes receive a message that the file is unsigned. I have a signature on the VBE developed Add-In and have converted it to an EXE so that the macros do not need a signature, but is there a way to sign an .xll file? or to convert the .xll so that there are not macro warnings for the end user? The reason I ask is that several users have reported that they do not have admin right to install a new signature or change the default macro security settings and I am trying to identify a method for registering / installing / using the .xll without needing admin rights.
Finally, if neither of the above is possible, it it possible to call a .NET function directly from a VBA?
Thank you in advance for any help,
Bob