D
Dan
Hi all, I'm new to Office 2003 addins and VS.NET tools for it. I have Visual
Studio .NET 2003, Visual Studio office tools, Office 2003 Pro, and I'd want
to develop some Word 2003 addins. I'd like to ask a couple of beginner
questions:
1) I'd like to develop a C# DLL which exposes some functions which can be
called from Word VBA. In old C++ days I did it creating a COM DLL and adding
a reference to it from the VBA project; now I'd want to use C#. In .NET how
this is supposed to be done?
2) I'd like to trigger the call to some of these DLL functions in Word
itself when pressing a specified keyboard shortcut: in previous versions of
Office I think this could not be done, so that I resorted using a DOT VBA
template with predefined keyboard bindings which called the DLL functions.
This means I had to sacrifice the ad-hoc addin architecture, which could add
toolbars but could not be bound to specified keyboard shortcuts
programmatically.
With reference to these questions, how does the new .NET addin architecture
fit in the whole picture (which project to use, which limitations to
consider, etc...)?
Thanks to all!
Studio .NET 2003, Visual Studio office tools, Office 2003 Pro, and I'd want
to develop some Word 2003 addins. I'd like to ask a couple of beginner
questions:
1) I'd like to develop a C# DLL which exposes some functions which can be
called from Word VBA. In old C++ days I did it creating a COM DLL and adding
a reference to it from the VBA project; now I'd want to use C#. In .NET how
this is supposed to be done?
2) I'd like to trigger the call to some of these DLL functions in Word
itself when pressing a specified keyboard shortcut: in previous versions of
Office I think this could not be done, so that I resorted using a DOT VBA
template with predefined keyboard bindings which called the DLL functions.
This means I had to sacrifice the ad-hoc addin architecture, which could add
toolbars but could not be bound to specified keyboard shortcuts
programmatically.
With reference to these questions, how does the new .NET addin architecture
fit in the whole picture (which project to use, which limitations to
consider, etc...)?
Thanks to all!