web.config

Build words list automatic

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
	<appSettings>
		<!-- extSet is the Set of extensions which this app will recognise 
		for auto-generation of menus -->
		<add key="extSet" value=".htm, .html, .asp, .aspx, .doc, .xls, .ppt, .pub, .mov, .avi, .wma, .wmv, .mp3, .pdf, .jpg, .jpeg" />
		
		<!-- key "privilegedGroup" is for INTRANET use.
		Value is the server user group eg "Teachers".   
		You can use the dummy value "Test" to open the privileged area 
		to everyone for testing. 
		<add key="privilegedGroup" value="Test" /> 
		You can use a non-existent group to switch off the privileged area altogether
		<add key="privilegedGroup" value="xxxxxxxx" /> 
		
		For INTERNET custom login, use a value of ""
		<add key="privilegedGroup" value="" />
		-->
		<add key="privilegedGroup" value="Test" />
		
		<add key="mainDir" value="Content" />
		
		<add key="publicDir" value="Departments" />
		<add key="publicLabel" value="Public" />
		<add key="privilegedDir" value="Staff" />
		<add key="privilegedLabel" value="Staff" />
		
		<!-- "Services" are independent pages or web app programming
		added to this framework.  Include your start pages in this list 
		to have them appear (minus extension) in the top menu bar.
		Value is the web path of your start page relative to this app root.
		-->
		<add key="service1" value="Services/About.htm" />
		<add key="service2" value="Services/Notices.aspx" />		
		
		<!-- Database Connection Strings.  Note the [-MAPPATH-] token for Microsoft Access.
		 Other database engines do NOT need this.  
		 These entries are processed in  'global.asax : Sub Session_onLoad' -->
		<add key="connDbControl" value="Provider=Microsoft.Jet.OLEDB.4.0; Data Source=[-MAPPATH-]\services\48002\Control.mdb; User ID=Admin;" />
		<add key="connDbNotices" value="Provider=Microsoft.Jet.OLEDB.4.0; Data Source=[-MAPPATH-]\services\48001\Notices.mdb; User ID=Admin;" />
		
		<!-- noticesSubmitNewOnly value="true" or "false".  Most commonly "false" 
		 "true" prevents change to existing notices -->
		<add key="noticesSubmitNewOnly" value="false" />
		<!-- noticesModeration value="true" or "false".  Most commonly "false"
		 "true" prevents display until checked and approved by administrator -->
		<add key="noticesModeration" value="false" />
		
		<!-- The 'Service' view.aspx enables "cloaking" of files placed
		 in a "cloaked directory" and accessed indirectly via Server.Transfer.
		 Also, download statistics are collected on such files 
		 This is an Internet facility, usually not needed on Intranet setups 
             Note subfolders indicated with forward slashes "/" -->
		<add key="cloakedDir" value="Content/48003" />
		
		<!-- AutoEmail is built into the new user Registration process
		This only applies when running in INTERNET mode 
		and you take new registrations
		and email these users their new passwords.
		Even then it is an optional extra. To activate, set IsAutoEmail to "true".-->
		<add key="IsAutoEmail" value="false" />
		<!-- AutoEmailFrom is what the User will see as the sender of an automated email.
		NOTE the XML requirement that reserved characters < and > 
		are represented as &lt; and &gt; -->
		<add key="AutoEmailFrom" value="Web Site Name &lt;[e-mail]&gt;" />
		<!-- AutoEmailSmtpServer value="" is the default and causes xmcontentmanager
		to attempt to find and use an SmptServer built in to the WebServer -->
		<add key="AutoEmailSmtpServer" value="" />
		
		<!-- dropbox, value = folder
		<add key="dropbox" value="xxxxx" /> -->
	</appSettings>
	<system.web>
		<!--  DYNAMIC DEBUG COMPILATION
          Set compilation debug="true" to insert debugging symbols (.pdb information)
          into the compiled page. Because this creates a larger file that executes
          more slowly, you should set this value to true only when debugging and to
          false at all other times. For more information, refer to the documentation about
          debugging ASP.NET files.
    -->
		<compilation defaultLanguage="vb" debug="true" />
		<!--  CUSTOM ERROR MESSAGES
          Set customErrors mode="On" or "RemoteOnly" to enable custom error messages, "Off" to disable. 
          Add <error> tags for each of the errors you want to handle.

          "On" Always display custom (friendly) messages.
          "Off" Always display detailed ASP.NET error information.
          "RemoteOnly" Display custom (friendly) messages only to users not running 
           on the local Web server. This setting is recommended for security purposes, so 
           that you do not display application detail information to remote clients.
    -->
		<customErrors mode="Off" />
		<!--  AUTHENTICATION 
          This section sets the authentication policies of the application. Possible modes are "Windows", 
          "Forms", "Passport" and "None"

          "None" No authentication is performed. 
          "Windows" IIS performs authentication (Basic, Digest, or Integrated Windows) according to 
           its settings for the application. Anonymous access must be disabled in IIS. 
          "Forms" You provide a custom form (Web page) for users to enter their credentials, and then 
           you authenticate them in your application. A user credential token is stored in a cookie.
          "Passport" Authentication is performed via a centralized authentication service provided
           by Microsoft that offers a single logon and core profile services for member sites.
    -->
		<authentication mode="Windows" />
		<!--  AUTHORIZATION 
          This section sets the authorization policies of the application. You can allow or deny access
          to application resources by user or role. Wildcards: "*" mean everyone, "?" means anonymous 
          (unauthenticated) users.
    -->
		<authorization>
			<allow users="*" /> <!-- Allow all users -->
			<!--  <allow     users="[comma separated list of users]"
                             roles="[comma separated list of roles]"/>
                  <deny      users="[comma separated list of users]"
                             roles="[comma separated list of roles]"/>
            -->
		</authorization>
		<!--  APPLICATION-LEVEL TRACE LOGGING
          Application-level tracing enables trace log output for every page within an application. 
          Set trace enabled="true" to enable application trace logging.  If pageOutput="true", the
          trace information will be displayed at the bottom of each page.  Otherwise, you can view the 
          application trace log by browsing the "trace.axd" page from your web application
          root. 
    -->
		<trace enabled="false" requestLimit="10" pageOutput="false" traceMode="SortByTime" localOnly="true" />
		<!--  SESSION STATE SETTINGS
          By default ASP.NET uses cookies to identify which requests belong to a particular session. 
          If cookies are not available, a session can be tracked by adding a session identifier to the URL. 
          To disable cookies, set sessionState cookieless="true".
    -->
		<sessionState mode="InProc" stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data source=127.0.0.1;Trusted_Connection=yes"
			cookieless="false" timeout="20" />
		<!--  GLOBALIZATION
          This section sets the globalization settings of the application. 
    -->
		<globalization requestEncoding="utf-8" responseEncoding="utf-8" />
	</system.web>
</configuration>