Now that the list is considerably reduced, as you said, it is probably quite
reasonable to apply this. I hope to remove the concept of the default
conventions all together, but I'm not sure if we can manage that before 1.0.

On Thu, Aug 20, 2009 at 1:40 PM, maxild <[email protected]> wrote:

>
> Hi,
>
> I saw some mention of 'issue 200' (http://code.google.com/p/fluent-
> nhibernate/issues/detail?id=200) when reading tons of mail. I just
> wanted to say that I have updated the patch. It can be seen here
>
> http://github.com/maxild/fluent-nhibernate/commit/f3b061bad9199b26e14cd810093f206fb33d4259
>
> I also noticed that the number of registered conventions had been
> drastically lowered --- this makes the commit/patch even simpler. It
> would be nice to have the patch applied.
>
> Sry for not being quicker to respond...have been away and ill for some
> time
>
> regards
> maxild
>
> On Aug 13, 8:59 pm, Jorgas <[email protected]> wrote:
> > On the same subject...
> >
> > What I ended up doing was that I am still using FluentNHibernate for
> > mapping using c# mapping files. And from those I generate *.hbm files
> > that I include in my project as embedded resources. And instead of
> > configuring NHibernate in my running application using
> > Fluently.Configure I configure my NHibernate parts using NHibernates
> > own configuration methods, adding the mappings from the embedded *.hbm
> > files instead. This makes the whole thing works inmediumtrustas
> > well.
> >
> > I did run into one problem though... It seems as Lazy Loading doesn't
> > play nice together withmediumtrustenvironments either, so I skipped
> > lazy loading (doesn't matter that much for me at this point any way).
> > But setting Not.LazyLoad() inside the .SubClass() method of the
> > DiscriminateSubClassesOnColumn<T> method doesn't seem to render the
> > lazy="false" attribute of the <subclass> element in the generated
> > *.hbm file. Is this a known behavior?
> >
> > Regards, Jörgen
> >
> > On Aug 12, 10:25 pm, James Gregory <[email protected]> wrote:
> >
> > > What stopped you from applying Mick's patch? What exactly is preventing
> you
> > > from running FNH undermediumtrust? People who have this issue seem to
> drop
> > > in, say "it doesn't work inmediumtrust", and then never come back.
> Makes
> > > it very difficult to pin it down.
> >
> > > On Wed, Aug 12, 2009 at 9:11 PM, Jorgas <[email protected]
> >wrote:
> >
> > > > Hi James.
> >
> > > > Any idea on when there will be a supported release from you guys
> where
> > > > this is addressed and working?
> >
> > > > I could not apply the patch supplied by Mick Delaney, is there a
> > > > version in the repository that has got it applied?
> >
> > > > Is there any other way of getting FluentNHibernate to work under
> > > >mediumtrust, short of installing it in the GAC? I'm not convinced my
> > > > ISP will allow that.
> >
> > > > Regards, Jörgen
> >
> > > > On 31 Juli, 19:05, James Gregory <[email protected]> wrote:
> > > > > Unfortunately that's still the case. Does the same fix work for
> you?
> > > > > For 1.0 we're drastically reducing the number of internal
> conventions, so
> > > > we
> > > > > may be able to remedy this on release.
> >
> > > > > On Fri, Jul 31, 2009 at 4:42 PM, Michael Delaney <
> [email protected]
> > > > >wrote:
> >
> > > > > > is FNH usable undermediumtrust. there seems to be an open issue
> > > > > > here:
> >
> > > > > >http://code.google.com/p/fluent-nhibernate/issues/detail?id=200
> >
> > > > > > i'm having the exact same problem.
> >
> > > > > > cheers.- Dölj citerad text -
> >
> > > > > - Visa citerad text -- Hide quoted text -
> >
> > > - Show quoted text -
> >
> >
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Fluent NHibernate" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/fluent-nhibernate?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to