SharpDevelop Community

Hi,

 I decided to post it since I receive hardly oftem following exception from #D while debugging an application. This pproblem is really annoying and mostly leads me to decide to restart IDE. I remember that similar problems already have been discoverred and as far as I remember it has already been solved.

If any further information could help then please let me know what is needed...

SharpDevelop Version : 2.1.0.2130
.NET Version         : 2.0.50727.42
OS Version           : Microsoft Windows NT 5.1.2600 Service Pack 2
Current culture      : English (United States) (en-US)
Working Set Memory   : 92048kb
GC Heap Memory       : 39986kb


Exception thrown:
System.InvalidOperationException: Invalid Content: ActiveContent must be one of the visible contents, or null if there is no visible content.
   at WeifenLuo.WinFormsUI.DockPane.set_ActiveContent(IDockContent value)
   at WeifenLuo.WinFormsUI.DockPane.ValidateActiveContent()
   at WeifenLuo.WinFormsUI.DockContentHandler.SetDockState(Boolean isHidden, DockState visibleState, DockPane oldPane)
   at WeifenLuo.WinFormsUI.DockContentHandler.set_Pane(DockPane value)
   at WeifenLuo.WinFormsUI.DockContentHandler.set_DockPanel(DockPanel value)
   at WeifenLuo.WinFormsUI.DockContent.set_DockPanel(DockPanel value)
   at ICSharpCode.SharpDevelop.Gui.SdiWorkbenchLayout.DetachViewContents(Boolean dispose)

 

TIA 

The problem with this bug is that we're unable to reproduce it. It happened a few times for me, but very rarely (once in two weeks, never inside a debugger) and I could never get enough information to find the problem.

We're going to revert to the docking library used by SD 2.0 if we cannot find the problem.

DanielGrunwald:

The problem with this bug is that we're unable to reproduce it.

 

Unfortunatelly, I also cannot easly reproduce it. Seems like the problem has been frozen temporarly...Or maybe this problem does not appear so frequently wneh SD is being debugged... 

I too run into this problem while debugging. As with everyone else, I cannot consistently reproduce it, but it happens pretty much every debugging session I have. When it does I lose all my panes with the exception of code editors. I sure hope that we can get to the bottom of this one, because it is the only real serious bone I would pick with the IDE. Everything else works very well for me, including the latest updates to the NUnit stuff.

Could you please try the latest build from the build server?

I don't know why the docking library gets in the invalid state that causes this, but yesterday I changed something that might fix that problem (or might now produce a different error message).

DanielGrunwald:

...but yesterday I changed something that might fix that problem (or might now produce a different error message).

 

Well. Actually I was trying to reproduce this and debug using latest build. So maybe that's why could not to get it - for now it works :) 

Well, I tried to reproduce the bug before doing that change but couldn't reproduce it. I get the bug maybe once every two weeks, but never if I want to reproduce it.

It has something to do with the order the docking panels got focus and maybe also with documents one has closed before. Maybe it requires working with SharpDevelop some time before it occurs; though I think I've already seen it for freshly started SharpDevelop instances.

So we'll have to wait to see if the change helps. 

DanielGrunwald:

Could you please try the latest build from the build server?

I don't know why the docking library gets in the invalid state that causes this, but yesterday I changed something that might fix that problem (or might now produce a different error message).

Will do. I have been doing that as well in the hope that it would be fixed, but have not pulled the latest build for about a week. That said, the current build server is not showing any new builds since the 5th of December. Is there somewhere else I should be getting the latest build?

Actually I take that back, the build reports are out of date, but there is a download for the build from the 11th. I am getting it now and will let you know how it goes

 
John
 

Okay, only the build reports are out of date. There is in fact a build to download (2160), so I will let you know how it goes.

Hi there,

Okay, I have been using the 2160 build for a while now with out this problem repeating itself. Not exactly scientific testing, but nonetheless so far so good. Just wanted to let you know.

 

John