Ayende @ Rahien

Oren Eini aka Ayende Rahien CEO of Hibernating Rhinos LTD, which develops RavenDB, a NoSQL Open Source Document Database.

You can reach me by:


+972 52-548-6969

Posts: 6,968 | Comments: 49,577

filter by tags archive
time to read 2 min | 255 words

This and this bugs are really pissing me off. Both those bugs are related to the same source, and one of them was originally a Rhino Mocks issue. They both  stems from the CLR runtime bugs.  Basically, trying to inherit from a generic interface with generic method parameters that has constraints causes the runtime to puke with a TypeLoadException.

I am not one to cry that select() is broken, but in this case, it most certainly is. It is verified using both the C# compiler and Reflection.Emit, so it is definitely a runtime bug.

The really annoying parts that they were acknowledged and verified as bugs by Microsoft, and then closed By Design.  No communication whatsoever about the reasoning for that, just the customary "By Design" response that I have seen all too often in the past.

I personally have had to track down the root cause when it was first submitted to me as a Rhino Mocks bug. If this is a By Design bug, then either the design is broken, or we deserve a lot more information about this, because no way your turn this, it should be legal to do this.

As you can probably tell, I am very angry about this, not the least because I spent many hours with it before admitting that it was a runtime bug that I had no way around. I am pretty sure that some of the bugs in connect are resolved to their reporters satisfactions, I just have to meet such a thing.

time to read 1 min | 70 words

I am going to print a response I just got from Microsoft Connect here, and let you do the judgement yourself:

Very sorry for not getting back to you on your last comment till now.  Unfortauntely the Connect system just tracks fixes for our next product releases.  To get fixes for shipped products you'll need to contact Microsoft Support at http://support.microsoft.com/oas/default.aspx?ln=en-us&prid=9511&gprid=344272.

This probably explains this better.


No future posts left, oh my!


  1. Production postmortem (28):
    21 Feb 2020 - The self signed certificate that couldn’t
  2. RavenDB 5.0 (2):
    21 Jan 2020 - Exploring Time Series–Part II
  3. Webinar (2):
    15 Jan 2020 - RavenDB’s unique features
  4. Challenges (2):
    03 Jan 2020 - Spot the bug in the stream–answer
  5. Challenge (55):
    02 Jan 2020 - Spot the bug in the stream
View all series


Main feed Feed Stats
Comments feed   Comments Feed Stats