This exception was caused by FoldingManager.UpdateFolding() re-using FoldingSections and adjusting their end offset.
If those FoldingSections were folded, the corresponding CollapsedLineSection was not updated for the new end position.
This inconsistency would cause visual glitches (such as fold markers not updating properly), and in some cases the InvalidOperationException during rendering.
FoldingSection now handles when its StartOffset or EndOffset is changed, and updates the CollapsedLineSection accordingly.
Do not force the use of IIS or IIS Express to debug or run a web project.
Fix IIS Express always being debugged even if Run without debugger was
selected.
http://community.sharpdevelop.net/forums/t/16643.aspx
The VB parser was using the end of the last statement as the EndLocation for the block. This made local variables
declared in that block unavailable when typing another statement at the end of the block.
We now use the location of the 'End' or 'Next' token instead.
Do not add an EntityTypeMapping element if it already exists.
Fix intermittent error were the EF data model view content
does not have a workbench window when the file is renamed
on save.
When an exception is thrown when loading a .edmx file
the EDMDesignerViewContent's Dispose method was not
handling the EDMView being null and causing the
underlying exception to be hidden.
The Add button was being enabled when the selected database
changed but on connecting to the server again the selected
database was cleared but the Add button was not disabled.
Setting two or more FxCop rules to be flagged as errors instead of
warnings was adding the rules into the CodeAnalysisRules element of
the MSBuild project file with the semi-colon separators being escaped.
This escaping then causes FxCopCmd.exe to fail.
Upgrade Ruby and Python syntax highlighting definitions to
version 2.0 so all named highlighting colours can be modified
in Tools | Options | Highlighting