Currently, there are only a handful of fairly minor differences in
functionality between the two languages (for example "using" in C#); it's
pretty much a choice of the syntax with which you're most comfortable.
VB.NET will appeal most to those who are familiar with VB6 and VBA, while C#
was designed to appeal to C++ and Java programmers.
Going forward, Microsoft has stated that they intend to allow both C# and
VB.NET to develop as separate languages so you might anticipate more
substantial differences in the future.
Dan
"James Maeding" wrote in message
news:4960950@discussion.autodesk.com...
After reading some more, and looking at code in vb.net and C#, they kind of
look the same.
Is there any totally obvious reason to go with C#?
I have always like how VB6 was "canned" for easy use of course, but it looks
like VB.net is really just VB wearing a net
- its naked!
thanks for any input.
Mike's Articles on the cadalyst management link were very useful so thanks,
Mike.
James Maeding
|>I have found many "vb.net with acad" examples, and the have looked at the
help files for the objectarx sdk,
|>but have not seen a walkthrough for people like me moving from vb6 to
vb.net.
|>
|>Part of the problem is I am new to all the arx stuff, I only know com
mostly.
|>I need to learn how all the transactions take place and how things work
with this new .net API.
|>
|>I have read several beginning books on vb.net now, and need the "beginning
.net with acad" side of things.
|>I miss things with examples, because they do not explain why things are
being done, just what is being done.
|>
|>This may be a pipe dream but does a walkthrough exist anywhere for
vb.net'ers?
|>thx
|>James Maeding
|>Civil Engineer and Programmer
|>jmaeding - athunsaker - com
James Maeding
Civil Engineer and Programmer
jmaeding - athunsaker - com
