What would be the negatives of having both C# and VB.NET code in large ASP.NET MVC project? [closed]

What would be the negatives of having both C# and VB.NET code in large
ASP.NET MVC project? [closed]

References

Reference NO 1

http://stackoverflow.com/questions/13655765/what-would-be-the-negatives-of-having-both-c-sharp-and-vb-net-code-in-large-asp

Reference NO 2

http://msdn.microsoft.com/en-us/library/ee671793(v=vs.100).aspx

Reference NO 3

http://msdn.microsoft.com/en-us/magazine/dd942833.aspx

Reference NO 4

http://coding.smashingmagazine.com/2012/07/02/dive-net-web-development/

Reference NO 5

http://net.tutsplus.com/articles/editorials/why-many-developers-hate-asp-net-and-why-they-are-wrong/

Reference NO 6

http://www.codeproject.com/Articles/416137/Understanding-Session-Management-Techniques-in-ASP

Reference NO 7

http://www.asp.net/web-api/overview/web-api-clients/calling-a-web-api-from-a-net-client

Reference NO 8

http://www.hanselman.com/blog/OneASPNETSneakPeekElegantWebFormsAndSnowballsInHell.aspx