We've banged the question around here quite a bit and I, similar to you, am the point man for half the developers here who want to use .net. I disagree to an extent that moving java developers to .net is costly since J# is available and C# is pretty much the same. Good java developers can pick it up in a few days OTJT. I did a comparison writing a small gui that read in a file, built a tree, displayed some data and printed some reports. The java developer (an instructor for a consulting company here in Dallas so he knew his stuff :~ ) wrote the java version and I wrote the C# version. It took ~5 hours to do the C# version with all the functionality. The java program was able to read the file, display some of the tree (he had a hard time parsing the file) and could display the data for the nodes after 10 hours. He gave up at that point! :laugh: We were also able to compare asp.net to jsp/struts. We were able to build a very complex form to send data to a database in a little less than a day. The java guys (2 of them) took over four weeks. (The java guys actually worked on this project for some time before someone asked what they were doing. When we found out we looked at what they did and one of the .net guys built the app the next day.) These are small comparisons to which the java folks say don't have anything to do with anything but I look at it this way.... Java will give you job security. ;P It takes longer to develop with it, it is harder to deploy and harder to maintain. In the long run or if making money is an objective...go with .net. If job security (through lack of work) is the issue, then go with java. ed Regulation is the substitution of error for chance.