Re: Double interface VSTO and VBA

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

One approach, probably the easiest, is as follows:

url:http://blogs.msdn.com/pstubbs/archive/2004/12/31/344964.aspx

Other ideas here:

url:http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=459282&SiteID=1

Bill Coan
billcoan@xxxxxxxxxxxx
<sylvaingross@xxxxxxxxxxx> wrote in message
news:1165832212.551131.275050@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi,

I need some help...
I develop a VSTO app for Excel 2003, with VS2003+VSTO, written in C#.
My pb is:
* my business code is written in .NET
* user interface is an excel doc
* my client wants to call my .NET functions from VBA macros (button
clic management,..., misc macros ...).
* A shared object, between VBA and .NET should exist, because action
requested by VBA should be executed by .NET. It smells like a singleton
pattern, but between different platforms...

What should be the best solution, to expose my .NET app to VBA ?
I thought that the best would be to use COM interop: write my component
for COM, and reference it in VBA project)
But the pb is that when I instanciate my class, the created object is
not shared with the instance created in .NET, even if I use statics
I hope that I clearly exposed my pb, and that sonmeone can help me !
Thank you !



.

Quantcast