.NET
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Which to go for C#/VB.NET for Customization

7 REPLIES 7
Reply
Message 1 of 8
nalawadesachin
195 Views, 7 Replies

Which to go for C#/VB.NET for Customization

Which is better C#.NET or VB.NET for Customization of AutoCAD?
I am using VBA now and in future want's to switch over to one of the above so need guidance so i can start working on it.
Thanks
7 REPLIES 7
Message 2 of 8
Anonymous
in reply to: nalawadesachin

Hi,

It's really a very simple decision.

Which do you prefer, given that most of the people doing it are using C# and
the Autodesk support guys tend to prefer C#, so the help examples are more
likely to be first written in C# and may be later ported to VB.

You have to balance that against the applicability of your VB understanding
to be easily ported to VB.NET
--


Regards

Laurie Comerford
wrote in message news:5892323@discussion.autodesk.com..
Which is better C#.NET or VB.NET for Customization of AutoCAD?
I am using VBA now and in future want's to switch over to one of the above
so need guidance so i can start working on it.
Thanks
Message 3 of 8
Anonymous
in reply to: nalawadesachin

I'd say there is no question in the acad arena.
The guys that know the answers to the hard questions are ObjectArx programmers, and they almost always go C#.
Also, many questions are answered by looking at objectarx examples, as well as the SDK.
I like each for different reasons, but the .net API for acad is essentially toned down (managed) ObjectArx.
I don't see how you can avoid it, and C# syntax is not hard compared to the other challenges of .net.
Its dealing with the object oriented environment that takes getting used to...inheritance, casting, conversions,
delegates...and the Adesk .net api.

Laurie Comerford
|>Hi,
|>
|>It's really a very simple decision.
|>
|>Which do you prefer, given that most of the people doing it are using C# and
|>the Autodesk support guys tend to prefer C#, so the help examples are more
|>likely to be first written in C# and may be later ported to VB.
|>
|>You have to balance that against the applicability of your VB understanding
|>to be easily ported to VB.NET
James Maeding
Civil Engineer and Programmer
jmaeding - at - hunsaker - dotcom
Message 4 of 8

Thanks a lot.
Iwill start up with C# then as just started my career in Customization.C# has long way to go so will help me
to get better jobs
Thanks
Sachin Nalawade
Pune
Message 5 of 8
jbooth
in reply to: nalawadesachin

Despite what you hear, these two languages are nearly identical. They both use the same libraries, and they both compile to the same intermediate language (IL). One of the few real differences is syntax. Other differences include extra features like the My namespace, but none of these differences are essential.

If you can understand both C# and VB.NET, you have the option to use either. The advantage of using one over the other is minimal.
Message 6 of 8
Anonymous
in reply to: nalawadesachin

Sorry, the languages aren't identical, not even close.

Perhaps you're confusing APIs and languages.

--
http://www.caddzone.com

AcadXTabs: MDI Document Tabs for AutoCAD 2009
Supporting AutoCAD 2000 through 2009
http://www.acadxtabs.com

wrote in message news:5894018@discussion.autodesk.com...
Despite what you hear, these two languages are nearly identical. They both use the same libraries, and they both compile to the same intermediate language (IL). One of the few real differences is syntax. Other differences include extra features like the My namespace, but none of these differences are essential.

If you can understand both C# and VB.NET, you have the option to use either. The advantage of using one over the other is minimal.
Message 7 of 8
jbooth
in reply to: nalawadesachin

Thanks for clarifying.

I still stand by my comment that there is little advantage choosing one over the other.
Message 8 of 8
Anonymous
in reply to: nalawadesachin

well, true if you are on a desert island.
But the .net API for acad is just like the ObjectArx API, and the people that know it have to be C++'rs.
So the advantage is being able to read help posted by experts.

Its funny to see good acad coders code in vb.net, when you know they are thinking in C++.
I guess you just get good at both, and be familiar with how to mix vb and C# projects in one VS solution.

Jason Booth <>
|>Thanks for clarifying.
|>
|>I still stand by my comment that there is little advantage choosing one over the other.
James Maeding
Civil Engineer and Programmer
jmaeding - at - hunsaker - dotcom

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk DevCon in Munich May 28-29th


Autodesk Design & Make Report

”Boost