Thanks, Chris. This is actually my third major .NET project and I totally 
knew the solution (adding a reference), but I just blanked out, probably 
because I was approaching it from a different perspective. Thanks for 
pointing the nose on my face. :)

At 11:09 PM 2/26/2003 -0500, Chris wrote:
>Ensure that the namespace for the classes makes sense in your solution -
>don't forget to check the AssemblyInfo.cs file to ensure that the assembly
>is properly named there.  Then add a REFERENCE to that assembly to your VB
>project.  Voila!  You should now be able to use the classes in the C#
>project as you do any other assembly, including seeing methods and
>properties in Intellisense in VB.  When your solution is built, another
>assembly (.dll) containing the C# compiled code will end up in the bin
>directory as part of the application.

::::::::::::::::::::::::::::::::::
Howard Cheng
http://www.howcheng.com/
howcheng at ix dot netcom dot com
AIM: bennyphoebe
ICQ: 47319315