Bob, The problem you had was you pasted the location information inside the existing authorization tag, so it had the wrong PARENT element. It doesn't have to be the first child element in configuration.
Put the configSections tag as the first element and your authorization will still work. On 5/10/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hi all, > > A week or 2 ago, you guys (Dean I believe) helped me properly configure my > Web.Config file for some authorization issues. This was where I wanted to > have one web page that anyone could get to without any log-in like I want on > all my other pages. The problem I was having was that the code Dean posted > had to be directly under the <Configuration> tag to work properly. Here is > what I have: > > <configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0 > "> > <appSettings> > <add key="timeout" value="180" /> > </appSettings> > <location path="Default.aspx"> > <system.web> > <authorization> > <allow users="?"/> > <!-- Allow all users --> > </authorization> > </system.web> > </location> > > This works perfectly. But yesterday, I downloaded the Atlas AJAX version. > Many changes are required in the web.config for this to work. My problem > is that the <ConfigSections> tag will only work if it is directly under the > <configuration> tag. So what gives? Only one of these two sections can be > first. > > Thanks, > Bob > > [Non-text portions of this message have been removed] > > > -- Dean Fiala Very Practical Software, Inc Now with Blogging... http://www.vpsw.com/blogbaby Microsoft MVP [Non-text portions of this message have been removed]
