This .NET class wraps the AcDbDxfFiler ObjectARX class. 

This abstract class provides the interface for derived classes that are used for I/O operations that work with the DXF information format. 

Specialty internal classes (that is, not exported to the API) derived from this class are used for DXF filing and for AutoLISP ADSRX function interaction with objects.

Autodesk.AutoCAD.DatabaseServices.DxfFiler

Public abstract Class DxfFiler
Inherits RXObject

public abstract class DxfFiler : RXObject;

DxfFilers are used for both file I/O and AutoLISP or ADSRX I/O. But, the DXF file format stores the X, Y, and Z coordinates of points and vectors individually, each with their own group codes (for example, group codes 10, 20, and 30 for the X, Y, and Z values of a point), whereas the AutoLISP or ADSRX entget, entmake, and entmod functionality works with a single group code and all three values (for example, group code 10 with all three point coordinates). 

This difference in storage is taken care of automatically by ObjectARX. The read and write functions in this class always take or return the complete point, vector, and so on in one operation using one DXF group code value (represented by the DxfCode enumerated type). If the filer is filing to a DXF file, then the point, vector, and so on is automatically broken into its individual X, Y, and Z components. The Y coordinate gets a DXF group code that is equal to the X coordinate's DXF group code + 10, and the Z value gets a DXF group code 10 greater than the Y coordinate's (for example, DXF group codes 10, 20, 30 or 11, 21, 31). If the filer is filing in from a DXF file, then the DxfFiler.ReadResbuf method (the filer's only input method) reads all the individual X, Y, and Z values into the resbuf's resval.rpoint array. 

When working with data of the int type, do not use the DxfFiler.WriteItem method. If you do, the call resolves to the Adesk.Boolean version of the writeItem function because that is the only one with an int argument. This results in any data value other than 0 or 1 being converted to a 1. To avoid this, either use the Adesk.Int32 data type instead of int, or explicitly call the DxfFiler.WriteInt32 method. 

When implementing an object class's dxfInFields() method (see DBObject.dxfInfields()), in the error-checking code you write to handle an unexpected value read-in, call the filer's PushbackItem() method (see DxfFiler.PushbackItem()) to rewind the filer's file pointer to the line that caused the error and then return with an appropriate ErrorStatus value. If this is not done, then the error information that AutoCAD displays to the user during a DXFIN operation shows an incorrect line number (or byte value in a binary DXF file) for the error's location. 

When objectIds are read in, they come in as ads_names. The calling application (usually the dxfInFields method of a custom object or entity class) must then convert the ads_name to an ObjectId (usually using the global function GetObjectId()). 

Clients that derive from DxfFiler must override the SetVAError() function to avoid a linker error.

DBObject