none
to reuse System.Web.Security in winforms RRS feed

  • Question

  • I have to do a project from rentacoder.com
    that is essentially to create a security framework (or API? what is the difference?)
    repeating functionality of System.Web.Security but for Windows Forms.

    There are few articles on using System.Web.Security for Windows forms (for ex., [1], [2])

    Nevertheles I'd like to understand better:
    Why the security API had not been unified through .NET? 
    Which possible differences, pitfalls should be considered?
    What are possible implications of using System.Web.Security for winforms

    Why someone would need or want to implement its own security framework having the ready (well-thought, well-done) one?
    What sould be changed in such (fine-tuned? in what?) custom Security API in comparison with System.Web.Security?

    Guennadi Vanine - Gennady Vanin - Геннадий Ванин
    [1]
    Juval Lowy. Unify Windows Forms and ASP.NET SECUTITY
    http://www.comconix.com/ivcug/archive/Unified%20Security%20with%20Juval%20Lowy.pdf

    [2]
    Maurice de Beijer. Using the ASP.NET membership provider in a Windows forms application
    http://www.theproblemsolver.nl/usingthemembershipproviderinwinforms.htm

    Sunday, November 25, 2007 7:11 AM

Answers