You can share custom subassemblies with others by copying the required files to a package file.
Custom subassemblies that have been created using .NET or VBA can be exported and imported using a package file. A package file contains all the files necessary for the custom subassemblies to work. Once the package file is created, users can import the package file into Autodesk Civil 3D, and then copy the custom subassemblies directly into a tool palette or catalog. For more information about importing subassembly package files, see To Access and Share Subassemblies.
To create a package file, you must copy all of the files that make up the custom subassembly or subassemblies into a folder. Create a .zip file of that folder, and then change the file extension from .zip to .pkt.
If you are sharing a single subassembly, it is recommended that you name the package file the same name as the subassembly. For example, if you plan to export a subassembly named OpenChannel, name the package file OpenChannel.pkt. If you plan to export multiple subassemblies in a single package file, give the folder a name that easily identifies the types of subassemblies that are contained in it. For example, DitchSubassemblies.pkt.
The following table describes the files that must be included in a package file to successfully export and import one or more subassemblies.
| File | Description |
|---|---|
| .atc file(s) | A valid .atc file that defines the shape and behavior of the subassembly or subassemblies is required. You can have one or more .atc files included in the package file. For example, you can have one .atc file that defines one or more subassemblies, or you can have multiple .atc files, each of which defines one or more subassemblies. If the package file contains multiple .atc files, each .atc file must have a unique name. All the paths referenced in .atc file must be relative paths, if they point to files in the same .pkt file. |
| .dll or .dvb file(s) | A .dll file is required for subassemblies that are defined using .NET. A .dvb file is required for subassemblies that are defined using VBA. A package file can contain both .dll and .dvb files. |
| Help file(s) | A Help file is not required in order for a subassembly to function properly. However, the Help file is needed for others to understand how to use the subassembly. Therefore, it is recommended that you always include a Help file with each subassembly. For more information, see Creating Subassembly Help Files. |
| Image file(s) | An image file for each is displayed on the tool palette and is used to provide a conceptual graphical representation of the subassembly shape. |