That works. Thanks Mick!

Am I calling GetOpGroupDataInExternalFile correctly? Mastercam.Support.Types.ExternalOpsFileData[] opData = null; Mastercam.Support.Types.ExternalGroupsFileData[] groupData = null; bool success = SearchManager.GetOpGroupDataInExternalFile(@"C:\Users\Samuel Hanson\Documents\my mcamx9\mcx\Components\rect.mcx-9", ref groupData, ref opData); It always returns false.

Excellent. This concept will do the trick.

That sounds promising. Are you aware of a way to reference the merged geometry? Perhaps the workflow would require components to be created on a specific, reserved layer. Thanks for your help.

Can the NET-Hook API import geometry from another .mcx- file? Similar to the File Merge/Pattern in Mastercam, but programmatic and also importing operations. The goal is to import from a library of geometry+operation components and place them within the current file. The only method I see using the API is FileManager.Open("Component.mcx-9"); to open a file then read the data I want into memory, reopen the initial file, and add the items to database. This has drawbacks (I assume it resets the undo stack, for one) and is not sufficient. An alternate solution is to store component data in a file format I can parse myself. Then read it and create the geometry and operations accordingly. If possible, though, I would prefer to use the API and mcx files. Currently using C#, developing for Mastercam 9.