http://mschnlnine.vo.llnwd.net/d1/Dev/App_Themes/C9/images/feedimage.pnghttp://channel9.msdn.com/posts/DanielMoth/VBA-interop-with-VSTO-managed-code-in-VS-2008/VBA interop with VSTO managed code in VS 2008http://channel9.msdn.com/posts/DanielMoth/VBA-interop-with-VSTO-managed-code-in-VS-2008/en-usThu, 29 May 2008 19:08:34 GMTThu, 29 May 2008 19:08:34 GMTEvNet (EvNet, Version=1.0.3608.3122, Culture=neutral, PublicKeyToken=null)Hi cotasson<BR><BR>Glad you found a solution soon after posting the question. For future&nbsp;VSTO questions the best place is this forum:<BR><a href="http://forums.microsoft.com/msdn/showforum.aspx?forumid=16&amp;siteid=1">http://forums.microsoft.com/msdn/showforum.aspx?forumid=16&amp;siteid=1</a><BR><BR>Cheers<BR>Danielhttp://channel9.msdn.com/posts/DanielMoth/VBA-interop-with-VSTO-managed-code-in-VS-2008/?CommentID=406491Thu, 29 May 2008 19:08:34 GMThttp://channel9.msdn.com/posts/DanielMoth/VBA-interop-with-VSTO-managed-code-in-VS-2008/?CommentID=4064910http://channel9.msdn.com/406491/WebViewBug.aspx?EVT=0Hi cotassonGlad you found a solution soon after posting the question. For future&nbsp;VSTO questions the best place is this forum:http://forums.microsoft.com/msdn/showforum.aspx?forumid=16&amp;siteid=1CheersDanielDaniel Moth0http://channel9.msdn.com/406491/Trackback.aspxHello again, <br><br>I found <a href="http://msdn.microsoft.com/en-us/library/bb931201.aspx#VSTO2005SEVBAInterop_ExampleIntegratingVBAandVSTO">this article</a>: <br>As a matter of fact, I was coding in C#, this might be the reason why. <br><br>Cheers. <br>http://channel9.msdn.com/posts/DanielMoth/VBA-interop-with-VSTO-managed-code-in-VS-2008/?CommentID=406425Thu, 29 May 2008 16:33:00 GMThttp://channel9.msdn.com/posts/DanielMoth/VBA-interop-with-VSTO-managed-code-in-VS-2008/?CommentID=4064250http://channel9.msdn.com/406425/WebViewBug.aspx?EVT=0Hello again, I found this article: As a matter of fact, I was coding in C#, this might be the reason why. Cheers. cotasson0http://channel9.msdn.com/406425/Trackback.aspxHello Dan, <br><br>I am currently working on VSTO. <br>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. <br><br>Your screencast does just what I need to implement. <br><br>I try to implement the second part of the screencast, to no avail. <br><br>The properties pane for the "workbook", under the VBA Interop category does not show the "VBACallsEnabled" option. However the second one, <br>"ReferenceAssemblyFromVBAproject" is featured. <br><br>I set it to "true", run the project, but the DLLs are not referenced, nor the VBA code referencing the .Net created...<br><br>Any ideas, tips, would help. <br><br>I have VS Studio 2008 Pro Edition, running on XP Pro. <br><br>Thanks. <br><br>PS : All that aside, I found your videos on VSTO quite instructive, far more than other VSTO videos I found elsewhere....<br>Congrats !<br>http://channel9.msdn.com/posts/DanielMoth/VBA-interop-with-VSTO-managed-code-in-VS-2008/?CommentID=406390Thu, 29 May 2008 15:25:12 GMThttp://channel9.msdn.com/posts/DanielMoth/VBA-interop-with-VSTO-managed-code-in-VS-2008/?CommentID=4063900http://channel9.msdn.com/406390/WebViewBug.aspx?EVT=0Hello Dan, 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&#8230;cotasson0http://channel9.msdn.com/406390/Trackback.aspx