And it is easy because with the lightweight Bytecode we don't need to be in
sync with neither LinFu nor Castle.Core nor Spring.

The problem with Antlr3 and re-linq is another.

On Tue, Dec 7, 2010 at 2:41 PM, Richard Birkby <[email protected]> wrote:

> The same sort of arguments apply to NHibernate too. The recommended
> advice for much of the last year for the NH.LinFu provider was to
> build it yourself rather than use the binary  release.
>
> Richard
>
> On 7 Dec 2010, at 17:37, Patrick Earl <[email protected]> wrote:
>
> > While I don't want to aggravate this heated argument, it is a bit odd
> that re-linq has releases that aren't actually the intended releases.  Is
> every single build a valid release?  If not, how are external users to know
> which code is stable and ready for external consumption?
> >
> >         Patrick Earl
>



-- 
Fabio Maulo

Reply via email to