DotNet vs ObjectArx vs VB

[Anonymous]

Dear members of forum.
I need opinion about design tool.
I designed ACAD applications using VB/VBA, Object ARX and now started to investigate DotNet. I already have some experience in DotNet(C#) but not in AutoCad.
I am going to create commercial Application in AutoCAD and I need to select designing tool. I tried to list all advantages and disadvantages of all three tools. For some points of this list I have no experience and I have no exact position about it. I am sure, that my view needed to be corrected.

1. Easy and fast design UI
• VB – easy and very fast
• ObjectARX – not fast and not easy
• DotNet(C#) – easy and very fast
• Interoperating with AutoCAD 2006 Type Library COM - ???

2. Easy and fast design of working with Acad
• VB – easy and very fast
• ObjectARX – not fast and not easy
• DotNet(C#) – ?????
• Interoperating with AutoCAD 2006 Type Library COM - ???

3. Design of other functions (algorithm and so on)
• VB – not enough good
• ObjectARX – good
• DotNet(C#) ––good

4. Debugging
• VB – very good
• ObjectARX – Bad
• DotNet(C#) – ?????
• Interoperating with AutoCAD 2006 Type Library COM - ???

5. Application Execution
• VB – not very fast but not bad
• ObjectARX – Fast
• DotNet(C#) – ????? (as I know DotNet is not enough fast)
• Interoperating with AutoCAD 2006 Type Library COM - ???

6. Deployment as commercial product
• VB – bad
• ObjectARX – good
• DotNet(C#) – ?????
• Interoperating with AutoCAD 2006 Type Library COM - ???

7. Bugs in designing tools
• VB – good
• ObjectARX – good
• DotNet(C#) – ????? (I already saw Bug with filtering Selection Set)
• Interoperating with AutoCAD 2006 Type Library COM - ???

8. Guides, tutors, books
• VB – good
• ObjectARX – not bad
• DotNet(C#) – bad

Any help, any correction, any views.
Thank you

[Anonymous]

how complex will your app be?
Will it have custom objects?
Will it be made to be used with lots of companies, or just a few?
In my opinion, service is the the highest goal - that is, fixing problems fast.
Stability is second.

So dont write in a language you do not understand well.
Seems like object ARX and .net are the only candidates now for serious future compatibility.
Lisp is good too but you have to use objectdcl to get decent dialog boxes, and that is third party stuff that is a bit
finicky to use...

emilg <>
|>Dear members of forum.
|>I need opinion about design tool.
|>I designed ACAD applications using VB/VBA, Object ARX and now started to investigate DotNet. I already have some experience in DotNet(C#) but not in AutoCad.
|>I am going to create commercial Application in AutoCAD and I need to select designing tool. I tried to list all advantages and disadvantages of all three tools. For some points of this list I have no experience and I have no exact position about it. I am sure, that my view needed to be corrected.
|>
|>1. Easy and fast design UI
|>• VB – easy and very fast
|>• ObjectARX – not fast and not easy
|>• DotNet(C#) – easy and very fast
|>• Interoperating with AutoCAD 2006 Type Library COM - ???
|>
|>2. Easy and fast design of working with Acad
|>• VB – easy and very fast
|>• ObjectARX – not fast and not easy
|>• DotNet(C#) – ?????
|>• Interoperating with AutoCAD 2006 Type Library COM - ???
|>
|>3. Design of other functions (algorithm and so on)
|>• VB – not enough good
|>• ObjectARX – good
|>• DotNet(C#) ––good
|>
|>4. Debugging
|>• VB – very good
|>• ObjectARX – Bad
|>• DotNet(C#) – ?????
|>• Interoperating with AutoCAD 2006 Type Library COM - ???
|>
|>5. Application Execution
|>• VB – not very fast but not bad
|>• ObjectARX – Fast
|>• DotNet(C#) – ????? (as I know DotNet is not enough fast)
|>• Interoperating with AutoCAD 2006 Type Library COM - ???
|>
|>6. Deployment as commercial product
|>• VB – bad
|>• ObjectARX – good
|>• DotNet(C#) – ?????
|>• Interoperating with AutoCAD 2006 Type Library COM - ???
|>
|>7. Bugs in designing tools
|>• VB – good
|>• ObjectARX – good
|>• DotNet(C#) – ????? (I already saw Bug with filtering Selection Set)
|>• Interoperating with AutoCAD 2006 Type Library COM - ???
|>
|>8. Guides, tutors, books
|>• VB – good
|>• ObjectARX – not bad
|>• DotNet(C#) – bad
|>
|>Any help, any correction, any views.
|>Thank you

James Maeding
Civil Engineer and Programmer
jmaeding - athunsaker - com

[Anonymous]

Thank you for general view. But I need serious understanding of some points of ObjectArx vs DotNet
1. execution speed
2. bugs in these tools
3. deployment
may be anybody have exactly view to these points.
Thank you

[Anonymous]

Visual Studio.NET is not without its problems.

I've not stressed it anywhere near the point that I've
stressed the Delphi IDE (which also has problems, but
I've been able to develop fairly massive projects and
complete object frameworks with it).

For example, the Forms designer has bugs that cause
strange things to happen, like controls moving around
a form or container; TabPages that mysteriously and
randomly changing their order in a TabControl, are just
a few I've seen.

There are also some compiler bugs that can cause
the IDE to lock up when you build a project. That's
a good reason to build every time you change a few
lines of code, or introduce a new type, or anything
like that, so you know what caused it.

Managed code is also notoriously slow, or at least,
by C++ and Delphi standards (not sure aobut VB
since I've never used it much).

--
http://www.caddzone.com

AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com

wrote in message news:4961065@discussion.autodesk.com...
Thank you for general view. But I need serious understanding of some points of ObjectArx vs DotNet
1. execution speed
2. bugs in these tools
3. deployment
may be anybody have exactly view to these points.
Thank you

[Anonymous]

Yes, in most cases managed code will be measurably slower than doing about
the same thing in C++ (I've never used Delphi). However, it's hard to
provide a 100% "apples to apples" comparision because the CLR is doing so
much behind the scenes that you would have to do manually in C++ (or if you
prefer "the CLR adds a lot of overhead").

However, the thing with performance is to determine if it really matters in
a particular situation. The performace of managed code is adaquate for
large classes of applications. For those situations where there really is a
critical path of code that must squeeze out every last cycle from the CPU,
it's fairly straight forward for managed and unmanaged code to interoperate.

Finally, it is possible to construct very special cases where managed code
is actually faster than similar C++ code; this is because the JITter can
optimize to the exact hardware configuration.

The .NET APIs for AutoCAD are going to be more productive for most people
than using native ObjectARX, which means you can get working code faster.
For many people, this increase in productivity will outweigh any potential
performance concerns.

Dan

"Tony Tanzillo" wrote in message
news:4961263@discussion.autodesk.com...
Visual Studio.NET is not without its problems.

I've not stressed it anywhere near the point that I've
stressed the Delphi IDE (which also has problems, but
I've been able to develop fairly massive projects and
complete object frameworks with it).

For example, the Forms designer has bugs that cause
strange things to happen, like controls moving around
a form or container; TabPages that mysteriously and
randomly changing their order in a TabControl, are just
a few I've seen.

There are also some compiler bugs that can cause
the IDE to lock up when you build a project. That's
a good reason to build every time you change a few
lines of code, or introduce a new type, or anything
like that, so you know what caused it.

Managed code is also notoriously slow, or at least,
by C++ and Delphi standards (not sure aobut VB
since I've never used it much).

--
http://www.caddzone.com

AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com

wrote in message news:4961065@discussion.autodesk.com...
Thank you for general view. But I need serious understanding of some points
of ObjectArx vs DotNet
1. execution speed
2. bugs in these tools
3. deployment
may be anybody have exactly view to these points.
Thank you