Follow me on Twitter at Twitter.com/wbm
FYI, I'm blogging most of my stuff over at More Wally now.
You might want to add my rss feed to your reader at:http://morewally.com/cs/blogs/wallym/rss.aspx
Visual Basic .NET <--> C# - Wallace B. McClure

Wallace B. McClure

All About Wally McClure - The musings of Wallym on MonoTouch for iPhone, MonoDroid for Android, and Windows Azure.

News

Personal Blog

Work Blog

.NET

Book Authors

Business

Family

Friends

Georgia Tech Bloggers

Personal

Archives

Visual Basic .NET <--> C#

I switch back and forth between Visual Basic and C#.  Sometimes, the project changes, but I keep writing the same code.  For some reason, I keep wanting to put the "static" keyword into my VB code.  I should have been using "shared" in VB/NET.  I couldn't figure out the error while I stared straight at the code for a few minutes.  What stumps you in switching between the two languages?

Geez, I wish this compiler error really existed in the Visual Studio .NET 2003.  Hmmm, as the graphic in Whidbey says, maybe I should go back to night school.

Posted: Mar 17 2005, 07:52 AM by Wallym | with 3 comment(s)
Filed under:

Comments

Scott Galloway said:

Not really VB.NET, more VB / VBScript...but I habitually add semicolons to the end of lines and forget that I need a 'then' and an 'end if' in if...then statements...
# March 17, 2005 8:02 AM

Karl said:

[] and ()

and in VB.Net I often do
i often do:
byval string x, byval int y

in my parameter list, but likely because I spend more time in C#

select/switch is another one too :)
# March 17, 2005 9:30 AM

TrackBack said:

Visual Basic .NET C#

For me it&#8217;s all the simple stuff. I don&#8217;t know how many times I&#8217;ve typed in string _name; in a VB.NET class and gotten an error.

What really gets me though is all the damn TYPING I have to do when I&#8217;m ...
# March 17, 2005 9:54 AM
Leave a Comment

(required) 

(required) 

(optional)

(required)