Somebody got a clue about this message:
 Operation is not valid due to the current state of the object.

regards remco

I inherit from panel and added a few controls on it such as labels and the like
a few properties and subs and thats it, nothing fancy
In an other project i got the same error when inherriting from panel

It compiles and works fine but when i enter the designer i got this error

When i click on the error on the tasklist nothing happend


Remco

Can you give some more details? What exactly are you trying to do?

I inherit from panel and added a few controls on it such as labels and the like
a few properties and subs and thats it, nothing fancy
In an other project i got the same error when inherriting from panel

It compiles and works fine but when i enter the designer i got this error

When i click on the error on the tasklist nothing happend


Remco

I figured it out

When you iherrit from a control (not usercontrol) and dropping controls on it eg a button it starts complaining in the disigner

Remco

Hi,

I'm getting this  Operation is not valid due to the current state of the object. Exception at runtime.
I'm inheriting DatagridView and I've override following methods from DataGridView class. to implement custom sorting and some special ColumnHeader painting.

OnCellPainting

OnColumnHeaderMouseClick

I've set object (from my source) as datasource for the grid. At runtime I start separate thread to read data from Database and then add objects to the datasource. on <objName>bindingsource.Add(object obj) method I get above mentioned error.
When I replaced my custom grid with DatagridView everything works fine.
P.S. I'm using .NET Framework 2.0 RTM

Thanks in advance
Sameer

Remco,

Are the complaints anything to be concerned about? Is there something I can do to prevent them? I'm assuming I'm probably doing something "wrong" in my class from the designer's perspective and that there must be something that I should surround with an if(!this.DesignMode){} block, but I'm not sure what is causing the complaint. How can I figure out what code causes the complaint?

TerriP

In my case it only complains in designtime not in runtime, so no concern about that. my (wild) gues is that the disigner don't like controls added and setting properties (initialisizecomponent) in disigntime on the control surface. notice that a control is shown as a pictogram instead of the actual control.

Remco

Hi,

I am getting this same error in Managed DirectX. I'm trying to write data to a vertex buffer but it throws a run time exception with this error. I do a similar operation with an index buffer and it works fine. Any thoughts?


Thanks,

I'm getting the exact same error for trying to write to a VertexBuffer as well! I'm trying to write more points than 3 in the buffer for the Managed DirectX 9 SDK .... Tutorial example 2, so I can have DirectX draw it as a LineList, LineStrip, or another.

How would the program 'state' know how many Vertices should be written at once?
It hadn't even gotten to the point where TriangleList was declared as the method desired. In fact, I commented out the line of code, and it still gives the error. How can a VertexBuffer only accept 3 Vertices at a time? Is this true? Anyone knowing why this error comes up, please help.

-Ambiguous User

I am getting this error while developing custom workflow using Sequential Workflow (Visual Studio 2008). Does anybody have any clue?

I got this while trying to delete a "SEALED" field from a sharepoint field collection using the sharepoint API, unsealing it first allowed me to continue.