Glad to help -- really other than ensuring you build them all "from the bottom up" of their dependency chain, its pretty straightforward. Some of the challenges in HORN were related to the way that these dependecies needed to be expressed/recorded for the sake of automating the process, but if you do it "by hand" it should be pretty clean (although also NOT the sort of thing you want to do manually on a repeat-basis due to the number of steps involved -- hence the need for something like HORN).
Glad you got it worked out, Steve Bohlen [email protected] http://blog.unhandled-exceptions.com http://twitter.com/sbohlen On Thu, Aug 19, 2010 at 11:14 AM, Aaron Boxer <[email protected]> wrote: > Thanks, Stephen. I had just read about the Horn project, and thought > there was some kung-fu involved > in building all three together. All sorted out now. > > On Wed, Aug 18, 2010 at 12:04 PM, Stephen Bohlen <[email protected]> > wrote: > > This is probably an issue best raised in the NHUSERS forum > > (http://groups.google.com/group/nhusers) rather than here in the dev > list, > > but can you advise what (if anything) is currently preventing you from > > building these yourself to incorporate the elements of one or another > TRUNK > > builds from one or more of these projects? As opensource projects, the > > source of each of these is available for you to checkout and build for > > yourself should there not be binaries (yet) available for download for > each > > and every pre-release version of each of these projects. > > > > You should be able to acquire the source for the projects for which you > are > > interested and subsequently recompile each of them against whatever > binary > > references you choose (assuming cross-compatibility of the APIs). > > > > HTH, > > > > Steve Bohlen > > [email protected] > > http://blog.unhandled-exceptions.com > > http://twitter.com/sbohlen > > > > > > On Wed, Aug 18, 2010 at 11:32 AM, Jorge <[email protected]> wrote: > >> > >> I would like to build all three together. This is because there is a > >> bug in the version of castle dynamic proxy distributed with nhibernate > >> 3 alpha, and this bug seems to be fixed in the latest castle core > >> code. > >> > >> The issue is: > >> > >> - Fixed DYNPROXY-ISSUE-118: Can't proxy remoting transparent interface > >> proxies. > >> > >> > >> How should I proceed here? I want to test the nh 3 alpha, but can't > >> because of this bug. > >> > >> Thanks!! > > >
