Recently spotted an article on web talking about ‘effectively’ utilizing the .NET power in AutoCAD .NET, Maximize the .NET in AutoCAD® .NET.
It says something about loading and unloading AutoCAD .NET assemblies using AppDomains.
“While we are on the subject of having a separate loader (as discussed in the attributes section above) for your real .NET application, the .NET architecture offers a number of other advantages if you do plan to implement a separate loader application for your real .NET application. This loader would be responsible for loading and unloading your .NET application dynamically in AutoCAD (apart from serving as a parser for the custom attributes). All this can be achieved using the .NET concept called AppDomains.”
Not sure whether the guy really created such a loader himself and posted it somewhere or provided through any means to benefit the AutoCAD .NET development community, but we did not see it anyway. Or he just tried hard to present some huge, fancy, but hollow concepts and ideas.
In fact, with the leading edge AutoCAD .NET Addin Wizard (AcadNetAddinWizard) on hand, we do not really have to worry about AutoCAD .NET assembly loading and unloading anymore. Apart from providing features as launching the right version and flavor of AutoCAD automatically from inside the Visual Studio debugger and loading the resultant debug version .NET assembly created by the current project automatically, it also provides some more wonderful features such as opening a test drawing and running a test command defined in the .NET assembly (thus the current .NET Visual Studio project) right after the drawing is being opened. All these can be done in a moment only by pressing the F5 button. It provides far more, such as various project wizards, item wizards, coders and widgets, as introduced in early posts.
Recent Comments