the membership system

hi
could I have some advice please.
I am converting a classic ASP website to net asp.
The existing system has over 3000 customers registered (on a sql server 2008 database).

Is the membership system which is part of ASP NET appropriate for these customer records? It looks like it is not appropriate but I don't want to develop something and be told that I should have used the integrated system!

thanks

 

Why wouldn't it be appropriate?

 

hi dannymax
Because, frankly, I don't really know enough about asp.net (yet!) to be sure that i am doing things properly. I only looked at it for the first time 10 days ago!
I also don't have a lot of time for the conversion, I have to convert a large classic asp website asap because the company it is currently hosted with is dropping the IIS6 servers.
On searching for different hosting it seems that many others are planning to do the same in the near future, so it seemed to be a shortsighted move to just switch to another hosting company. Especially as there are a lot of website changes planned over the next six months.
So I appreciate all the advice/help I can get!
Michael

 

3000 user accounts stored in SQL Server - ASP.NET membership will work well for this purpose. It is in itself a large framework which shields you from having to design a database schema and write tons of boiler plate code to manage accounts and account related data. The Role and Profile services are related to membership (although not linked or hard wired in any mandatory way) - these might be worth some research too depending on your site requirements.

I've a web application that's been hosted on the DASP servers for the last 3 years that uses membership which proves it works well in this environment. My recommendation is take care when making your initial configuration choices specifically with respect to the applicationName attribute and passwordFormat attribute. If you make the right decisions from the start you'll spare yourself a lot of potential hassle later if someone decides they need things to work differently.

Don't just take my word for it though: http://msdn.microsoft.com/en-us/library/yh26yfzy.aspx