It is probably safe to just remove the assert for AME
On Tue, Jun 16, 2009 at 11:54 PM, Roelof Blom <[email protected]> wrote:

> So what's the fix for this?
>
>
> On Sun, Jun 7, 2009 at 11:56 PM, Ayende Rahien <[email protected]> wrote:
>
>>
>> There is probably no good reason
>>
>> On Sunday, June 7, 2009, Ken Egozi <[email protected]> wrote:
>> > Im on W7 also.
>> >
>> > Ayende - what was the benefit of only catching the AME? as this is not
>> part of the SUT anyway, and fail in ways that has nothing to do with Brail
>> (or DP2), would it be allright to simply swallow any Exception (and then it
>> will pass on any machine)?
>> >
>> > On Sun, Jun 7, 2009 at 10:17 PM, Ayende Rahien <[email protected]>
>> wrote:
>> >
>> > that is interesting, it means that they fixed the bug that this is
>> working around
>> >
>> > On Sun, Jun 7, 2009 at 8:05 AM, Ken Egozi <[email protected]> wrote:
>> > on Brail.Tests.LanguageFeatures
>> > CanHandleDynamicProxyObjects
>> >
>> > the GetProperty("Text") call does not raise the AME, so the test if
>> failing. if I manually bypass that, the view gets rendered properly (without
>> raising AME)
>> >
>> >
>> > any idea?
>> >
>> >
>> > --
>> > Ken Egozi.
>> > http://www.kenegozi.com/blog
>> > http://www.delver.com
>> > http://www.musicglue.com
>> > http://www.castleproject.org
>> > http://www.gotfriends.co.il
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > --
>> > Ken Egozi.
>> > http://www.kenegozi.com/blog
>> > http://www.delver.com
>> > http://www.musicglue.com
>> > http://www.castleproject.org
>> > http://www.gotfriends.co.il
>> >
>> >
>> > >
>> >
>>
>>
>>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to