Windsor deadlock in ASP.NET (IOC-370)

47 views
Skip to first unread message

Vladimir Okhotnikov

unread,
Jan 10, 2013, 6:25:06 AM1/10/13
to castle-pro...@googlegroups.com
Hi

after recent upgrade to Windsor 3.1 and new NHibernate, we hit the same
issue as described in

http://issues.castleproject.org/issue/IOC-370
and
https://github.com/castleproject/Windsor/issues/17

In the latter, Krzysztof commented that it was fixed in 3.2 2 days ago.
I assume 3.2 means trunk, but cannot find any relevant commits in
https://github.com/castleproject/Windsor (the last one is 21 days ago).

Krzysztof, could you confirm that the fix is in the github repo and if
not, could you somehow share it with us? We hit that bug in production,
and it's obviously quite a pressing matter for us.

Thanks in advance,
Vladimir Okhotnikov

Krzysztof Kozmic

unread,
Jan 10, 2013, 6:45:45 AM1/10/13
to castle-pro...@googlegroups.com
I hadn't pushed it as I was still working on something.

Anyway, I just did push it, so if you can't wait you can use it now.

Or you can wait until I find time to make a proper release. I don't plan any more changes before v3.2, I just need time (and motivation) to make the release.


-- 
Krzysztof Kozmic

--
You received this message because you are subscribed to the Google Groups "Castle Project Users" group.
To post to this group, send email to castle-pro...@googlegroups.com.
To unsubscribe from this group, send email to castle-project-u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en.

Vladimir Okhotnikov

unread,
Jan 10, 2013, 6:50:32 AM1/10/13
to castle-pro...@googlegroups.com
Many thanks, Krzysztof, you are fantastic.

Regards,
Vladimir Okhotnikov
Reply all
Reply to author
Forward
0 new messages