Correction: our bad :)
I might not do much work on FNH these days but I do try to stay on top of
the mailing list moderation.
On Sun, May 1, 2011 at 1:57 AM, James Gregory wrote:
> I obviously messed up on this one and let a few more emails pile up than I
> should've. My bad.
>
> --
> You receiv
Yeah, I can guess that (would feel bad if I were, LOL).
I need the example the way it is as it needs to be as close to Jose's
EF/confORM examples as pssoible, as the main idea of creating mine was
porting his confORM one to FNH.
That's why will keep it the way it is for now and update it once nat
For what it's worth, you're not the only one who's requested native ISet
support either.
--
You received this message because you are subscribed to the Google Groups
"Fluent NHibernate" group.
To post to this group, send email to fluent-nhibernate@googlegroups.com.
To unsubscribe from this grou
If you were happy to use Iesi, then it would all work fine ;)
But yeah, it's about time we supported the native .Net 4 collections. I'll
get a fix out soon.
--
You received this message because you are subscribed to the Google Groups
"Fluent NHibernate" group.
To post to this group, send email
Thank you very much for your information. I'm glad that such a good
project get further development. Keep doing this good work.
--
You received this message because you are subscribed to the Google Groups
"Fluent NHibernate" group.
To post to this group, send email to fluent-nhibernate@googlegro
hmm.. It's OK. I guess I'll keep the example the way it is for now.
Glad to know you'll handle it soon anyway.
Thanks a lot, James, you rock :)
Regards,
*Mohamed Meligy
*Readify | Senior Developer
M:+61 451 835006 | W: readify.net
[image: Description: Description: Description: Description:
rs
Ugh, that's not good. Sorry Mohamed, but it doesn't look like there's going
to be an easy way to get this to work without using Iesi.Collections. I'll
get a fix out ASAP to get it working with the native .Net 4 collection
types, no hackery required.
--
You received this message because you are
Thanks for the pointers from James Gregory here. I have resolved this
be using a different approach to ignoring members:
using System.Reflection;
using FluentNHibernate;
using FluentNHibernate.Automapping;
using FluentNHibernate.Cfg;
namespace FNHProblem
{
class Program
{
static v
OK, then I did replace all ISet<> with HashSet<>. Also, commented the
collection factory line.
The configuration passes, on save, I get the following error:
{"Unable to cast object of type
'NHibernate.Collection.Generic.PersistentGenericSet`1[FluentNHSampleApp.Domain.Customization]'
to type
'Syst
CollectionTypeResolver definitely looks like the place we should be
changing, and ideally adding a callout to something configurable.
Your second example isn't anything to worry about, that's a part of the
PersistenceSpecification stuff (a testing tool for mappings). It's not
actually used to g
1. It's latest NuGet package. Not sure how outdated / recent this would be.
3. These are the places I thought might be relevant in FNH src 1.x branch
sounded like latest modified):
a. fluent-nhibernate\src\FluentNHibernate\Mapping\CollectionTypeResolver.cs
line: 25-33:
static bool IsSet(
Like I said, FNH is not dead. There's no "more or less" about it, there will
be a NH3.2 compatible release when it's done. Simple as that. No need to
worry.
--
You received this message because you are subscribed to the Google Groups
"Fluent NHibernate" group.
To post to this group, send email
Sorry, but my intention was not working NOW with a non-GA release. My
intention is to get know if this project will be exists for further NH
GA Releases or not!!! Not more or less! I like FNH and I like it how
easy it makes my life working with NH. Keep this!
--
You received this message because
Automapping is really going to struggle to make sense of your DisplayTitle
property. As it's a getter only, it'll try to find a backing field that
matches; off the top of my head, I don't know what it'll do if it doesn't
find one.
The Access.ReadOnlyProperty() method looks suspiciously broken.
I obviously messed up on this one and let a few more emails pile up than I
should've. My bad.
--
You received this message because you are subscribed to the Google Groups
"Fluent NHibernate" group.
To post to this group, send email to fluent-nhibernate@googlegroups.com.
To unsubscribe from this
Export your mappings and show us them, that's a good place to start.
Is it only SQLite which is causing the problems, or do you get the same
issues with SQL server?
Try turning on show_sql (or use a profiler) to see what SQL is being
executed.
--
You received this message because you are subs
For the record, it seems the latest fnh works with latest nh preview. The
only thing i had to change was proxy factory factory to the built one
On 01/05/2011 6:47 PM, "James Gregory" wrote:
> How very sensationalist a title this is.
>
> No, FNH is not dead. Yes, there will be a release for NH 3.2.
How very sensationalist a title this is.
No, FNH is not dead. Yes, there will be a release for NH 3.2.
As has always been the case, we don't track non-GA releases, so as NH 3.2 is
currently still in Alpha we don't have a release out for it.
--
You received this message because you are subscrib
Hi Mohamed,
What version of FNH are you running?
1) Definitely sounds like an oversight. Ideally there should be a way for
the user (yourself...) to control what FNH considers a Set, rather than us
having a hard-coded list of collection types.
2) What part of the code is this? Even though FNH
19 matches
Mail list logo
