[asp.net 2.0] Interesting Membership problem

[Jeff]

Hey

ASP.NET 2.0

At work my boss have given me the task of developing a new website. Users
will be able to register at the website and gain exclusive access to some
information etc... Some users will have limited access to the information
and some users (Administrators) will have total access. There will be 3
levels of users: Normal User, Power User and Administrator.

My boss have created the table design for this project. The table UserType
will hold information about the user levels/categories. I've mentioned to my
boss that using the Membership system in ASP.NET 2.0 could be better. Anyway
he still wants to avoid using Membership and instead use plain tables. He
also wants me to use the standard Login and NewUser controls in ASP.NET 2.0,
but I'm not sure I can use them when the data will not be stored in the
Membership system..... I think he wants to avoid using Membership system
cose he don't understand how it works, I would maybe do the same if I didn't
know how it works....

- There will be a few hundred registered users at the website.
- Data will be stored in Sql Server 2005

(I'm new at work, so it's not easy for me to convince my boss that I'm right
and he is not etc)

Do you have any links telling all the advantages using Membership compared
to using regular tables (as we are about to do), regarding speed of
development, security, gui design and flexibility. I could send my boss the
link

Lets say if I need to program this now as my boss suggest. How should I go
about implement custom providers for SiteMap and Security - I know that in
web.config I can specify that a certain SiteMap is available for a certain
role, but if I develop this project as my boss wants then I guess I need to
develop some kind of custom provider for it to work

Do you see any advantages using the system my boss suggest compared to using
the ASP.NET Membership system.

Any other suggestions are more than welcome ;)

[Joe Fawcett]

"Jeff" <it************@hotmail.com.NOSPAMwrote in message
news:eD**************@TK2MSFTNGP02.phx.gbl...

Hey

ASP.NET 2.0

At work my boss have given me the task of developing a new website. Users
will be able to register at the website and gain exclusive access to some
information etc... Some users will have limited access to the information
and some users (Administrators) will have total access. There will be 3
levels of users: Normal User, Power User and Administrator.

My boss have created the table design for this project. The table UserType
will hold information about the user levels/categories. I've mentioned to
my boss that using the Membership system in ASP.NET 2.0 could be better.
Anyway he still wants to avoid using Membership and instead use plain
tables. He also wants me to use the standard Login and NewUser controls in
ASP.NET 2.0, but I'm not sure I can use them when the data will not be
stored in the Membership system..... I think he wants to avoid using
Membership system cose he don't understand how it works, I would maybe do
the same if I didn't know how it works....

- There will be a few hundred registered users at the website.
- Data will be stored in Sql Server 2005

(I'm new at work, so it's not easy for me to convince my boss that I'm
right and he is not etc)

Do you have any links telling all the advantages using Membership compared
to using regular tables (as we are about to do), regarding speed of
development, security, gui design and flexibility. I could send my boss
the link

Lets say if I need to program this now as my boss suggest. How should I go
about implement custom providers for SiteMap and Security - I know that in
web.config I can specify that a certain SiteMap is available for a certain
role, but if I develop this project as my boss wants then I guess I need
to develop some kind of custom provider for it to work

Do you see any advantages using the system my boss suggest compared to
using the ASP.NET Membership system.

Any other suggestions are more than welcome ;)

I've used the Membership system often. It's fairly easy to employ and extend
by inheriting from the basic provider and/or the MembershipUser.
The roles stuff also works more or less out-of-the-box and is implemented as
you'd probably do it yourself.
Although Microsoft doesn't always produce the best code every time it's hard
to imagine that a lone developer with other jobs to do could produce a
system as flexible and powerful in a limited time frame.
There is a good Wrox book on the system:
http://www.wrox.com/WileyCDA/WroxTit...764596985.html and 4 guys
from Rolla did a lengthy series on it too:
http://aspnet.4guysfromrolla.com/articles/072308-1.aspx

--

Joe Fawcett (MVP - XML)
http://joe.fawcett.name