VBA interop with VSTO managed code in VS 2008
- Posted: Oct 21, 2007 at 5:29 PM
- 9,494 Views
- 3 Comments
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
Right click “Save as…”
Author: Hi, I am Daniel Moth ![]()
Introduction: With VSTO v3.0 the attraction to write managed code in order to customise Office applications is huge. However, if you already have investments in VBA code, you do not need to throw it out just yet. Just interop, like I show in
this 8' video. For other resources, start at my
blog post here.
Video download: Click on the image to play the video (from a streaming file). If you'd prefer to download the wmv packaged in a zip file, you may do so
here.
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
Follow the Discussion
Oops, something didn't work.
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.sign up for email notifications?
I am currently working on VSTO.
As far as I know, it is not possible to write Excel UDFs directly in .Net, you have to rely somehow on VBA as a gateway to do this.
Your screencast does just what I need to implement.
I try to implement the second part of the screencast, to no avail.
The properties pane for the "workbook", under the VBA Interop category does not show the "VBACallsEnabled" option. However the second one,
"ReferenceAssemblyFromVBAproject" is featured.
I set it to "true", run the project, but the DLLs are not referenced, nor the VBA code referencing the .Net created...
Any ideas, tips, would help.
I have VS Studio 2008 Pro Edition, running on XP Pro.
Thanks.
PS : All that aside, I found your videos on VSTO quite instructive, far more than other VSTO videos I found elsewhere....
Congrats !
I found this article:
As a matter of fact, I was coding in C#, this might be the reason why.
Cheers.
Glad you found a solution soon after posting the question. For future VSTO questions the best place is this forum:
http://forums.microsoft.com/msdn/showforum.aspx?forumid=16&siteid=1
Cheers
Daniel
Remove this comment
Remove this thread
close