> All of this will cost you. Interop is not free. There's a whole level of indirection to go through.
Yeah, I just find it strange at times. For instance, we had a DTS package that used some VB classes that simply do some simple data transformation and return it to the VBScript in the package. We took out the VB classes, wrote some C# classes, and there was a significant speed improvement (15x, event using reflection as everything was accepted as an object -- we simply didn't want to find the necessary dll to reference). It just seems awfully strange that in that instance there was an incredibly speed boost, whereas in this instance, there is a decent speed loss. Although it is probably understandable, as the types passed to the C# classes were pretty simple. > For instance, marking the class with: [ClassInterface(ClassInterfaceType.AutoDual)] to generate a dual > interface or whatever to get the early binding behavior. There are a lot of other things you can do. I'm not too incredibly worried about early binding. Mainly I don't want to get the VB classes dependent on a type library that will break the next time I export it. >I would suggest looking at Adam Nathan's book for detailed explanations. I'm on chapter 9, looking for anything useful :) Adam.. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
