e-commerce site using asp.net

[bobo12]

hi all,
so the hosting company is using win2003 servers for an e-commerce site that we will launch eventually. the site will be done using asp.net with backend dbs. i expect a majority of the work to be the coding aspect in asp.net but i want to know how much or what do i need to do as far as win2003 server is concerned?

i guess i don't know where the line for asp.net programming is seperated from win2003? is there anything i need to do to the actual win03 server, or do i simply upload the asp.net scripts and thats it?

 

[aftertaf]

humm...
best check the programming formums for technical aspects of that...

But you need to install and set up IIS. Gtet the server up to date with the latest sPacks for .Net framework 1.1.

DB backend - SQL Server 2000?
need to see how user authentification will be managed. AD users, validated by IIS and SQL ?

best thing to do in VSNet is to add a deployment program to your project, that way it packages everything up in a MSI. When you the install this on your server, it will add it correctly to IIS, set up the virtual directory etc...

then all you have to do it configure the authorization mode you are using...

i've done this in the past with SQL Server , VSNEt, web services and shared libraries (distributed DLL packages), but for our intranet.
i used windows authentification and authenticated against active directory... i dont know if you plan, or can, do this in your case

Aftertaf
if its not broken, fix it anyway - with luck you might break it and have an excuse

 

[JerryLan]

Authenticating against the Active Directory is prohibitive for an e-comerce site. This would require you to create a user in your active directory for every person you wish to allow access to, ie each of your customers. The better choice would be to create an automated login/user creation page which would allow the user to create their own account. The result would be stored in the database. This would require forms authentication. In IIS you would specify that this application would run under the Worker Process Group. On my 2003 server this is the IIS_WPG account. This account would have read and write access to the authentication database and security standards would dictate that the passwords would not be stored in plain text, but be encrypted. I do not recommend using the SA username and password to connect to the database. If the IIS_WGP user has windows authentication access then you are ok provided there is no way for your program to do things to the database that you have not specifically programmed for.