We are evaluating the benefits and sacrifices of migrating from SolidWorks Desktop to 3DExperience SolidWorks as it pertains to the API. We have a library of VBA Macros and C# (EXE) Standalones that we use to automate our work flow. One thing I learned is that 3DExperience SolidWorks cannot use Add-Ins, but I am told it can execute VBA macros.

So now the questions I have are:

1. Can 3DExperience SolidWorks be used with Standalone programs?
2. Why can 3DExperience SolidWorks not use Add-Ins, but SolidWorks Desktop can?
3. Is the macro creation/performance the same?

Does anyone have experience using 3DExperience SolidWorks that can elaborate on the 3DExperience SolidWorks use within the API, and how it differs between 3DExperience SolidWorks and SolidWorks Desktop?