Securing Applications in ASP.NET 2.0
page 5 of 5
by Uday Denduluri
Feedback
Average Rating: This article has not yet been rated.
Views (Total / Last 10 Days): 22840/ 48

Conclusion

Securing Applications is always one of the toughest challenges programmers face. This is because of the changes the application undergoes. The security policies do change and thus the security code needs to be rewritten. For such scenarios Microsoft has come up with the provider model. The inbuilt classes such as MembershipProvider, RoleProvider, and ProfileProvider help us to create our own custom classes. In case of any changes in the security policy we just need to write a new custom class that deals with the changes. Also, since its assembly names are mentioned in the configuration, we can maintain different versions of the custom classes.


View Entire Article

User Comments

No comments posted yet.

Product Spotlight
Product Spotlight 





Community Advice: ASP | SQL | XML | Regular Expressions | Windows


©Copyright 1998-2021 ASPAlliance.com  |  Page Processed at 2021-03-02 12:49:31 PM  AspAlliance Recent Articles RSS Feed
About ASPAlliance | Newsgroups | Advertise | Authors | Email Lists | Feedback | Link To Us | Privacy | Search