In the same web.config (that means also files in the same application)
specify a <location> tag (inside <configuration> outside <system.web>) that
points to the file. Inside it specify differentiating authorization details.
...
</system.web>
<location path="publicpage.aspx">
<system.web>
<authorization>
<allow users="*" />
</authorization>
</system.web>
</location>
...
</configuration>
If you need to protect other content than normal ASP.NET stuff like aspx,
asmx etc, you need to map that file extension in IIS for ASP.NET's ISAPI dll
so those files are served by ASp.NET (that they are *not* by default)

Signature
Teemu Keiski
MCP, Designer/Developer
Mansoft tietotekniikka Oy
http://www.mansoft.fi
AspInsiders Member, www.aspinsiders.com
ASP.NET Forums Moderator, www.asp.net
AspAlliance Columnist, www.aspalliance.com
> Hi all;
> I want to use user name and password in my asp.net project
[quoted text clipped - 14 lines]
>
> Thanks for your help...