J
Jack Hoxley [MVP]
Morning all,
Just a quick post to request some best-practice advice as to what my options
might be. I've been digging around MSDN for a while and haven't found any
promising leads yet.
In a nutshell I want some VBA (or C#) code for Excel 2003 where I can store
help text that appears in the function helper window - e.g. function
description, category and parameter name/description.
I found the following two articles
http://www.dailydoseofexcel.com/archives/2006/02/17/registering-a-user-defined-function-with-excel/
http://www.bettersolutions.com/excel/EIK284/YN723710331.htm
But they cause strange errors whereby our UDF's aren't always called. I did
some digging, and found http://msdn.microsoft.com/en-us/library/bb687900.aspx
which left me confused as to how the aforementioned code is ever supposed to
work. It strikes me that the oft repeated fragments online are nothing but
fugly hacks. Who's smart idea was it to try and pull out User32.dll calls and
re-alias them as other VBA functions?! A true "WTF".
Does anyone know of any other approaches to exposing intellisense-style
information to the end-users of our Excel Addin? Can VSTO somehow do it
directly from within the .NET/C# code maybe?
Any suggestions or advice are appreciated,
Jack
Just a quick post to request some best-practice advice as to what my options
might be. I've been digging around MSDN for a while and haven't found any
promising leads yet.
In a nutshell I want some VBA (or C#) code for Excel 2003 where I can store
help text that appears in the function helper window - e.g. function
description, category and parameter name/description.
I found the following two articles
http://www.dailydoseofexcel.com/archives/2006/02/17/registering-a-user-defined-function-with-excel/
http://www.bettersolutions.com/excel/EIK284/YN723710331.htm
But they cause strange errors whereby our UDF's aren't always called. I did
some digging, and found http://msdn.microsoft.com/en-us/library/bb687900.aspx
which left me confused as to how the aforementioned code is ever supposed to
work. It strikes me that the oft repeated fragments online are nothing but
fugly hacks. Who's smart idea was it to try and pull out User32.dll calls and
re-alias them as other VBA functions?! A true "WTF".
Does anyone know of any other approaches to exposing intellisense-style
information to the end-users of our Excel Addin? Can VSTO somehow do it
directly from within the .NET/C# code maybe?
Any suggestions or advice are appreciated,
Jack