Artur Trosin's blog - All Comments

Twitter Trackbacks for Domain Driven Design: Learning - Artur Trosin's blog [asp.net] on Topsy.com

Fri, 25 Sep 2009 07:41:31 GMT

Pingback from Twitter Trackbacks for Domain Driven Design: Learning - Artur Trosin's blog [asp.net] on Topsy.com

re: Rhino Tools: Rhino Security Guide

Rich — Thu, 27 Aug 2009 13:59:07 GMT

Do you know if it is possible to use Rhino Security with Castles NHibernate Integration facility? It looks like the need to have a Hibernate.cfg.xml configuration file will not allow it.

re: Rhino Tools: Rhino Security Guide

dotnet coder — Wed, 22 Jul 2009 05:13:01 GMT

Can u publish a post for" EntityGroups, IEntityInformationExtractor, Query Permissions,.. ,Permissions class " ??? A demo would be a good start to look into these left out topics of rhino security .

re: Rhino Tools: Rhino Security Guide

Artur Trosin — Tue, 21 Jul 2009 06:30:35 GMT

Hi @dotnet.coder,

You can store your entities wherever you want (even outside the DB), the only info that is required to “know” by Rhino Security is IEntityInformationExtractor. The interface (should) provides a unique key that in unique mode indentify the entity when the entity is associated with Rhino Security(e.g. add permission for the entity, the entity is added to group,…).

Hope that helps

re: Rhino Tools: Rhino Security Guide

dotnet.coder — Tue, 21 Jul 2009 01:04:10 GMT

Do we need to add tables in the rhino security schema for each and every entity we want to add to entity group ??? or the entities would be picked from application schema only ????

re: Rhino Tools: Rhino Security Guide

dotnet.coder — Thu, 16 Jul 2009 00:58:36 GMT

Thanks for the useful info. I have been looking into rhino security recently.

It would be great if you could cover EntitiesGroups and other areas of Rhino security skipped in this post.

#.think.in infoDose #32 (2nd June - 9th June)

#.think.in — Fri, 12 Jun 2009 21:53:42 GMT

#.think.in infoDose #32 (2nd June - 9th June)

Domain-Driven Design: Two basic premises

Artur Trosin's blog — Tue, 09 Jun 2009 14:41:37 GMT

In the post I want to discuss about two basic Domain-Driven Design premises which stand on the base of

re: Domain-Driven Design: Two basic premises

Zaphod — Tue, 09 Jun 2009 13:40:20 GMT

On to the main point. It's simply amazing that the most minimal, time-honored practices can suddenly assume a name ("DDD") and be marketed. That's why I got out of the software development industry.

re: Builder Pattern and Fluent Interface

Artur Trosin — Mon, 08 Jun 2009 07:15:34 GMT

@Sandeep

I’m glad you liked it.