I can try this out, but I thought I'd ask here whether anybody has any experience with this.

My actual situation is that I have a program that dynamically loads some .NET dlls. Currently, everything is written in VB. In VS, you can be debugging a project and step right into the dynamically loaded dlls. This is still pretty amazing to me. The dll doesn't have to be anywhere in particular. In my case, the dynamic dlls are in one folder somewhere, while the projects that created the dlls are in the default Projects folder for the VS that was used to create them. The dynamic dlls are the release versions, too, so they don't contain symbol information. Still, VS has no problem finding the source code when I step into code in one of those dynamic dlls, and stepping right into it. Of course, if the dynamically loaded dll is not in sync with the source code, then problems arise, but as long as they are in sync, I don't even have to tell VS where the source is located.

So, there's no reason why a C# dll wouldn't work just as well as a VB dll for dynamic loading. What I'm curious about is what happens when stepping through code. Will it step right into C# from VB? My guess is that it will, and I can test it without great difficulty, but I'm wondering if anybody has any experience with stepping into C# dlls from VB, or vice versa. Are there any issues I'll need to be aware of? Any problems that might come up?