Stuck on Web Config

[FuzzBox]

Hi all,
I have created a three page website in FrontPage ran it and it works fine. Then I copied all the HTML of one form and pasted it in one of the web forms and renamed it. I then added the <form id=”FormName” method=”post” runat=”server” > and <form/> tags. I repeated this for all three pages. Which is simple so far , ok.

In IIS I created a virtual directory with a path to the folder that contains my Default.aspx for my three page web site (which is in C:\Inetpub\wwwroot\Alias\folderName).

Back in .NET I compile with no errors. Then I click on View in Browser and I get the follow error message for Web Config:

Parser Error Message:
It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS.

Source Error:
Line 19: "Forms", "Passport" and "None"
Line 20:
-->Line 21: <authentication mode="Windows" />
Line 22: <!-- AUTHORIZATION
Line 23: This section sets the authorization policies of the application. You can allow or deny access

I have tried "Forms" and "None" in line 21 above but with the same result.

Any ideas where I'm going wrong?

Thanks for your time

[scostell]

In IIS, if you go to the Virtual Directory you created and go to it's properties does it have an Application Name?

When I got that error message that's what the problem was. If the virtual folder has an application name the icon in IIS under "Default web services" will not be a folder but something else.

[FuzzBox]

Yes I do have the correct application name and an icon other that a folder.

[scostell]

I've got no idea then. If you figure it out please post the solution just in case I run into that problem in the future.

Thanks

[FuzzBox]

Ok, I think I know what I have done wrong. Since I'm not getting this error any more I have an other error related to HTML

Anyway, I took my code from FrontPage as I mentioned. But I had 'Published' the website in FP on my PC to check it out. That must of caused some conflict with the autentication mode. I redone the website without publishing it and it seems to have gone.