It definitely sounds like the bug :) Unfortunately, I don't think there is a fix for .NET 3.5 (CLR 2.0). In the Connect issue, Microsoft said, "it will be fixed in the next major version of the CLR" - which, I think, would be .NET 4.0. I've never tried to reproduce the issue with .NET 4, but I think chances are good that upgrading would fix the issue.
The only workaround I know of is to avoid using the debugger in scenarios where the bug would be triggered. Fabian On Tue, Jul 17, 2012 at 1:43 PM, srudin <[email protected]> wrote: > Hi Fabian > > From the description I would say it sounds exactly like what I'm > experiencing - we're using .Net 3.5 with VS2010 but if I'm right this is > using .Net 2.0 as runtime which would be 2.0.50727.5456 (this would explain > why this five year old case is still active). > > Does that sound like it? Is there a fix? Will it be gone when I change to > .Net 4.0? > > Kind regards > Sandro > > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Development List" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/castle-project-devel/-/IqcwLju1OJoJ. > > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/castle-project-devel?hl=en. -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
