Jamie, a good question. I had a similar situation. While most of my current application is MM.Net, there are a few pieces that do not use MM.Net at all. In my case, I didn't feel that the cost of rewriting those working components were justified. There were a few issues initially which were primarily the result of poor design choices I made early on in the application's early history and this required some minor tweaking. Overall, there is peace and harmony with my MM.Net and non-MM.Net components.

Ciao,
Carl

>Hi All,
>
>I am trying to get up to speed on MM .Net and may have a project that I could use it on. I have played with it enough that I could probably develop the maintenance windows with MM .Net, but there will be a couple screens that are quite complex and I am not sure if my knowledge of MM .Net is enough to make it work. Plus there are some non-UI objects that I need to implement. If I can get these working in MM .Net I will need an exit stratagy. Anyways I say all this because I am wondering if you can mix non MM .Net code easily in a MM.Net application, or is it an all or nothing deal. Just having the maintenance windows alone would save me weeks of work bacause of how quick the are to set up.
>
>Any comments or suggestions would be welcome.
>
>Jamie