using ExcelDna.Integration;
using ExcelDna.Integration.CustomUI;
using ExcelDna.IntelliSense;
And added comments to the function:
But it does not work in Excel:
Anybody knows an answer to this problem:
[ExcelFunction(Description = "Joins a string to a number", Category = "ExcelDnaFunctions")]
public static string JoinThemExcelDNA([ExcelArgument("string for name")]string str, [ExcelArgument("double for number")] double val)
{
return str + val;
}
using ExcelDna.Integration; using ExcelDna.IntelliSense; public class AddIn : IExcelAddIn { public void AutoOpen() { IntelliSenseServer.Register(); } public void AutoClose() { } }
Easiest is to just download the pre-compiled IntelliSense add-in from here:
https://github.com/Excel-DNA/IntelliSense/releases
Pick either ExcelDna.IntelliSense.xll or ExcelDna.IntelliSense64.xll depending on your Excel version, and File->Open to load it.
Everything should then work without any changes to your add-in.
If that doesn’t work, you can contact me directly to arrange for a support session too.
-Govert
--
Application.RegisterXLL("<YOUR PATH>\ExcelDna.IntelliSense64.xll")Managed Debugging Assistant 'LoaderLock' : 'Attempting managed execution inside OS Loader lock. Do not attempt to run managed code inside a DllMain or image initialization function since doing so can cause the application to hang.'
The Visual Studio warning about the “LoaderLock” is expected, and you can just disable that in Visual Studio when debugging your add-in (the dialog that pops up should have a checkbox that enables you to do this).
The IntelliSense uses a dangerous mechanism to detect that add-ins are loaded and unloaded, but tried to be careful when implementing it and have not heard of any trouble from this.
-Govert
From: exce...@googlegroups.com <exce...@googlegroups.com> On Behalf Of Nasrul Arif
Sent: 25 April 2019 04:31
To: Excel-DNA <exce...@googlegroups.com>
Subject: Re: [ExcelDna] ExcelDNA Intellisense not working
But unfortunately I faced some issue with it. After few minutes of running the Add-In in debug mode, this happens in my Visual Studio.
--