ASP.NET IIS login problem
-
Sir, I am working on an e-commerce project using ASP.Net and C#.Net (Visual Studio 2005-Windows XP). I am facing problems in the login module. I created the login accounts using the roles and users in the ASP.Net Website Administration Tool. The login module is working fine when I test the website within the Visual Studio. I mean the login form is working properly under the Development Server integrated in the Visual Studio. What I want is to make this work properly under IIS (i.e. the Production Server). When I deployed the project to the IIS, the login form with the login control is displayed, but cannot login and gives a login failed message. I posted this problem in few forums along with the source code of the login module only. But nobody cared in downloading my source code. I have searched about this issue in Google and they are providing good tutorial links to solve this issue. Even after reading those I couldn’t solve this as I am new to Web Development. I need help from experts on this. Can you please provide me a sample source code with the web.config and also a description of the major steps in configuring IIS to support the role based login? I had gone through the following titles under google "Always set the "applicationName" property when configuring ASP.NET 2.0 Membership and other Providers" I would like you to see the following link which I tried. I think this will help you to help me. http://www.asp.net/hosting/tutorials/users-and-roles-on-the-production-website-vb Thanks in Advance.
-
Sir, I am working on an e-commerce project using ASP.Net and C#.Net (Visual Studio 2005-Windows XP). I am facing problems in the login module. I created the login accounts using the roles and users in the ASP.Net Website Administration Tool. The login module is working fine when I test the website within the Visual Studio. I mean the login form is working properly under the Development Server integrated in the Visual Studio. What I want is to make this work properly under IIS (i.e. the Production Server). When I deployed the project to the IIS, the login form with the login control is displayed, but cannot login and gives a login failed message. I posted this problem in few forums along with the source code of the login module only. But nobody cared in downloading my source code. I have searched about this issue in Google and they are providing good tutorial links to solve this issue. Even after reading those I couldn’t solve this as I am new to Web Development. I need help from experts on this. Can you please provide me a sample source code with the web.config and also a description of the major steps in configuring IIS to support the role based login? I had gone through the following titles under google "Always set the "applicationName" property when configuring ASP.NET 2.0 Membership and other Providers" I would like you to see the following link which I tried. I think this will help you to help me. http://www.asp.net/hosting/tutorials/users-and-roles-on-the-production-website-vb Thanks in Advance.
Have you deployed the app_code directory to your production environment? This is where the membership datebase is stored. Alternatively you can create the database in SqlServer like this: http://msdn.microsoft.com/en-us/library/x28wfk74.aspx[^] Which will let you store users in a proper database. If you go down this route make sure you change your web.config to point to the external DB.
-
Have you deployed the app_code directory to your production environment? This is where the membership datebase is stored. Alternatively you can create the database in SqlServer like this: http://msdn.microsoft.com/en-us/library/x28wfk74.aspx[^] Which will let you store users in a proper database. If you go down this route make sure you change your web.config to point to the external DB.
-
I don't have an app_code directory in the production environment. But I have an App_Data directory in the production environment. What to do?
modified on Thursday, July 8, 2010 12:23 PM
Sorry Gjm, my mistake. Put the app_data directory into your production environment.