That is true and its not even a hard reference, NH uses reflection to load it. However there are hard references to assemblies like System.ServiceModel, System.Transactions and System.Configuration which dont exist in dnx. The system.configuration change is probably the hardest part.
On Monday, October 12, 2015 at 5:30:51 PM UTC-4, Ricardo Peres wrote: > > The only place where System.Web.dll classes are referenced is > WebSessionContext, AFAIK. > > RP > > On Monday, October 12, 2015 at 6:31:05 PM UTC+1, Jeffrey Becker wrote: >> >> It looks like some of the dependencies aren't dnx compatible. On top of >> that there would probably be some pretty serious breaking changes for a dnx >> compatible NHibernate no? >> >> On Monday, October 12, 2015 at 9:09:39 AM UTC-4, Fabio Maulo wrote: >>> >>> If the problem is just the webcontext what you have to do is a custom >>> implementation of ICurrentSessionContext. >>> The full real support of dnx is another matter... a little bit more >>> complicated. >>> BTW with the full .NET framework NH should work. >>> >>> On Thursday, September 17, 2015 at 6:40:40 PM UTC-3, Riy wrote: >>>> >>>> Hi Patric, >>>> >>>> I am testing it against DNX, I had removed DNX core from project.json. >>>> >>>> I got error for webcontext since nHibernate is looking for a context to >>>> bind the session and MVC6 doesn't provide webcontext out of the box there >>>> it fails. >>>> >>>> I attached my project, if possible please take a look into it and do >>>> let me know if I am doing something wrong or point me in right direction >>>> from where I can upgrade my projects. >>>> >>>> Thanks. >>>> >>> -- You received this message because you are subscribed to the Google Groups "nhusers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/nhusers. For more options, visit https://groups.google.com/d/optout.
