So it is fixed with SP2?

On Mon, Apr 27, 2009 at 6:56 PM, Shane Courtrille <[email protected]
> wrote:

> He has SP 1 and we have SP 2.  We've modified the interface to be less
> generic.
>
> On Mon, Apr 27, 2009 at 9:50 AM, Ayende Rahien <[email protected]> wrote:
>
>> what version of the runtime are you running this on? including SP1
>> It is a long standing bug with Reflection Emit relating to generic
>> constraints that relate to one another.
>>
>>
>> On Mon, Apr 27, 2009 at 6:42 PM, Shane C <[email protected]>wrote:
>>
>>>
>>> We have a machine where this actually works fine so we're confused.
>>>
>>> On Apr 27, 9:39 am, Shane C <[email protected]> wrote:
>>> > Is this the CLR bug that was hot fixed or is there some sort of
>>> > guidance as to what we shouldn't be doing?
>>> >
>>> > On Apr 27, 9:36 am, Ayende Rahien <[email protected]> wrote:
>>> >
>>> > > It is a known issue when you have complex generic constraints.The
>>> root issue
>>> > > is a CLR bug.
>>> >
>>> > > On Mon, Apr 27, 2009 at 6:33 PM, Shane C <[email protected]>
>>> wrote:
>>> >
>>> > > > We have an interface that looks like this...
>>> >
>>> > > > public interface IKennel<T> : IKennel where T : IDog
>>> > > > {
>>> > > >  void DoSomething<TDog>(TDog dog) where TDog : IDog;
>>> > > > }
>>> >
>>> > > > This interface when mocked causes NUnit to crash.  Unfortunately
>>> NUnit
>>> > > > doesn't want to reveal the type of exception that is occuring
>>> beyond
>>> > > > the fact it's a win32 exception.  Is this a known issue or has
>>> anyone
>>> > > > seen this?
>>> >
>>> > > > I wanted to double check before creating a test case...
>>> >
>>> >
>>>
>>>
>>
>>
>>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Rhino.Mocks" 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/RhinoMocks?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to