使用 NHibernate 时如何处理成员资格/角色? [英] How do you handle Membership/Roles when using NHibernate?

问题描述

我即将开始一个使用 NHibernate 和 ASP.Net MVC 的新项目，并且遇到了成员资格问题.我想知道我是否应该使用 3rd 方 NHibernate Membership/Role 提供程序，创建自己的，或者一起跳过这些提供程序.

I'm about to kick off a new project using NHibernate and ASP.Net MVC and have come upon the question of membership. I'm wondering if I should use a 3rd party NHibernate Membership/Role provider, create my own, or just skip the providers all together.

到目前为止我看过:
Manuel Abadia 的 NHCustomProviders - 似乎像很多配置一样，不确定是否要将所有这些都放在我的 web.config 中.
Leo Vildosola 的 NHibernateProvider - 项目所有者似乎不再支持它，因为他不支持不再使用 NHibernate.
Eucalypto - 我喜欢表结构，但有点警惕它附带的所有额外的 CMS 内容.
* 这些项目中的每一个看起来都已经有一段时间没有被触及了，这可能意味着需要额外的工作来更新它们以使用最新版本的 NHibernate.

So far I've looked at:
Manuel Abadia's NHCustomProviders - It seems like a lot of configuraton, not sure if I want to put all that in my web.config.
Leo Vildosola's NHibernateProvider - Which doesn't appear to be supported by the project owner anymore since he doesn't use NHibernate anymore.
Eucalypto - I like the table structure, but am a bit warry of all the extra CMS stuff it comes with.
* Each of these projects looks like it hasn't been touched in a while, which could mean extra work just getting them updated to use the newest version of NHibernate.

这是已多次解决的问题之一，我想花时间解决新问题，并希望增加一些商业价值.

This is one of those problems that's been solved many times and I would like to spend my time solving new problems, and hopefully adding some business value.

推荐答案

我自己动手.这实际上比大多数人想象的要容易得多(我也很惊讶)——一旦你真正开始，一切都会很快地结合在一起.花几天或更长时间解决已解决的问题是一回事，但这花了我几个小时，包括计划.

I rolled my own. It's actually a lot easier than most people think (I was surprised too) - once you actually get rolling, everything comes together pretty quickly. It's one thing to spend days or more solving a solved problem, but this took me all of a few hours including planning.

这篇关于使用 NHibernate 时如何处理成员资格/角色?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！