Any idea when new version (> 1.3.0.717) of NuGet package for FNH will be released
50 views
Skip to first unread message
Cole W
Jan 24, 2012, 10:39:43 AM1/24/12
to Fluent NHibernate
There are a few updates that have been made after the NuGet package
version 1.3.0.717 was released that I'd like to have but I was just
wondering if a new package was in the works or when it might be
available. I could compile it from source but I'd rather not use a
3rd party assembly outside of NuGet at this point. Thanks in advance.
version 1.3.0.717 was released that I'd like to have but I was just
wondering if a new package was in the works or when it might be
available. I could compile it from source but I'd rather not use a
3rd party assembly outside of NuGet at this point. Thanks in advance.
tbushell
Jan 25, 2012, 1:09:47 PM1/25/12
to Fluent NHibernate
I'd like to know that too, and also - what's going on with the FNH
project in general?
There's been very little activity on GitHub recently, and it seems
there's a lot less response to questions from "the community" then -
say - a year ago.
Don't mean to be alarmist, but I'm starting to worry that this
terrific project may be dying.
-Tom Bushell
project in general?
There's been very little activity on GitHub recently, and it seems
there's a lot less response to questions from "the community" then -
say - a year ago.
Don't mean to be alarmist, but I'm starting to worry that this
terrific project may be dying.
-Tom Bushell
Joe Brockhaus
Jan 25, 2012, 3:23:30 PM1/25/12
to fluent-n...@googlegroups.com
i've wondered as well. I've been putting off upgrading my NH core and FNH specifically for these reasons, despite having to come up with annoying workarounds for issues fixed in later builds.
and like you said it's been a process that has slowly congealed over the course of ~year.
now that NH itself has code-first/fluent configuration ability .. are there really features & functionality FNH offers that the NH core doesn't?
--
You received this message because you are subscribed to the Google Groups "Fluent NHibernate" group.
To post to this group, send email to fluent-n...@googlegroups.com.
To unsubscribe from this group, send email to fluent-nhibern...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/fluent-nhibernate?hl=en.
Sebastien Lambla
Jan 26, 2012, 8:03:16 AM1/26/12
to fluent-n...@googlegroups.com
Well if one wanted, one could preserve the FNH syntax and rebuild it on top of the existing metamodels.
I personally do not like the NH fluent mappings at all, and would rather use FNH.
But I have no development time to allocate to FNH, and if it dies off I can't do much about it. Anyone that has time would be well advised to send pull requests though :)
Seb
From: fluent-n...@googlegroups.com [fluent-n...@googlegroups.com] on behalf of Joe Brockhaus [joe.br...@gmail.com]
Sent: 25 January 2012 20:23
To: fluent-n...@googlegroups.com
Subject: Re: [fluent-nhib] Re: Any idea when new version (> 1.3.0.717) of NuGet package for FNH will be released
Sent: 25 January 2012 20:23
To: fluent-n...@googlegroups.com
Subject: Re: [fluent-nhib] Re: Any idea when new version (> 1.3.0.717) of NuGet package for FNH will be released
tbushell
Jan 26, 2012, 3:23:34 PM1/26/12
to Fluent NHibernate
On Jan 25, 3:23 pm, Joe Brockhaus <joe.brockh...@gmail.com> wrote:
> i've wondered as well. I've been putting off upgrading my NH core and FNH
> specifically for these reasons, despite having to come up with annoying
> workarounds for issues fixed in later builds.
2.1.2 to FNH 1.3 / NH 3.2.
It was a disaster - multiple undocumented breaking changes in NH, and
at least one bug in FNH I had to fix (submitted to GitHub - issue
#113). Posted questions here and to Stack Overflow - got almost zero
response.
Finally gave up in disgust and reverted to the old versions.
> now that NH itself has code-first/fluent configuration ability .. are there
> really features & functionality FNH offers that the NH core doesn't?
open source or commercial - that does anything remotely equivalent.
I don't use FNH code-first myself, but most of the people who do say
that the FNH approach is much better.
-Tom Bushell
tbushell
Jan 26, 2012, 3:37:37 PM1/26/12
to Fluent NHibernate
> I personally do not like the NH fluent mappings at all, and would rather use FNH.
since I only use Automapping.
> But I have no development time to allocate to FNH, and if it dies off I can't do much about it.
and some minor improvements to the wiki documentation.
Anyone heard from James Gregory recently, since his last post here in
November 2011?
-Tom Bushell
Joe Brockhaus
Jan 26, 2012, 4:15:46 PM1/26/12
to fluent-n...@googlegroups.com
>> That seems to be the consensus in the FNH community. I can't comment,
>> since I only use Automapping.
>> since I only use Automapping.
hah, funny how things work: I tried automappings at first because it seemed
like it should 'just work' .. 'just working', though, requires much extra side-work.
so i just opted to KISS and do explicit mappings.
i guess you could say i don't know what i'm missing =)
>> Anyone heard from James Gregory recently, since his last post here in
>> November 2011? nope, nothing since his holiday or maybe just briefly after his supposed return.
it seems post approval was removed .. perhaps that's an indication of something?
James Gregory
Jan 27, 2012, 5:20:32 AM1/27/12
to fluent-n...@googlegroups.com
Sorry everyone for my absence. I've been largely neglecting FNH lately primarily because I'm in the middle of a big life change; aka, I've moved to the other side of the world, changed jobs, and everything else that comes with that.
I'll try to put together some kind of official statement, but it boils down to this:
Is FNH dead? No.
Is FNH neglected? Yes.
Will it remain so? Perhaps.
I don't have the time or desire right now to run the project at the pace I have been doing for the past few years, but I also have no desire to let the hard work of myself and others fall apart. Everything is still crazy right now, but once I get settled again I do intend to pick things up.
Joe Brockhaus
Jan 27, 2012, 9:49:44 AM1/27/12
to fluent-n...@googlegroups.com
I, for one, am a bit jealous of the move to Australia. You and your summers in my winters! ;-)
the absence is understandable
--
You received this message because you are subscribed to the Google Groups "Fluent NHibernate" group.
To view this discussion on the web visit https://groups.google.com/d/msg/fluent-nhibernate/-/lUIOcEdvCq4J.
tbushell
Jan 27, 2012, 2:56:08 PM1/27/12
to Fluent NHibernate
James,
Thanks for checking in, and congrats on your move to Oz. I've always
wanted to visit there, and would be very interested to hear your
impressions once you've settled in.
> I'll try to put together some kind of official statement,
That's probably a good idea, and might keep people from abandoning FNH
because of perceived lack of support and improvements.
> I don't have the time or desire right now to run the project at the pace I
> have been doing for the past few years, but I also have no desire to let
> the hard work of myself and others fall apart. Everything is still crazy
> right now, but once I get settled again I do intend to pick things up.
Very glad to hear that!
Perhaps we as a group could take some of the load off you, and keep
things moving forward.
Speaking for myself, I've only fixed one bug (#113), and really don't
understand the codebase. But I could probably help with things like
documentation, testing, etc.
Is there anything else you could suggest?
-Tom Bushell
Thanks for checking in, and congrats on your move to Oz. I've always
wanted to visit there, and would be very interested to hear your
impressions once you've settled in.
> I'll try to put together some kind of official statement,
because of perceived lack of support and improvements.
> I don't have the time or desire right now to run the project at the pace I
> have been doing for the past few years, but I also have no desire to let
> the hard work of myself and others fall apart. Everything is still crazy
> right now, but once I get settled again I do intend to pick things up.
Perhaps we as a group could take some of the load off you, and keep
things moving forward.
Speaking for myself, I've only fixed one bug (#113), and really don't
understand the codebase. But I could probably help with things like
documentation, testing, etc.
Is there anything else you could suggest?
-Tom Bushell
tbushell
Jan 27, 2012, 3:17:58 PM1/27/12
to Fluent NHibernate
> hah, funny how things work: I tried automappings at first because it seemed
> like it should 'just work' .. 'just working', though, requires much extra
> side-work.
In my experience (limited to a single greenfield project, admittedly),
everything mostly _does_ "just work"!
The only extra side-work I had to do was a couple of overrides to work
around some bugs in FNH, which were quickly fixed in the next
release. And this was for a reasonably complicated object model, with
multiple levels of inheritance, multiple nested lists of other
objects, etc.
I've always wondered why more people don't use it - mapping with code
looks like a lot more work.
-Tom
Desmond Diong
Jan 29, 2012, 7:54:13 AM1/29/12
to fluent-n...@googlegroups.com
"multiple levels of inheritance"
I have spent quite a days trying to map that with table-per-hierarchy
and finally gave up on it at the moment. Would be interesting to know
how you tackle that.
tbushell
Jan 30, 2012, 12:44:22 PM1/30/12
to Fluent NHibernate
Desmond,
I've always used the default "table-per-subclass" strategy, which
worked perfectly for me in version 1.0. I just used pure Automapping
- did not need to do *any* additional work to handle inheritance. I
can't speak for table-per-hierarchy - sorry.
However, there seems to be a problem with later versions - at least
with my object model.
Some deeply derived classes (i.e. 3 or 4 levels of inheritance) were
not being Automapped properly. I eventually found a bug (reported as
issue #113), and submitted a fix, but I don't believe this has been
integrated into the main branch yet. Only one function changed, so it
would be fairly easy for you to get the source and apply the fix
yourself.
If this does not help, suggest you post a question here and to Stack
Overflow, with sample code and detailed description of what happens.
-Tom
On Jan 29, 7:54 am, Desmond Diong <ysdi...@gmail.com> wrote:
> "multiple levels of inheritance"
>
> I have spent quite a days trying to map that with table-per-hierarchy
> and finally gave up on it at the moment. Would be interesting to know
> how you tackle that.
>
I've always used the default "table-per-subclass" strategy, which
worked perfectly for me in version 1.0. I just used pure Automapping
- did not need to do *any* additional work to handle inheritance. I
can't speak for table-per-hierarchy - sorry.
However, there seems to be a problem with later versions - at least
with my object model.
Some deeply derived classes (i.e. 3 or 4 levels of inheritance) were
not being Automapped properly. I eventually found a bug (reported as
issue #113), and submitted a fix, but I don't believe this has been
integrated into the main branch yet. Only one function changed, so it
would be fairly easy for you to get the source and apply the fix
yourself.
If this does not help, suggest you post a question here and to Stack
Overflow, with sample code and detailed description of what happens.
-Tom
On Jan 29, 7:54 am, Desmond Diong <ysdi...@gmail.com> wrote:
> "multiple levels of inheritance"
>
> I have spent quite a days trying to map that with table-per-hierarchy
> and finally gave up on it at the moment. Would be interesting to know
> how you tackle that.
>
Reply all
Reply to author
Forward
0 new messages