lol -- imagine COBOL.NET -- sounds like an oxy moron... I think you are right, although the languages should be able to support OO style in order to integrate .NET. and if you have multiple languages in one program, you have to be sure you interface correctly to take into account calling conventions -- passing by value vs by reference, handling of arrays, etc. --le ----- Original Message ----- From: Homme, James To: programmingblind@xxxxxxxxxxxxx Sent: Wednesday, June 23, 2010 1:09 PM Subject: .Net Impressions, Right Or Wrong Hi, Am I getting the right impression about this? From what I'm reading, you can pick many different languages. They all use the .Net Framework Classes. Therefore, it only matters which language you use if you are working in an environment where that language is used. For example, if you work somewhere and they use C# with .net, then you'd want to learn C#. If you worked or had fun somewhere in which they use VB.Net, then you'd want to learn that language. The same would apply if you wanted to use Python in the .Net environment. You could use Python, but you'd be able to access the classes in the .Net framework, but with Python. And the same would go for Cobol, assuming there is some sort of Cobol something that uses .Net. Is that anywhere in the ball park? Thanks. Jim Jim Homme, Usability Services, Phone: 412-544-1810. Skype: jim.homme Internal recipients, Read my accessibility blog. Discuss accessibility here. Accessibility Wiki: Breaking news and accessibility advice ------------------------------------------------------------------------------ This e-mail and any attachments to it are confidential and are intended solely for use of the individual or entity to whom they are addressed. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not keep, use, disclose, copy or distribute this e-mail without the author's prior permission. The views expressed in this e-mail message do not necessarily represent the views of Highmark Inc., its subsidiaries, or affiliates.