Why post this, here of all places? My guess would be about 70% of Slashdot visitors hate Silverlight and 85% hate VB.
Apparently you think that being exposed to diverse viewpoints is a bad thing. 70% of Fox News fans hate Barack Obama. Wouldn't it be nice if they did some genuinely "Fair and Balanced" reporting on him sometime?
VB.Net has single line parameters, C# has XML Literals, and they are continuing to become more and more similar functionally speaking. The only big difference left now is multi-line lambdas and that C# is case sensitive.
-Rick
Optional parameters have finally been added to C# in.NET 4. Another way C# is catching up with VB;-)
The majority of difference between C# and VB at this point are due to there having been 2 teams at MS working on the VB.Net and C# editors for Visual Studio. Now, those teams have been merged.
-Rick
Interesting. Even though it's a language/compiler-specific behavior, my least favorite part of the C# editing environment - the problem with annoyingly persistent squigglies - has got MUCH better. (i.e. when you fix a compiler error you can tell its fixed without having to recompile the whole project).
Great proposal. Here's my disclaimer.
I was given the book for free. I forked out $50 for its predecessor (SL3). I thought the old book was great, and I loved the additions to the new one too. The main problems with it are those I identified in the review. My first para was probably too gushy, and who reads beyon the first para?
I have easier ways to earn $60 (spare me the jokes), and were I paid in cash I wouldn't have spent it on an update to a book I already owned. Said that in the review too.
Perhaps if you understood the difference between grammar/syntax and meaning/semantics you might make a decent programmer - in VB or any other language.
...or perhaps a snob's snob finding a reason to be civil? No, that seems to be too much of a stretch judging from the evidence here.
MM wrote this for C# also, and some of us are lucky enough to program in both languages. (Is that like mixing with the hoi polloi? Shame on me!).
Why post this, here of all places? My guess would be about 70% of Slashdot visitors hate Silverlight and 85% hate VB.
Apparently you think that being exposed to diverse viewpoints is a bad thing. 70% of Fox News fans hate Barack Obama. Wouldn't it be nice if they did some genuinely "Fair and Balanced" reporting on him sometime?
VB.Net has single line parameters, C# has XML Literals, and they are continuing to become more and more similar functionally speaking. The only big difference left now is multi-line lambdas and that C# is case sensitive.
-Rick
Optional parameters have finally been added to C# in .NET 4. Another way C# is catching up with VB ;-)
The majority of difference between C# and VB at this point are due to there having been 2 teams at MS working on the VB.Net and C# editors for Visual Studio. Now, those teams have been merged.
-Rick
Interesting. Even though it's a language/compiler-specific behavior, my least favorite part of the C# editing environment - the problem with annoyingly persistent squigglies - has got MUCH better. (i.e. when you fix a compiler error you can tell its fixed without having to recompile the whole project).
Great proposal. Here's my disclaimer. I was given the book for free. I forked out $50 for its predecessor (SL3). I thought the old book was great, and I loved the additions to the new one too. The main problems with it are those I identified in the review. My first para was probably too gushy, and who reads beyon the first para? I have easier ways to earn $60 (spare me the jokes), and were I paid in cash I wouldn't have spent it on an update to a book I already owned. Said that in the review too.
Perhaps if you understood the difference between grammar/syntax and meaning/semantics you might make a decent programmer - in VB or any other language.
...or perhaps a snob's snob finding a reason to be civil? No, that seems to be too much of a stretch judging from the evidence here. MM wrote this for C# also, and some of us are lucky enough to program in both languages. (Is that like mixing with the hoi polloi? Shame on me!).