优雅的 Asp.Net MVC 3 自定义成员资格包装类，具有扩展（自定义）方法和属性

发布于 2024-11-06 21:16:29 字数 833 浏览 4 评论 0原文

我正在尝试编写一个自定义会员资格类别。继承 Membership 类并为所有包含的必需项目（验证用户、创建用户、删除用户、已批准等）提供功能似乎可以正常工作。

然而，当我尝试添加属性或方法时，我遇到了问题。

由于所有其他属性和方法都是密封类中的公共重写类，附加属性不会显示。

举例来说（仅作为示例，而不是“真实”代码）：

public sealed class Membership : MembershipProvider
{
    public override string ApplicationName
    {
        get
        {
            return "myApp";
        }
    }
    public string myValue { get;set;}
}

现在，我明白为什么当我尝试执行 Membership.myValue 时 myValue 不会显示，但 Membership.ApplicationName 会显示。

我的问题是，如何扩展会员资格以显示自定义项目？我是否完全放弃 Membership.xxx 并编写一个包装类？如果是这样，怎么办？我可以找到世界上所有有关如何创建自定义会员级别的文档。我有一个工作自定义会员资格，如果我仅使用所有可用选项，它就可以正常工作。我有一个自定义角色提供程序和一个自定义配置部分来存储所有内容，它是最好的朋友。

我没有一个优雅的解决方案。

我希望最终结果是我使用一个引用（例如 Membership.xxx 或 myClass.xxxx）来引用所有会员项目 + 自定义项目。

请提供如何实施的示例或链接到将解决自定义方法项目的适当项目。

原文

I am attempting to write a custom membership class. It seems to work ok inhering the Membership class and providing functions for all the included required items (validate user, create user, delete user, isapproved, etc).

However, where I run into a problem is when I try to add properties or methods.

As all the other properties and methods are public override classes in a sealed class,
the additional properties do not show up.

Say for example (example only, not "real" code):

public sealed class Membership : MembershipProvider
{
    public override string ApplicationName
    {
        get
        {
            return "myApp";
        }
    }
    public string myValue { get;set;}
}

Now, I understand why myValue will not show up when I try to do Membership.myValue but Membership.ApplicationName will.

My question is, how to extend membership to show the custom items? Do I ditch Membership.xxx entirely and write a wrapper class? If so, how? I can find all the documentation in the world on how to create a custom membership class. I've got a working custom membership that works fine if I use all the available options only. I've got a custom roles provider and a custom config section to store everything and it's best friend.

What I don't have is an elegant solution.

I'd like the end result to be that I use one reference (such as Membership.xxx or myClass.xxxx) to reference all membership items + custom items.

Please provide examples of how to implement or links to appropriate items that will resolve the custom methods item.

分享到QQ

分享到微博