Heath Stewart wrote: If you need to maintain the source, why not just learn VB.NET? And while you're at it, COBOL .Net and Fortran .Net work pretty well too. Why don't you mix some of them into your project? Then nobody on your team will be able to maintain your project. Job security, man! Top 10 Reasons to mix languages as much as possible: #10: Find all those hidden inter-language bugs before all your buddies! #9: Flaunt company coding standards #8: Help prepare you for the MCSD exams instead of working, like you're paid to do #7: Since nobody else can read your code, you stay employed longer #6: Unable to cut-and-paste between different languages forces better encapsulation and prevents clipboard inheritance #5: Adds at least one more language item to your resume! #4: Microsoft *never* has a history of modifying a language like VB after everyone has already learned it #3: Experience the magic of inter-language type-casting! #2: Because occasionally your semi-colon pinky gets tired And the top reason to mix languages in .Net as much as possible: #1: Just because your boss told you not to do it, doesn't necessarily mean you'll actually get fired for trying. - Tony Goggin