Release and Debug issues.
-
Application: I have a Windows forms application which interacts with COM components to update data in the Oracle DB. Whenever I try to update the data based on a condition it never works in the full run using the release exe. But when I try the same thing through step by step debugging of the release exe, it works fine and updates the DB. This appears quite strange and inconsistent. Can someone throw light on this?
Regards, SPanicker.
-
Application: I have a Windows forms application which interacts with COM components to update data in the Oracle DB. Whenever I try to update the data based on a condition it never works in the full run using the release exe. But when I try the same thing through step by step debugging of the release exe, it works fine and updates the DB. This appears quite strange and inconsistent. Can someone throw light on this?
Regards, SPanicker.
SPanicker* wrote:
Whenever I try to update the data based on a condition it never works in the full run using the release exe.
SPanicker* wrote:
Can someone throw light on this?
Does the information in your applications logging data suggest anything?
led mike
-
Application: I have a Windows forms application which interacts with COM components to update data in the Oracle DB. Whenever I try to update the data based on a condition it never works in the full run using the release exe. But when I try the same thing through step by step debugging of the release exe, it works fine and updates the DB. This appears quite strange and inconsistent. Can someone throw light on this?
Regards, SPanicker.
You may be running in to a case where the runtime is being too agressive and running a GC too soon. How are you acessing the COM components? If you're doing this in a managed wrapper, it should implement IDisposable and include calls to GC.KeepAlive() in the appropriate functions.
Scott Dorman
Microsoft® MVP - Visual C# | MCPD President - Tampa Bay IASA [Blog][Articles][Forum Guidelines]
Hey, hey, hey. Don't be mean. We don't have to be mean because, remember, no matter where you go, there you are. - Buckaroo Banzai
-
You may be running in to a case where the runtime is being too agressive and running a GC too soon. How are you acessing the COM components? If you're doing this in a managed wrapper, it should implement IDisposable and include calls to GC.KeepAlive() in the appropriate functions.
Scott Dorman
Microsoft® MVP - Visual C# | MCPD President - Tampa Bay IASA [Blog][Articles][Forum Guidelines]
Hey, hey, hey. Don't be mean. We don't have to be mean because, remember, no matter where you go, there you are. - Buckaroo Banzai