They require special access for those downloads, if you email the sdk inbox they can hook you up

Are you calling Commit() on the solid ay any point? You will need to eliminate all commit() calls on solids from .net

you should use translate_silent

I dont know half the stuff u kno either

That's very true, however that's a limitation of the import manager not Mastercams API, The Nesting Manager can import solids fine Import Operations With Solids – myMastercam

Those operations are not supported by the api, there is also a bug with commit, the chook api is far better suited for these tasks, for most tasks involving toolpaths the nethook api is not suitable

There is not currently a way to do this without third party software AFAIK, my company provides solutions like this for a fee for customers, feel free to reach out if you are interested.

yes, you can ask the sdk team for access

Mastercam C++/CLI New Project Template VS 2022 - Visual Studio Marketplace This template contains a c# example of translating geometry using the chook api with an interop dll, which will likely mitigate your issue

Solid surfaces are store as toolpath entities the way drill points are or chains, they contain parasolid ids for the toolpath api to lookup the geometry, translating the geometry with a chook call and regenerating the operation should work, however, if the op is using the nethook API, calling .Commit() on the solid could invalidate the associated toolpath entities. Sometime calling Commit(false) solves the issue, however i would recomment using the chook api for advanced operations like unified in the older versions you could lookup the solid surfaces and other toolpath info by dumping the database

Yes you can use visual studio, the csharp project from the visual studio marketplace would be good for that

Sure viewsheets are accessible through the nethook api, I made an app a long time ago that store views heets in the toopath Manager window

That sounds right MFC is being slowly replaced with wpf in Mastercam. Wpf has a more modern look and has graphical ui elements instead of subwindows. They were talking about it in the developer Event when they covered the new managed ui.

Leaving a read me file explaining the process should be sufficient to mitigate any confusion. I'm simply stating that the way you are suggesting is mid at best, and extremely problematic at worst.

The way I proposed mitigates a lot of the issues that plague users left and right. Using common files between users is mid.