tag:blogger.com,1999:blog-6497434045878013201.post4683028290389008867..comments2023-12-06T18:45:51.800-08:00Comments on Dot Net Tips & Tricks , C# (C Sharp)Tips & Tricks: Using Vb.Net Function in VBAUnknownnoreply@blogger.comBlogger3125tag:blogger.com,1999:blog-6497434045878013201.post-89674253599088640192008-12-16T19:06:00.000-08:002008-12-16T19:06:00.000-08:00My limited understanding is that there are differe...My limited understanding is that there are differences between DLLs. A COM (VB6 or C++) DLL should interface with VBA without much performance hit. But don't VB.net DLLs require various shims and interface code to talk to VBA?Jon Peltierhttps://www.blogger.com/profile/05234895820595509962noreply@blogger.comtag:blogger.com,1999:blog-6497434045878013201.post-33649889765612875452008-12-16T18:13:00.000-08:002008-12-16T18:13:00.000-08:00Ideally it shoudn't be a big a performance penalty...Ideally it shoudn't be a big a performance penalty as the Vb.NET code is a compiled one and used as another DLL by VBA.<BR/><BR/>Though the difference in performance wouldn't be felt for small arrays, using .NET function is quicker for large arraysAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-6497434045878013201.post-36361842573905560882008-04-27T17:29:00.000-07:002008-04-27T17:29:00.000-07:00Interesting to see an example of a .Net function c...Interesting to see an example of a .Net function called from "plain old" VBA.<BR/><BR/>How does the performance of this approach compare to using a bubble sort or quick sort function in VBA? Is there a penalty for leaving th VBA thread to access the .Net assembly?Jon Peltierhttps://www.blogger.com/profile/05234895820595509962noreply@blogger.com