Hello to all,

From what I understand, stand alone SW routines will run slower because they are run "out-of-process" vs a SWP macro which runs

"in-process." Ok, fine. But, what about a VSTA vb.net macro?

Since the compiled VSTA .dll is loaded within SolidWorks, is it running "in-process"?

I did a quick test to get some numbers...

The tests were run on an assembly containing 64 components and a total of 2575 bodies.

The routine goes through each Component in the assembly and gets the list of Bodies. The name of the Feature associated with each body is stored to a variable.

Time to complete:
VSTA = 6.5s

SWP = 0.09s

VB.NET stand-alone Form = 2.7s (with commandinprogress=true)

VB.NET stand-alone Form = 107s (witout commandinprogress=true)

Add-in would be around the same time as the SWP.

So why is the VSTA so slow? Slower than a stand-alone in fact.

Thoughts?