Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We have a development company we are working with that wants to use VB.NET since that’s what they are most comfortable with and we prefer C#. This is a pretty large ASP.NET MVC software project and all of the front end will be done in JavaScript, so the .NET is server side only. Should we worry about them staying in VB and us in C#? What would be negatives of proceeding like this forward?
Are the lines in the project so clear cut that you’re not going to be in the VB.NET code and they’re not going to be in your C#? It is rarely ever that clean and thus there will be a lot of context switching when you jump between files. You’re also asking a lot of whoever is going to maintain your project. Whoever is going to maintain it should probably get the first vote for the language.