I had to format my C Drive to freshly install IIS. After that Visual Studio is installed and now its working beautifully.
I did not install SQL Server again as I am using SQL Express that has been shipped with VS.
For other users my suggestion is: locally its better not using SQL Server 2005/2008.
Its wise to use SQL Express Database in APP_Data folder.
The whole afternoon went to fix up IIS in my Laptop. Actually till today I test my every kind of aspx web application in file system.
From today, I will go for IIS, almost adieu File Syatem?
Still the concept of virtual directory seems to be rather obscure, but I probably understood it at last! 🙂
After installing IIS it’s important to run aspnet_regiis.exe in Command Prompt. For the beginners, it’s important, don’t forget!
On a stateless protocol such as HTTP, and ASP.NET on the server side, how do you manage state on the Web?
Actually to pass data from one page to other page in ASP.NET, you can use several techniques.
You imagine something like this: http://… /page.aspx?state=some
So basically it’s about state mangement. And please remember there is no right answer.
There are some server side options : Application state, Cache object, Session state, Database.
Some client side options : Cookie, Hiddden field, ViewState, ControlState, QueryString (URL).
There is a great debate, which one is best?
As always, we start from where we ended last time, that is aspnet_regsql.exe.
System.Web.Security.SqlMembershipProvider: Provides you with the capability to use the
We have seen how aspnet_regsql.exe looks about. Now time to work around it and probably get into the real task.
There are several server controls which can talk to the Data source. But It needs providers to get works going.
So the things happen like this: server controls interact with the providers to retrieve informations about the users from the Data sources.
ASP.NET 3.5 provides two membership providers out of the box.
membership system to connect to Microsoft’s SQL Server 2000/2005 as well as with Microsoft
SQL Server Express Edition.
System.Web.Security.ActiveDirectoryMembershipProvider: Provides you with the capability
to use the membership system to connect to Microsoft’s Active Directory.
The default provider is the SqlMembershipProvider instance.
//here is the config settings in web.config
//end of the code
Now here in web.config, you can control your provider’s characters, like
minRequiredNonalphanumericCharacters=”1″ could be minRequiredNonalphanumericCharacters=”0″
So that you while registering you need not provide any Ulpha Numeric Character. But always it’s advisable to do that for resisting reverse engineering.
Actually I’d like to present this article in a few installments. Otherwise, in one go I’d not be able to finish it off, moreover, there will be gross injustice to the whole subject.
What you ‘d like to do
This question should be answered in the very beginning. What would you like to do?
Answer is, I’d like to make a membership log in page in a website using asp.net. When users first come to my site, they will be told that :
“You are not logged in, please register below..”
Below, there will be a hyperlink to the page, where they can register their username, password etc.
Next after registering they will be asked to Log in.
After logging in, they can go to the member’s page.
That is all I wanted to do.
What you required?
To accomplish your task, all you need is a Visual Studio Express or Standard edition. It’s a nice designer software having .NET framework and class library installed so you can primarily drag and drop user controls. And it’s better to install SQL Server 2005 installed. So that you can use aspnet_regsql.exe
The first step
Where you’ll keep your users records? You can build a Databese, say the name is Users and using aspnet_regsql.exe you can add user and membership tables there.
Go to the command prompt of VS 2008.
Type it down:
aspnet_regsql.exe -d Users -A all -E
Press enter. Membership, Profile and other classes and related tables will be added to the Databse Users.
How it happens?
Look at this image:
a series of providers is available in ASP.NET
What it’s saying is, ASP.NET provides a large number of providers. Now all you have to do is setting up your SQL Server 7.0, 2000, 2005, or 2008 to work with this providers. In the beginning, I told that SQL Server 7.0, 2000, 2005, or 2008 will work as your back end datacenter.
How the aspnet_regsql.exe looks
Got a good break on Forms authentication.
I’d like to share it as soon as possible. May be in one/two days.