.NET
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
*James Maeding
Is .net API only available through C#, or can VB.net do it?
Options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
64 Views, 4 Replies
08-31-2005 03:41 PM
I am good at lisp and VB, but not .net yet (if ever).
Is there any use in going to VB.net verses VB6 in terms of gaining powere over acad?
Can vb.net use the .net API for acad, or does it just use the COM API?
Do I have to go to C# to use the .net API for acad?
Sorry for such mundane questions, feel free to redirect me to other threads on this subject.
thx
James Maeding
Civil Engineer and Programmer
jmaeding - athunsaker - com
Is there any use in going to VB.net verses VB6 in terms of gaining powere over acad?
Can vb.net use the .net API for acad, or does it just use the COM API?
Do I have to go to C# to use the .net API for acad?
Sorry for such mundane questions, feel free to redirect me to other threads on this subject.
thx
James Maeding
Civil Engineer and Programmer
jmaeding - athunsaker - com
Re: Is .net API only available through C#, or can VB.net do it?
Options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
08-31-2005 04:07 PM in reply to:
*James Maeding
Any .NET language can use the AutoCAD .NET API. You can also still use the ActiveX API. There is more power in the .NET API.
Here is a free book on upgrading from VB6 to VB.NET.
http://msdn.microsoft.com/vbrun/staythepath/additi
Regards - Nathan
Here is a free book on upgrading from VB6 to VB.NET.
http://msdn.microsoft.com/vbrun/staythepath/additi
Regards - Nathan
*James Maeding
Re: Is .net API only available through C#, or can VB.net do it?
Options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
09-01-2005 10:31 AM in reply to:
*James Maeding
cool, I'll read that too.
I read parts of Dan Appleman's book "Moving to VB.net" and am convinced its a next generation language.
I went to an AU class last year that made me think you might as well learn ARX if you want the power of the acad .net
API.
That was discouraging as who out there has time to write pages of code that can be done with lisp in four lines?
Its like you have to have major serious need before going to .net, the other languages are still very powerful.
Time and stability are the issues, and very few have either to spare.
Nathan Taylor <>
|>Any .NET language can use the AutoCAD .NET API. You can also still use the ActiveX API. There is more power in the .NET API.
|>
|>Here is a free book on upgrading from VB6 to VB.NET.
|>http://msdn.microsoft.com/vbrun/staythepath/addi
|>
|>Regards - Nathan
James Maeding
Civil Engineer and Programmer
jmaeding - athunsaker - com
I read parts of Dan Appleman's book "Moving to VB.net" and am convinced its a next generation language.
I went to an AU class last year that made me think you might as well learn ARX if you want the power of the acad .net
API.
That was discouraging as who out there has time to write pages of code that can be done with lisp in four lines?
Its like you have to have major serious need before going to .net, the other languages are still very powerful.
Time and stability are the issues, and very few have either to spare.
Nathan Taylor <>
|>Any .NET language can use the AutoCAD .NET API. You can also still use the ActiveX API. There is more power in the .NET API.
|>
|>Here is a free book on upgrading from VB6 to VB.NET.
|>http://msdn.microsoft.com/vbrun/staythepath/addi
|>
|>Regards - Nathan
James Maeding
Civil Engineer and Programmer
jmaeding - athunsaker - com
*Tony Tanzillo
Re: Is .net API only available through C#, or can VB.net do it?
Options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
09-01-2005 12:15 PM in reply to:
*James Maeding
"write pages of code that can be done with
lisp in four lines?"
The number of lines of code are not the issue. The
issue is the limitations of the API/language, and the
qualifications and skills of the one who is writing the
code.
Many things I do with ObjectARX, cannot be done with
40,000 lines of LISP, or any number of lines of LISP for
that matter, because those things can't be done with
LISP.
It's not about a language 'preference', because that
implies that all of the langauges/APIs are equivalent
in terms of capabilities, which is not the case.
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
"James Maeding" wrote in message news:4945525@discussion.autodesk.com...
cool, I'll read that too.
I read parts of Dan Appleman's book "Moving to VB.net" and am convinced its a next generation language.
I went to an AU class last year that made me think you might as well learn ARX if you want the power of the acad .net
API.
That was discouraging as who out there has time to write pages of code that can be done with lisp in four lines?
Its like you have to have major serious need before going to .net, the other languages are still very powerful.
Time and stability are the issues, and very few have either to spare.
Nathan Taylor <>
|>Any .NET language can use the AutoCAD .NET API. You can also still use the ActiveX API. There is more power in the .NET API.
|>
|>Here is a free book on upgrading from VB6 to VB.NET.
|>http://msdn.microsoft.com/vbrun/staythepath/addi
|>
|>Regards - Nathan
James Maeding
Civil Engineer and Programmer
jmaeding - athunsaker - com
lisp in four lines?"
The number of lines of code are not the issue. The
issue is the limitations of the API/language, and the
qualifications and skills of the one who is writing the
code.
Many things I do with ObjectARX, cannot be done with
40,000 lines of LISP, or any number of lines of LISP for
that matter, because those things can't be done with
LISP.
It's not about a language 'preference', because that
implies that all of the langauges/APIs are equivalent
in terms of capabilities, which is not the case.
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
"James Maeding"
cool, I'll read that too.
I read parts of Dan Appleman's book "Moving to VB.net" and am convinced its a next generation language.
I went to an AU class last year that made me think you might as well learn ARX if you want the power of the acad .net
API.
That was discouraging as who out there has time to write pages of code that can be done with lisp in four lines?
Its like you have to have major serious need before going to .net, the other languages are still very powerful.
Time and stability are the issues, and very few have either to spare.
Nathan Taylor <>
|>Any .NET language can use the AutoCAD .NET API. You can also still use the ActiveX API. There is more power in the .NET API.
|>
|>Here is a free book on upgrading from VB6 to VB.NET.
|>http://msdn.microsoft.com/vbrun/staythepath/addi
|>
|>Regards - Nathan
James Maeding
Civil Engineer and Programmer
jmaeding - athunsaker - com
*Bobby C. Jones
Re: Is .net API only available through C#, or can VB.net do it?
Options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
09-01-2005 12:55 PM in reply to:
*James Maeding
Hey James,
And the 2006 version of the .NET API is even richer than what you saw last
year for 2005. It's still as simple as more power = more complexity.
Embrace the complexity and enjoy the power that comes with it :-)
--
Bobby C. Jones
http://www.acadx.com
"James Maeding" wrote in message
news:4945525@discussion.autodesk.com...
cool, I'll read that too.
I read parts of Dan Appleman's book "Moving to VB.net" and am convinced its
a next generation language.
I went to an AU class last year that made me think you might as well learn
ARX if you want the power of the acad .net
API.
That was discouraging as who out there has time to write pages of code that
can be done with lisp in four lines?
Its like you have to have major serious need before going to .net, the other
languages are still very powerful.
Time and stability are the issues, and very few have either to spare.
Nathan Taylor <>
|>Any .NET language can use the AutoCAD .NET API. You can also still use the
ActiveX API. There is more power in the .NET API.
|>
|>Here is a free book on upgrading from VB6 to VB.NET.
|>http://msdn.microsoft.com/vbrun/staythepath/addi
b6/
|>
|>Regards - Nathan
James Maeding
Civil Engineer and Programmer
jmaeding - athunsaker - com
And the 2006 version of the .NET API is even richer than what you saw last
year for 2005. It's still as simple as more power = more complexity.
Embrace the complexity and enjoy the power that comes with it :-)
--
Bobby C. Jones
http://www.acadx.com
"James Maeding"
news:4945525@discussion.autodesk.com...
cool, I'll read that too.
I read parts of Dan Appleman's book "Moving to VB.net" and am convinced its
a next generation language.
I went to an AU class last year that made me think you might as well learn
ARX if you want the power of the acad .net
API.
That was discouraging as who out there has time to write pages of code that
can be done with lisp in four lines?
Its like you have to have major serious need before going to .net, the other
languages are still very powerful.
Time and stability are the issues, and very few have either to spare.
Nathan Taylor <>
|>Any .NET language can use the AutoCAD .NET API. You can also still use the
ActiveX API. There is more power in the .NET API.
|>
|>Here is a free book on upgrading from VB6 to VB.NET.
|>http://msdn.microsoft.com/vbrun/staythepath/addi
b6/
|>
|>Regards - Nathan
James Maeding
Civil Engineer and Programmer
jmaeding - athunsaker - com
