[quote user="dgn2dwg"]An addin has already been developed[/quote]
"Terminology note": I think if your code start MicroStation, it should not be mentioned as addin. My feeling is MicroStation addin is a code derived from Bentley.MicroStation.AddIn class, that requires to start MicroStation upfront. Your code is an external application (process) that starts and drives MicroStation. It's not a big difference in general, but important in some detail issues.
[quote user="dgn2dwg"]I think some measure has to be done to wait for the command to finish before Microstation quiting[/quote]
As I mentioned in a different post, I think (but I am curious if somebody else will provide further information :-) the correct way is to wait until MicroStation enters idle mode with EnterIdle event.
[quote user="dgn2dwg"]it seems the Application.IsProcessLocked[/quote]
I have never created external application driving MicroStation from outside and I prefer to create real addins, so I heard about this property for the first time. From what is mentioned in VBA help file, it seems it exists because of timing out purposes, not to tell the application MicroStation processed all tasks in input queue. But may be it's some side effect?
Regards,
Jan