asp.net 2.0 login controls 1

[intrex]

I am ramping up on a new project with asp.net 2.0. I started designing the security system then realized that microsoft has built all of these login user controls for 2.0. I started diging around and experimenting with them some. I now have a very simple working web security system. Everything is actually pretty cool, but I can tell where this is going. From years of microsoft experience I am guessing that as soon as I want to do something outside of their default functionallity I am going to be better off writing this whole thing from scratch. The user system I am building is going to have to have alot more information than just login, password, and secret. I am going to want to be able to return more detailed messages to the user other than just you weren't able to login. Am I going to be able to easily tie these controls into my own database schema (right now I let the app create its sql express database in the app_data dir)? If so, are there any good tutorials out there on how to fully customize the createuserwizard control? Can I import the sqlexpress file into an enterprise sql server and then modify the schema of the user table? Has anyone in here gone down this road and had success? Basiclly I am asking for your opinion on wether or not these controls are worth using in a complex custom solution?

Thanks in advance for any help,

Bryan

 

[ca8msm]

I think I tend to favour the "DIY" approach. I've found that controls like this are very good for doing the basics and can be implemented a lot quicker than building your own but they do seem to make things harder once you want to do your own thing.

I've built my own from scratch that I use with each project, but you could always look at extending the microsoft controls.


____________________________________________________________

Need help finding an answer?

Try the Search Facility or read FAQ222-2244 on how to get better results.

 

[intrex]

Thanks for the reply,

It looks like I am going to design everything from scrath. Those controls are not very flexible at all (just as I suspected). Have you found any limitations or annoyances with using master pages. In .net 1.1 I always made user controls for common components on each page, but I was pretty excited about the idea of master pages. I haven't run into any problems yet but I am sure I will.

Bryan

 

[ca8msm]

I haven't really come across any problems with Master Pages as yet. I always went down the route of Page Inheritance in previous versions of the framework so I guess Master Pages have simply been an evolution of this.

The only slight drawback that may be of a problem to some (it hasn't bothered me since I never use the "design" window in VS) is that if you specify a default master page for the whole site (by setting it in the web.config file rather than on a page by page basis), the design window can't render the page.


____________________________________________________________

Need help finding an answer?

Try the Search Facility or read FAQ222-2244 on how to get better results.