I disagree with that statement, I don't have to know all that much about .Net to realize the current stuff is handeling the job masterfully, and that rewriting in another language (any other language) will take lots of
time/money/effort/risk/interuption. Meanwhile I am developing new features everyday that save use time/effort/money that would be posponed during a transition. So there would have to be a GIANT return to justify this, what would that be?

Fox is not right for every job, it is right for this one

.Net is not right for every job, would probally be OK for this project, but extremely costly for a small company.

.Net is probably good for your job, but other languages could handle it just fine as well, I'm sure.

>You cannot say that, you don't know enough about .Net to provide a qualified opinion.