xll

问题 We are using XLDNA to make a small VB.net XLL that loads our data files and places the contents in Excel for editing. When we tried to deploy this among our three-person team, it was like an episode of the Three Stooges - it would work fine on one machine but then tell us that it was not a valid XLL on another, causing much head-smacking. We realized with was 32/64 related, but also found that the machines in question randomly had the 32 or 64 version of Excel even though they are all the

问题 We are using XLDNA to make a small VB.net XLL that loads our data files and places the contents in Excel for editing. When we tried to deploy this among our three-person team, it was like an episode of the Three Stooges - it would work fine on one machine but then tell us that it was not a valid XLL on another, causing much head-smacking. We realized with was 32/64 related, but also found that the machines in question randomly had the 32 or 64 version of Excel even though they are all the

问题 Is it possible to view the source code of the XLL Excel add in without having the original source code? I'm guessing that this XLL was written in C#, but not sure. I.e. a .NET DLL you can decompile with dotPeek, or an XLA file you can open in Excel via Developer > Visual Basic. I tried both approaches with no luck. 回答1: Do you know if this Excel Add-In was built using Excel-DNA? If it was, then you can extract the .NET assemblies from the .XLL file using ExcelDnaUnpack. Source code is on

问题 I have a piece of C++ code, which creates a XLL (Excel add-in). It can be successfully loaded by Excel, and works perfectly. Then, I switched to 64-bit Excel, and the code stopped working. So I have recompiled the code in Visual Studio using x64 platform settings. The compilation went error free. Now when I try to load it in 64-bit Excel, Excel does not recognize the file extension: It complains showing "The file format and extension of 'MyAddin.xll' don't match.", and gives me the follwoing

问题 I have a particular function in an Excel addin(xll). The addin is proprietary and we do not have access to the source code. However we need to call some functions contained within the addin and we would like to call it from a C# program. Currently, I was thinking of writing a C++ interface calling the Excel function with xlopers, then calling this C++ interface from C#. Does anybody who has prior experience of this kind of issues know what would be the best solution for that ? Anthony 回答1:

问题 I have a particular function in an Excel addin(xll). The addin is proprietary and we do not have access to the source code. However we need to call some functions contained within the addin and we would like to call it from a C# program. Currently, I was thinking of writing a C++ interface calling the Excel function with xlopers, then calling this C++ interface from C#. Does anybody who has prior experience of this kind of issues know what would be the best solution for that ? Anthony 回答1:

问题 I have a xll file which have a function and I want to call that function from C#. This xll file is used in excel.any body have idea how to do that?.I tried refrencing the xll file but I am not getting the value.If I open excel like start-->programms-->excel and in excel if i directly give the function I am getting right value.Same thing If i automate excel in c# and opened excel from Microsoft.Office.Interop.Excel and applied the function I am getting error 回答1: You probably won't be able to

问题 i create a debug version of an excel addin lets call it myaddin.xll. when i open an instance of excel and add myaddin.xll to it i get the expected result. but when i hit debug from within visual studio environment the myaddin.xll tries to open and gives a "this program cannot be in dos mode" error. for other excel addin i have developed i do not have this problem. this problem is suddenly occuring for this particular addin. "dos mode..." error usually happens when something is missing.

问题 I've got a XLL Addin and I'm trying to run it under Excel 2007 XP without VBA installed. My addin is well registered (OPEN key as /R "C:\Program Files (x86)\MyAddin\myAddin.xll" in HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Excel\Options). When debuging, I see that DLLMain is called... but not xlAutoOpen (neither others xlSomethings functions): my UDFs are thus not registered (it was done in xlAutoOpen). Do I miss something ? Do I absolutly need VBA installed ? If yes, is there another

问题 I have no idea how to handle XLOPER type variable in VBA. There are plenty of web pages explaining the relationship between Xloper variable , c++ DLL and XLL add-in, however i need to write c++ function in a dll returning a xloper directly to VBA without XLL framework. (No need of User Defined Function since functions from the dll will be called by the VBA code - not by Excel users). Indeed i'm coding a Excel VSTO and i need to call c++ code from it. I found that xloper variable are very