What's the big secret of succeeding in developing COM module for MTS?

Since a week, we have moved our ASP framework into a Visual FoxPro COM for MTS. During the development, we have to reboot several times per day because MTS crashes when it tries to execute our module. When that happens, the MTS crash closes all of our application. This is aweful as each time I have to reopen approx. 10 applications and be back to where I was before. This is not to mention about the unsaved data of those applications. After that, we find that the COM objects are locked, so even if all seems to be ok, we have to reboot.

We never have those problems with ASP. It's seems MTS is not ready for development.

The problems does not happen in Visiaul Basic but when we call the object from a Web page. We have several various error messages. Without changing the COM, sometimes, a crash will happen. So, it's not in our code.

Any feedback is appreciated.