Purging registered application names in the current AutoCAD drawing using .NET

Purging can seriously reduce the size of AutoCAD drawings by removing unnecessary symbol table and dictionary entries. The PURGE command in AutoCAD allows you to safely purge these non-graphical objects (layers, linetypes, block definitions, etc.).

Since AutoCAD 2005 (if I recall correctly), PURGE also supports the removal of Registered Application names. Applications that make use of Extended Entity Data (XData) must register unique application names in drawings. A few applications have, in the past, created many more names than they required, and as these RegApp names get copied from drawing to drawing (when they get XRefed, for instance), they ended spreading from DWG file to DWG file (one comparison I remember hearing was to a virus, although that was perhaps a little extreme). To the best of my knowledge the applications that mistakenly caused this problem have now been fixed (and shall remain nameless), but there are still drawings out there with a lot of these records, which is ultimately why we extended PURGE to address the problem from within AutoCAD.

Anyway, I've chosen to implement a command to purge these RegApp names - even though it's now there in the product - really just an example of how to code this type of functionality. It could very easily be extended to handle the specific data you feel needs purging in your company's (or customers') DWG files.

The Database.Purge() function available in .NET wraps AcDbDatabase::purge(). These functions are both misleadingly named, as neither of them actually performs a purge on the database. What they do - and this is actually more useful, as it gives you more control - is filter a list of object IDs you pass in, removing any that cannot safely be purged by your application. So they would more accurately be named TellMeWhatCanSafelyBePurged(), or something like that. Typically objects get removed from the list because a reference exists somewhere in the drawing to that object - such as from an entity to a layer (making the layer dangerous to purge). The code calling the Purge function will usually then erase the objects that have been returned. And that's how the PURGE command is implemented.

Here's some C# code that purges the Registered Application names in the current document:

using Autodesk.AutoCAD.ApplicationServices;

using Autodesk.AutoCAD.DatabaseServices;

using Autodesk.AutoCAD.EditorInput;

using Autodesk.AutoCAD.Runtime;

using System.IO;

using System;

namespace Purger

{

  public class Commands

  {

    [CommandMethod("PC")]

    public void PurgeCurrentDocument()

    {

      Document doc =

        Application.DocumentManager.MdiActiveDocument;

      Database db = doc.Database;

      Editor ed = doc.Editor;

      int count =

        PurgeDatabase(db);

      ed.WriteMessage(

        "\nPurged {0} object{1} from " +

        "the current database.",

        count,

        count == 1 ? "" : "s"

      );

    }

    private static int PurgeDatabase(Database db)

    {

      int idCount = 0;

      Transaction tr =

        db.TransactionManager.StartTransaction();

      using (tr)

      {

        // Create the list of objects to "purge"

        ObjectIdCollection idsToPurge =

          new ObjectIdCollection();

        // Add all the Registered Application names

        RegAppTable rat =

          (RegAppTable)tr.GetObject(

            db.RegAppTableId,

            OpenMode.ForRead

        );

        foreach (ObjectId raId in rat)

        {

          if (raId.IsValid)

          {

            idsToPurge.Add(raId);

          }

        }

        // Call the Purge function to filter the list

        db.Purge(idsToPurge);

        Document doc =

          Application.DocumentManager.MdiActiveDocument;

        Editor ed = doc.Editor;

        ed.WriteMessage(

          "\nRegistered applications being purged: "

        );

        // Erase each of the objects we've been

        // allowed to

        foreach (ObjectId id in idsToPurge)

        {

          DBObject obj =

            tr.GetObject(id, OpenMode.ForWrite);

          // Let's just add to me "debug" code

          // to list the registered applications

          // we're erasing

          RegAppTableRecord ratr =

            obj as RegAppTableRecord;

          if (ratr != null)

          {

            ed.WriteMessage(

              "\"{0}\" ",

              ratr.Name

            );

          }

          obj.Erase();

        }

        // Return the number of objects erased

        // (i.e. purged)

        idCount = idsToPurge.Count;

        tr.Commit();

      }

      return idCount;

    }

  }

}

Here's what happens when you run the PC command:

Command: PC

Registered applications being purged: "AcadAnnoPO" "PE_URL" "AcadAnnoAV"

"ACAD_EXEMPT_FROM_CAD_STANDARDS"

Purged 4 objects from the current database.

In the next post we'll look at extending this to - once again - work on a folder of drawings.

Comments

[James Maeding]

Hey, thanks for hitting this subject Kean! If there is any chance you could comment on the possibility/difficulty of stopping reg apps in xrefs from "sticking" in drawings they are xreffed to, that would be appreciated. No worries if you cannot get to it, you already did a huge favor by these posts!

[Kean]

Hi James,

I can see a few ways to go about this:

• Respond to events telling you when an xref is created - from here you can fire off the PC command to purge the current drawing (probably using SendStringToExecute()):
• the Editor.CommandEnded event for the XATTACH command
• the Database.ObjectAppended event for a block reference corresponding to an xref
• As a matter of course run the PC command (or the code it uses) just before a drawing is saved:
• redefine the QSAVE and SAVE commands to call PC first
• use the Database.BeginSave event (assuming that's not too late - this would need testing) to run the code from there

I'm sure there are options I've missed, but these are some of the different ways you might investigate automating this activity.

Cheers,

Kean

[anonymous]

Hi Kean,

Could you please explain how we can redefine QSAVE?

Thanks
ss

[Kean]

You undefine it with the UNDEFINE command, and implement your own command of that name.

Kean

[tArun]

How to get the VBA macro attached with a drawing?

[Kean]

This isn't a VBA macro, so currently can't be attached with a drawing.

Kean

[tArun cHatterjee]

is there any api module available in Realdwg to detect VBA macro attached with a drawing..
i tried Dictionary entry of "ACAD_VBA" which returns VBA manager object..... but how to type cast it?

DBDictionary dic = tr.GetObject((ObjectId)nod.GetAt("ACAD_VBA"), OpenMode.ForRead) as DBDictionary;

foreach (DictionaryEntry entry in dic)
{

object a = tr.GetObject((ObjectId)entry.Value, OpenMode.ForRead);
}

[Kean]

tArun -

This is a question for the ADN team, if you're a member.

Regards,

Kean