We are in the process of porting a series of applications from VB6 to managed code. Our programs automate via COM a third party application. In order to minimize the impact of this effort we are porting small portions or components one at a time, so for a period we will be living with Interop.

An example, we now have a managed object that is called from the VB6 app, interacts with objects both COM based and .NET based that were instantiated and controlled by the parent VB6 app. Amazingly this approach has worked fine so far. Carefully following the guidelines and walkthroughs we have been able to get everything to play well together.

My question, and the advice I am seeking is, what issues should we look for that we may not have run into yet, especially in terms of memory leaks etc. We have not noticed any decrease in overall application stability and performance, other than a slightly longer "cold" start to the application. Presumably the overhead of initializing both the VB6 runtimes and the CLR. We have also not noticed any significant resource leaks. But I am wary and know we have to live in this mode for an extended period of time as we port our applications and bring our staff up to speed with .NET so I thought I would solicit any advise I could from this group.

The app is Winforms based for now, and heavily database oriented. We are looking at creating an ASP version and possibly a PocketPC version as well in the future, once the port is completed.

Thanks in advance for your time.

Cheers,

Robert Porter