VB 2005 Syntax

  • Thread starter Thread starter Sharrukin Amiri
  • Start date Start date
S

Sharrukin Amiri

Hello,

I have issues which I do not know how to go about. For example, reading and
writing into a textfile.txt. I have looking into some videos from
learningvisualstudio.net. The instructor makes the syntax look easy. My
question is how does he know what to do? As a 15 year programmer from vb6
coming to vb2005, things are not easy as they seem. If one is writing an
app for selling purposes, this could invite a lot of debugging problems and
gray hair. Because the syntax is foreign and new, how does one go about
trusting his/her own syntax. How many people use vb2005 for production and
not for learning. Am I correct in what I am saying? or am I on the wrong
track?

Please help!

Sharrukin



--



Warm Regards,

Sharrukin
 
buy yourself a good book

as you are a VB6 programmer you should best buy

programming microsoft visual basic VB.Net 2003 and 2005 from francesco
balena as these books are especially usefull for VB6 programmers


I started with Basic on the C64 :-) but never stopped learning new
technology`s i guess you have some catching up to do :-)

regards

Michel Posseth [MCP]
 
Hello Sharrukin,

Neat name, if it's real.

Anyhow.. VB.NET syntax is not all that different from VB6. I spent probably
a good 2 months in learning before I was confidant enough to use it in production.
Here's some of the biggest thing's to keep in mind (at least for me).. there
are undoubtedly a myriad of minor things but those are easy to catch as you
code.

1. Constructors.. proper ctor overloading can make a world of difference,
not only in how you create an object, but it can, to a smaller extent, affect
architecture as well.

2. Variable instantiation during declaration.. (ex. Dim tName as string
= "Joe"... or Dim tName As String = String.Empty)

Those two things are probably the two most time-saving and helpful things
I notice in every-day coding. There are, as I said before, a myriad of other
minor things.. but the VS IDE handles of lot of it for you.. (like property
accessor sytax and interface implementations)..

Books are good for a one-shot deal. My problem with books is that they depreciate
uin value almost as fast as new vehicles.. and I only use them once.. and
usually I only use a fraction of them. The last programming book I bought
I looked at one chapter and have never looked at it since. Ah well. $45.00
well spent. HA.

-Boo
 
Books are good for a one-shot deal. My problem with books is that they
depreciate
uin value almost as fast as new vehicles.. and I only use them once.. and
usually I only use a fraction of them. The last programming book I bought
I looked at one chapter and have never looked at it since. Ah well.
$45.00 well spent. HA.
Click to expand...



I thought so to untill i bought the "right" books


regards

Michel Posseth [MCP]


GhostInAK said:
Hello Sharrukin,

Neat name, if it's real.

Anyhow.. VB.NET syntax is not all that different from VB6. I spent
probably a good 2 months in learning before I was confidant enough to use
it in production. Here's some of the biggest thing's to keep in mind (at
least for me).. there are undoubtedly a myriad of minor things but those
are easy to catch as you code.

1. Constructors.. proper ctor overloading can make a world of difference,
not only in how you create an object, but it can, to a smaller extent,
affect architecture as well.

2. Variable instantiation during declaration.. (ex. Dim tName as string
= "Joe"... or Dim tName As String = String.Empty)

Those two things are probably the two most time-saving and helpful things
I notice in every-day coding. There are, as I said before, a myriad of
other minor things.. but the VS IDE handles of lot of it for you.. (like
property accessor sytax and interface implementations)..

Books are good for a one-shot deal. My problem with books is that they
depreciate uin value almost as fast as new vehicles.. and I only use them
once.. and usually I only use a fraction of them. The last programming
book I bought I looked at one chapter and have never looked at it since.
Ah well. $45.00 well spent. HA.

-Boo
Click to expand...
 
Back
Top