This is not only a matter of sufficiently recent .Net Framework, but also a matter of sufficiently recent IDE, as discussed here <https://github.com/nhibernate/NHibernate.Mapping.Attributes/pull/12#issuecomment-374561506> .
Referencing a .Net Standard assembly requires switching to "PackageReferences" instead of using old "package.config" system. Recent versions of the .Net Framework are usable in old versions of Visual Studio, and many companies take quite some time to update their tooling (especially if they choose to have "perpetual licences" and so have to pay new ones for upgrading). VS 2013 end of support is in 2024 by example. Yes it cannot use C#6/7 features we are using in NHibernate code, but that does not prevent referencing and using the generated assembly. Le vendredi 13 avril 2018 17:12:39 UTC+2, Patrick Earl a écrit : > > I just wanted to add a clarifying note that .Net Standard is a target in > NHibernate 5.1 and it is supported in both .Net Core and sufficiently new > versions of the .Net framework (as well as others like Xamarin). I don't > think the main question is whether people are using .Net Core, but how long > to support old versions of the full framework if we've reached sufficient > parity with the .Net Standard version. > -- --- You received this message because you are subscribed to the Google Groups "nhibernate-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to nhibernate-development+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
