Strange Error

  • Thread starter Thread starter Tamir Khason
  • Start date Start date
T

Tamir Khason

I recieve the very strange error while compiling project:

"object reference net set to the instance of the object" in line 0 !!!
The first lines in this .cs are
using System;

using System.Collections;

using System.ComponentModel;

using System.Drawing;

using System.Data;

using System.Windows.Forms;



So what is the problem???
 
Tamir Khason said:
I recieve the very strange error while compiling project:

"object reference net set to the instance of the object" in line 0 !!!
The first lines in this .cs are
using System;

using System.Collections;

using System.ComponentModel;

using System.Drawing;

using System.Data;

using System.Windows.Forms;
Click to expand...

Hi Tamir,

You could try stepping through the code with a debugger to see where the
actual problem is. One of your references is set to null or undefined.

Joe
 
Tamir Khason said:
I recieve the very strange error while compiling
project:
"object reference net set to the instance of the
object" in line 0 !!!
Click to expand...

Can you reproduce this in a small, simple program that you could post here?

P.
 
There are no error in debugger.....
The error appears as task in the Task List and cause the same error while
adding this control to form...
The program compiles, but there are 3 lines of Object reference... Line 0 in
Task List

Any clues?
 
I tried to reproduce it - nothing. The problem is that the program (user
control) compiles, but leaves 3 tasks with "object reference...line 0" in
the task list. the error occures while adding this component to form...
 
Tamir Khason said:
I tried to reproduce it - nothing. The problem is that the program (user
control) compiles, but leaves 3 tasks with "object reference...line 0" in
the task list. the error occures while adding this component to form...
Click to expand...


Do you have the source code to the component. If so, open a second instance
of VS.NET with the debug version of the component project, select
Debug/Processes and attach to the DevEnv.exe instance that you want to add
the component to, make sure break points are set in the component source
code, and try to drop your component onto the form in the first instance of
VS.NET. If you have your breakpoint set in the right place on the second
instance of DevEnv it will stop there so you can step through your code.

Joe
 
Hi Tamir,

In your previous description, I think this error may due to the component.
I think you should follow Joe's suggestion to debug the this component to
find the cause.

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
Back
Top