Govert van Drimmelen

@raymondjstone You're right - Active Setup seems to be the standard way of ensuring per-user installs can be done for all users. With Excel-DNA I've tried to also make it...

Here is a new report post-v1.1.0 for a related issue: https://groups.google.com/g/exceldna/c/TSOPygt334Y Not sure if the App-V is a sufficiently different environment, or whether this affects only elevated contexts. But the...

@rosssaunders I can't remember all the details, but I think that the registry write is to HKLM\...\ClickToRun\REGISTRY\USER is normal, and we expect the user to have permissions to write to...

Thank you very much for the update. I have in mind looking at two improvements, though can’t promise anything yet: * Add a setting in Excel-DNA to either ignore the...

@Chadders187 Thank you - I think this is a useful suggestion.

@altso That's amazing! I didn't know about `XmlPeek` / `XmlPoke` before. I had some trouble running it as is, because the default .dna files now have a namespace included, and...

Getting the calling cell from an Excel-DNA UDF with the COM call to `Application.Caller` is problematic. Instead, you can use the C API call `XlCall.Excel(XlCall.xlfCaller)`. This gives you an `ExcelReference`...

Are you using the `ExcelDna.Registration` library to hook up the async function? If so, it might be that the `ExcelArgument(AllowReference = true)` arguments are hooked up in a way that...

@pearsonfive Thank you very much for signing up as a GitHub Sponsor for Excel-DNA! I haven't had a look at this yet. The first step will be to look at...

@pearsonfive I might need a bit more context to what you are seeing. When I run the code from the initial post it seems to work OK and I can't...