Stand-alones are the only type of program that run outside of the SLDWORKS.EXE process.
Are you timing the macro from the moment you click the run button or within the code (by printing the current time to the debug window)? Because if you are doing the former then your test is not accurate. VSTA macros do take longer to start load before they run, at least from the VSTA editor.
The time is taken for main code execution only - it excludes startup and shutdown times.
Time is output via msgbox. Tests are of compiled project and are not taken during debug.
I have similar issues when doing a VSTA .dll macro.
The macro is using a windows form and runs through the features and changes appearances based on criteria in the form.
I have noticed the program is running fast when the form is made modal, but very slowly when it is made modeless. Here are the times for 1 example:
Could the answer be to switch from modal to modeless and vice-versa as required? Unfortunately I haven't found a way to do this without closing the form. Any idea?