I don't see why not. You also have Linq to SQL built into the framework, if the target is SQL Server. It's actually quite good. Certainly better than EF1. But NHibernate will provide a better upgrade path, if you manage to move away from .NET 3.5.
/G Den sön 18 nov. 2018 kl 16:16 skrev Stephen Meier <[email protected]>: > Hi, > > > > i need to enhance a older software that uses dot net 3.5 with a ORM layer, > since the EF 1 got a vote of no confidence back in 2009 im thinking about > using nhibernate. > > according to this: https://www.nuget.org/packages/NHibernate/4.1.2.4000 > it only needs: > > Iesi.Collections (>= 4.0.0 & < 5.0.0) > > > but is it a good idea to add a almost current nhibernate to such a old dot > net version? > > -- > 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 https://groups.google.com/group/nhusers. > For more options, visit https://groups.google.com/d/optout. > -- 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 https://groups.google.com/group/nhusers. For more options, visit https://groups.google.com/d/optout.
