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

Are there docs on learning VB.net for acad?

10 REPLIES 10
Reply
Message 1 of 11
Anonymous
473 Views, 10 Replies

Are there docs on learning VB.net for acad?

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
10 REPLIES 10
Message 2 of 11
Anonymous
in reply to: Anonymous

I have one or two very generic ones up on CADalyst http://tinyurl.com/6auc5

You can also check out www.acadx.com and I believe AUGI

-- Mike
___________________________
Mike Tuersley
___________________________
the trick is to realize that there is no spoon...
Message 3 of 11
Anonymous
in reply to: Anonymous

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
Message 4 of 11
NathTay
in reply to: Anonymous

The great thing about VB.NET in my opinion is that you are still using the basic syntax that I first used in QBasic but it has access to the power of the .NET Framework. As the power is in the framework language choice is not as important anymore.

Regards - Nathan
Message 5 of 11
Anonymous
in reply to: Anonymous

the thing is, VB6 was so nice and "canned", but objectarx is not IMO.
So now we are starting to code things that look more like arx with .net.
Its like the language does not matter because we are now writing what is almost C code in a VB IDE.
The cool thing is we get a huge return for participating in the transition, whether we like it or not.
I just hope I dont run into a bunch of little things missing like so often happens when transitioning to new things
adesk is doing. Many times those little things were critical links in a programs chain.


Nathan Taylor <>
|>The great thing about VB.NET in my opinion is that you are still using the basic syntax that I first used in QBasic but it has access to the power of the .NET Framework. As the power is in the framework language choice is not as important anymore.
|>
|>Regards - Nathan

James Maeding
Civil Engineer and Programmer
jmaeding - athunsaker - com
Message 6 of 11
Anonymous
in reply to: Anonymous

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
Message 7 of 11
Anonymous
in reply to: Anonymous

You really don't need to learn the .NET API to use VB.NET with AutoCAD. You
can also use the COM object model (the one you use with VB6).

albert

"James Maeding" wrote in message
news:4960503@discussion.autodesk.com...
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
Message 8 of 11
Anonymous
in reply to: Anonymous

I have a concern as a beginer, I have never work with VB6 or VB.Net... So i
am still confuse as of which to learn and use with autocad after reading all
your comment...... So confuse

Binny
"Albert Szilvasy" wrote in message
news:4961045@discussion.autodesk.com...
You really don't need to learn the .NET API to use VB.NET with AutoCAD. You
can also use the COM object model (the one you use with VB6).

albert

"James Maeding" wrote in message
news:4960503@discussion.autodesk.com...
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
Message 9 of 11
Mikko
in reply to: Anonymous

Bottom line is there is no more VB6. It is out-of-date and I believe, now unsupported by Microsoft. VB.NET is VB and has been for the last several years. Do not get confused with this. I think what most people are talking about is whether to learn the COM.Interop or the new .NET API which was released for 2006. They both work very well, separately or together.
Message 10 of 11
Anonymous
in reply to: Anonymous

I have never liked the com object model because of the lack of utility functions like GrDraw, GrVecs and GrRead.
I am hoping the .net api will allow me to mimic the things I used to do with these...

Its interesting that VBA still uses old VB but .net is the current "outside" acad language.
Wonder if we might see VBA.net sometime, or if that even makes sense...

Mikko <>
|>Bottom line is there is no more VB6. It is out-of-date and I believe, now unsupported by Microsoft. VB.NET is VB and has been for the last several years. Do not get confused with this. I think what most people are talking about is whether to learn the COM.Interop or the new .NET API which was released for 2006. They both work very well, separately or together.

James Maeding
Civil Engineer and Programmer
jmaeding - athunsaker - com
Message 11 of 11
Anonymous
in reply to: Anonymous

"VBA.NET" is called VSTA (Visual Studio Tools for Applications) and was
announced at last week's PDC. See
http://msdn.microsoft.com/vstudio/extend/vsta/default.aspx

Dan

"James Maeding" wrote in message
news:4961619@discussion.autodesk.com...
I have never liked the com object model because of the lack of utility
functions like GrDraw, GrVecs and GrRead.
I am hoping the .net api will allow me to mimic the things I used to do with
these...

Its interesting that VBA still uses old VB but .net is the current "outside"
acad language.
Wonder if we might see VBA.net sometime, or if that even makes sense...

Mikko <>
|>Bottom line is there is no more VB6. It is out-of-date and I believe, now
unsupported by Microsoft. VB.NET is VB and has been for the last several
years. Do not get confused with this. I think what most people are talking
about is whether to learn the COM.Interop or the new .NET API which was
released for 2006. They both work very well, separately or together.

James Maeding
Civil Engineer and Programmer
jmaeding - athunsaker - com

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