I still remember one Micosoftie advising us to go with COM. So far COM works well with .NET I don't know in the near future. I think we need to accept the fact that in IT, what you know today maybe obsolete 6 mos. after. The same thinking as someone entering an airplane: "My one foot is already in the grave..."

>As .NET becomes more and more NET foundation class oriented, its break from the old window OS will boarden. I have not heard Microsoft address the issue of backward compatibilty regarding COM, DCOM, or anything else. At a recent announcement about the upcoming .NET 2000 operating system, many IT CIO were concerned that Microsoft did not address this issue. It may be two soon to know exactly what to do regarding the question this thread is asking. I don't know whether to jump on .NET, remain legacy, or what. Eventually I may be forced to do something even if its wrong.