Multi-language support for asp.net 2.0 in the same project won't generate quite a mess?

H

Hans Baumann

Hello,

I am a .net developer over 3-4 years, using both C# and VB in different
scenarios (web services, web app, windows app, etc..) leading a small group
of programmers for two years in an intranet development.

The fact is that in my little experience leading a development team, I've
learnt that one of the basis to achieve goals is standarization, including
the preferred language to develop. In this case I chose VB because of the
many "classic-asp" programmers came to my team, and to minimize the impact
in the new platform.

But I started looking the new asp.net 2.0 and you can develop in the same
web application, web forms with C#/VB code, so, at first sight you can say
"Oh! excellent, my programmers now can develop in the language they feel
more comfortable!" but what happens when that C#-star-programmer has to
leave the team and another with a more VB-profile comes in, he will see a
20% of the app written in C#, and he has to learn the new synthax, and even
worse, suppose a new programmer has to take the lead of the coding of the
same app, now he has to learn basically two synthaxs!! (notice I'm not
saying languague because of the common plattform types)

Any opinions about this? how do I face a new asp.net 2.0 projects? Should I
let them to code in different languages in the same app?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,755
Messages
2,569,536
Members
45,009
Latest member
GidgetGamb

Latest Threads

Top