Do I use EF by choice?  Well, that's complicated :).  My preference
isn't even for .NET any longer honestly.

You can do almost anything with EF that you can do with NH.  You can
achieve field level security.  With the next version of EF you should
even be able to achieve an injected domain model in the style of how
RS injects its domain model into another projects NH settings.

My take is that if you're working alone or in a small company, NH is
likely the better choice.  If you're working in a larger company, if
you're new to .NET, or if you have to work with people who are new to
.NET, EF is probably the better way to go.

If you're adventurous, look into CouchDB or Ayende's RavenDB.  I use
CouchDB a lot and I love it.  RavenDB sounds great as well, but I
became hooked on CouchDB before Oren started Raven.

On Mon, May 16, 2011 at 9:56 AM, Deke Kraft <[email protected]> wrote:
> So are you using EF by choice? And are you able to achieve field level 
> security with EF?
>
> Sent from my iPhone
>
> On May 16, 2011, at 7:07 AM, Nathan Stott <[email protected]> wrote:
>
>> Since I'm using EF in new .NET projects, I've just rolled my own.
>>
>> For the projects I am maintaining that use RS, it has worked fine and
>> I am sure will continue to work fine for the lifetime of these
>> products.  Some people have reported problems with RS performance for
>> very large userbases with lots of operations.
>>
>> RS is a mature project that works well for what it does.
>>
>> On Mon, May 16, 2011 at 8:10 AM, Raif <[email protected]> wrote:
>>> First, sorry, I am recompiling with NH3 I was just under the
>>> impression that NH3 had removed ICriteria in favor of QueryOver but
>>> that is not the case.
>>> Second, Thank you for the offer but I don't think I would be a good
>>> manager for RS as I can barely get to the email I have now.  I do
>>> appreciate your doing the job.
>>> Third, I don't mean you push the point but if your not using it for
>>> new dev what are you using?  Did you branch RS for you a more specific
>>> purpose or have you rolled your own?  RS does seem to cover most bases
>>> but if you have more experience with it and have come across some
>>> short comings I'd like to hear about it and see if a) it's a going to
>>> burn me later or b) if I should try and address the issue and submit a
>>> patch.
>>> Thanks
>>> Raif
>>>
>>> On May 15, 10:13 pm, Nathan Stott <[email protected]> wrote:
>>>> I am using RS in projects I am maintaining.  I'm just not using it for
>>>> new development.  I will be happy to apply any well-made patches that
>>>> address issues or add functionality.  If they have good unit tests,
>>>> they are good by me.
>>>>
>>>> RS is still a great project.  It simply does everything I need it to
>>>> do in the projects I am maintaining.  I think the same is true for
>>>> many of its users.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Sat, May 14, 2011 at 10:09 AM, Deke Kraft <[email protected]> wrote:
>>>>> If you and Oren aren't using RS anymore, what are you using/suggest?
>>>>
>>>>> On Sat, May 14, 2011 at 7:45 AM, Nathan Stott <[email protected]> wrote:
>>>>
>>>>>> You can use RS with NH3 without recompiling it with the NH3 library?
>>>>>> That doesn't sound right.  It should certainly work with NH3 criteria
>>>>>> if you recompile using NH3 dependency though.
>>>>
>>>>>> Oren isn't using RS any longer except in existing projects.  The same
>>>>>> is true of me.  Oren passed the torch of RS to me to watch over it and
>>>>>> simply accept commits that fix issues.  If you want to actively
>>>>>> develop RS, I will be happy to pass the torch to you.
>>>>
>>>>>> On Fri, May 13, 2011 at 11:34 AM, Raif <[email protected]> wrote:
>>>>>>> Hi, in looking at this further, it seems that you can actually use
>>>>>>> criteria in NH3 the same way as you would in NH2.1.  And as such the
>>>>>>> RS can be used fully in with NH3.
>>>>>>> It might be nice to build the QueryOver stuff into it, in fact it
>>>>>>> certainly would because QueryOver is strongly typed and criteria uses
>>>>>>> strings, but it is not necessary.  Furthermore, I don't believe you
>>>>>>> can use linq with the QueryOver stuff but you can with the ICriteria
>>>>>>> stuff.  It's a tough call.
>>>>>>> I think if someone can show me that you can use linq with the
>>>>>>> queryover I would build an AuthorizationRepository that used it.  But
>>>>>>> unless you can some how turn an IQueryable<T> into a QueryOver<T,T> I
>>>>>>> don't see how.
>>>>>>> R
>>>>
>>>>>>> On May 12, 4:33 pm, Raif <[email protected]> wrote:
>>>>>>>> hrumph.
>>>>>>>> that sucks.
>>>>>>>> Essentially with out these features RS days are numbered.
>>>>>>>> so
>>>>>>>> 1) what is Oren doing?  I presume he's still using it and I presume
>>>>>>>> he's using NH3
>>>>>>>> 2) It would seem that the changes to make it compatible with NH3 are/
>>>>>>>> would be to change any method that returns an ICriteria to instead
>>>>>>>> return an IQueryOver<T,T>.  This I believe would be the private
>>>>>>>> GetPermissionQueryInternal methods. they would take the same args but
>>>>>>>> use the queryover to build up the IQueryOver<T,T>.
>>>>>>>> Does this sound right or would it involve a lot more?
>>>>>>>> Thanks,
>>>>>>>> Raif
>>>>
>>>>>>>> On May 12, 3:14 pm, Nathan Stott <[email protected]> wrote:
>>>>
>>>>>>>>> On Thu, May 12, 2011 at 3:03 PM, Raif <[email protected]> wrote:
>>>>>>>>>> So I guess my questions are
>>>>>>>>>> 1) Can I use RS and NH3 and linq?
>>>>
>>>>>>>>> No
>>>>
>>>>>>>>>> 2) Can I use RS and NH3 and Criteria?
>>>>
>>>>>>>>> No
>>>>
>>>>>>>>>> 3) Can I even use RS and NH3 or does it need to be refactored to
>>>>>>>>>> use
>>>>>>>>>> NH3.
>>>>
>>>>>>>>> Needs to be refacoted to use NH3.  It currently uses NH 2.1.0.4000
>>>>
>>>>>>>>>> 4) Should I look at extending the RSRepository to use linq or will
>>>>>>>>>> that kill all the level 2 cache stuff and/or is that a huge
>>>>>>>>>> undertaking.
>>>>
>>>>>>>>> If you are interested in doing this refactor, it would be much
>>>>>>>>> welcomed by RS users and may even promote a renaissance of RS usage.
>>>>>>>>> It will not be trivial
>>>>
>>>>>>> --
>>>>>>> You received this message because you are subscribed to the Google
>>>>>>> Groups "Rhino Tools Dev" 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/rhino-tools-dev?hl=en.
>>>>
>>>>>> --
>>>>>> You received this message because you are subscribed to the Google Groups
>>>>>> "Rhino Tools Dev" 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/rhino-tools-dev?hl=en.
>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google Groups
>>>>> "Rhino Tools Dev" 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/rhino-tools-dev?hl=en.
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups 
>>> "Rhino Tools Dev" 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/rhino-tools-dev?hl=en.
>>>
>>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups 
>> "Rhino Tools Dev" 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/rhino-tools-dev?hl=en.
>>
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Rhino Tools Dev" 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/rhino-tools-dev?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Rhino Tools Dev" 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/rhino-tools-dev?hl=en.

Reply via email to