Object reference not set to an instance of an object

Navigation
3

I know the question is a little subjective, but maybe someone has already gone through it and can help me.

I have an application developed in C # / Windows Forms / ADO.NET with firebird database.

The "Object reference not set to an instance of an object" error was being intermittently displayed on some system features. I noticed that these features are linked to some database transaction (insert / update / delete).

When trying to debug through a development server the application did not display the error. Not knowing what to do, I simply restarted IIS and the application stabilized. Has anyone ever experienced this?

Note: I read in a Microsoft article ( link ) that ADO.NET was not fully tested in the .NET Framework environment and may cause intermittent problems. I thought it might be related to this.

    
asked by anonymous 16.03.2016 / 15:24

2 answers

1

The above mentioned link addresses intermittent errors in ADO and ADO MD. These problems occur because technology compatible with the .NET Framework is ADO.NET technology.

The text highlights: "Caution ADO and ADO MD have not been fully tested in a Microsoft .NET Framework environment" and complements with a temporary workaround until the full migration from ADO to ADO.NET.

    
19.05.2016 / 20:13
1

I found that in several project methods, instances of the FBCommand and FbDataReader object were not using the dispose method. After implementing this method the application stabilized.

    
02.06.2016 / 15:49
Moodle - How to unmount the blocks Contact form 7 in custom post