I may be starting a new ASP.NET job that is going to use, dare I say it, VB.NET rather than C#. I learned C# to get out of the VB6 world, but like a bad dream it keeps haunting me. I've read some 'Best kept secrets of VB.NET' on the web that are standard practice in C# and it scares me.
I have my C# to VB.NET cheat sheet, but can any of you other C#'ers point me to some other sites you know of that may not be in my list? Or any gotcha's that really threw you for a loop...such as the use of the Shadows keyword and the fact that they still (for some stupid reason) allow you to not have Option Explicit... why, WHY, would any good coder NOT want this on, all the time, and unchangeable?! VB really just does things the hard way IMHO.
I have my C# to VB.NET cheat sheet, but can any of you other C#'ers point me to some other sites you know of that may not be in my list? Or any gotcha's that really threw you for a loop...such as the use of the Shadows keyword and the fact that they still (for some stupid reason) allow you to not have Option Explicit... why, WHY, would any good coder NOT want this on, all the time, and unchangeable?! VB really just does things the hard way IMHO.