Debugging vb.net seems to be time consuming compared to earlier VB6 ?

[Anonymous]

I have been wondering why it seems to be neccesary to make AutoCAD start up every time I want to debug a dll in .NET
Debugging seemed a lot easier in the old times. Then I just had to fire up AutoCAD once and for all - open a drawing of interest to my code and then run my dll code from within VB6

Therefore I have - until now - made most of my vb-code as a Windows form application not using managed code but instead referring to the COM AutoCAD 2010 Type Libary plut the COM AutoCAD/ObjectDBX Common 18.0 Type Libary. This enables me to debug my entire application without having to make Visual Studio Express start AutoCAD every time I want to check my code!
I just call my executable with a command parameter that represents the sub that I want to execute ... and it works out fine! But ...

1. I think that there must be an easier and more elegant way to do this ?
2. Much worse! I am having serious trouble accessing AEC and MEP objects via the COM interface.

Can anyone help me out on this please?

BR
Jan Grenov

[Anonymous]

Hi Jan,

If anybody can hep you with NET issues you are far more likely to
contact them in the NET newsgroup.

VBA does not create these de-bugging issues.


Regards,


Laurie Comerford

JanGrenov wrote:
> I have been wondering why it seems to be neccesary to make AutoCAD start up every time I want to debug a dll in .NET
> Debugging seemed a lot easier in the old times. Then I just had to fire up AutoCAD once and for all - open a drawing of interest to my code and then run my dll code from within VB6
>
> Therefore I have - until now - made most of my vb-code as a Windows form application not using managed code but instead referring to the COM AutoCAD 2010 Type Libary plut the COM AutoCAD/ObjectDBX Common 18.0 Type Libary. This enables me to debug my entire application without having to make Visual Studio Express start AutoCAD every time I want to check my code!
> I just call my executable with a command parameter that represents the sub that I want to execute ... and it works out fine! But ...
>
> 1. I think that there must be an easier and more elegant way to do this ?
> 2. Much worse! I am having serious trouble accessing AEC and MEP objects via the COM interface.
>
> Can anyone help me out on this please?
>
> BR
> Jan Grenov
>

[Anonymous]

Oops - wrong forum ...
Thanks for your reply 🙂

Regards
Jan Grenov

[arcticad]

Just to answer the question, You will have limited access to objects using ActiveX, Autodesk is putting it's time into .NET.
COM access will be slow in arriving or non existant for new types of AEC objects.

Learn the Managed Code.
As for the reloading problem, get used to it.
There is no netunload command.