I'm trying to track down an issue I'm having when converting a WinForms app from 32-bit to 64-bit. Basically what happens after the conversion is that when I run the main operation in the product, the application's process proceeds to consume all available memory and CPU for some time, then finally fails to return a result. The app itself is composed of two separate solutions--the main WinForms app as well as a dependent DLL that does the main body of work. It's in the latter that I think the problem lies but I'm not quite sure. I've explicitly set the architecture in VS.Net (2010) to x64 for all project and re-complied all but still get this behavior. I will note that the main Winforms app references one COM object (provided by Microsoft) and both solutions reference another Microsoft provided .Net assembly. I haven't quite been able to figure out the magic to get this to work on x64 and would welcome any pointers in the right direction.
Darren
Darren Mar-Elia MS-MVP, Group Policy
www.gpoguy.com
www.sdmsoftware.com - "The Group Policy Experts"
