Hunting memory leaks
-
I'm not sure if I'm posting this on the right board, but I'll give it a shot. 13 years ago we developed an expert system using VB6. It comprised of a standalone MDI-interface with a whole bunch of COM+ components. As time advanced, our software needed an overhaul. The decision was made to move to .Net (C#) module by module. As we implemented the MDI in C# (.NET3.5), we started to see a memory leak when we replaced the old VB6-MDI. The .net MDI starts the existing COM+ components the same way as the old MDI did. The old application did not have memory leaks, so it must have started with the .net transition. Now my question is, is there a way to hunt down that memory leak? What is the best tool to use and can that cool work with .net and com+ at the same time? Thank in advance!
The consumer isn't a moron; she is your wife.
-
I'm not sure if I'm posting this on the right board, but I'll give it a shot. 13 years ago we developed an expert system using VB6. It comprised of a standalone MDI-interface with a whole bunch of COM+ components. As time advanced, our software needed an overhaul. The decision was made to move to .Net (C#) module by module. As we implemented the MDI in C# (.NET3.5), we started to see a memory leak when we replaced the old VB6-MDI. The .net MDI starts the existing COM+ components the same way as the old MDI did. The old application did not have memory leaks, so it must have started with the .net transition. Now my question is, is there a way to hunt down that memory leak? What is the best tool to use and can that cool work with .net and com+ at the same time? Thank in advance!
The consumer isn't a moron; she is your wife.