P
Peter Bennett
Hi
I'm looking to upgrade my firm's VBA code to fully managed .NET. Currently, the code is actioned through customised buttons in a global template, and this scheme is the way I'd like to keep things
Unfortunately, from what I read, there's a bit of a Catch-22 situation here (please correct me if I'm wrong!)
1) VSTO code can only be triggered by opening or creating documents
2) VSTO can respond to button events, but only if VTSO put buttons there in the first place
In a nutshell, is there any support at all for VSTO/.NET code to be statically accessible within Word 2003 or am I stuck with having to use a COM interface into .NET, which would seem to bypass VSTO altogether
Thanks
Pete
I'm looking to upgrade my firm's VBA code to fully managed .NET. Currently, the code is actioned through customised buttons in a global template, and this scheme is the way I'd like to keep things
Unfortunately, from what I read, there's a bit of a Catch-22 situation here (please correct me if I'm wrong!)
1) VSTO code can only be triggered by opening or creating documents
2) VSTO can respond to button events, but only if VTSO put buttons there in the first place
In a nutshell, is there any support at all for VSTO/.NET code to be statically accessible within Word 2003 or am I stuck with having to use a COM interface into .NET, which would seem to bypass VSTO altogether
Thanks
Pete