web.config

this is the file to chat in web

<?xml version="1.0"?>
<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">
 <connectionStrings>
    <!--<add name="PhotoDBConnectionString0" connectionString="Data Source=.\SQLEXPRESS;Database=Photos.mdf;Integrated Security=True;Connect Timeout=30;User Instance=True" providerName="System.Data.SqlClient"/>-->

    <add name="msn_Data_ConnStr" providerName="System.Data.SqlClient" connectionString="server=zxzcom\SQLEXPRESS;database=AjaxChatDB;Integrated Security=SSPI"/>

  </connectionStrings>



  <!--<configSections>
		<sectionGroup name="ajaxNet">
			--><!--
				If you are using Microsoft .NET 1.1 please remove the two attributes
				RequirePermission  and restartOnExternalChanges, they are only supported
				with .NET 2.0.
			--><!--
			<section name="ajaxSettings" type="AjaxPro.AjaxSettingsSectionHandler,AjaxPro.2" RequirePermission="false" restartOnExternalChanges="true"/>
		</sectionGroup>
	</configSections>-->
	<!--<ajaxNet>
		<ajaxSettings>
			<urlNamespaceMappings useAssemblyQualifiedName="false">
				--><!--
					Set the attribute useAssemblyQualifiedName to true to enable
					use of assemblies placed in the GAC by using the full assembly
					qualified name.
				
					To hide internal knowledge of assemblies, classes and namespace
					you can override the name of the virtual http endpoints.
					
					<add type="Namespace.Class1,Assembly" path="mypath" />
				--><!--
			</urlNamespaceMappings>
			<jsonConverters>
				--><!--
					This section can be used to add new IJavaScriptConverters to the
					Ajax.NET Professional engine. If you want to disable built-in
					converters you can use the remove tag.
				
					<remove type="Namespace.Class1,Assembly"/>
					<add type="Namespace.Class2,Assembly"/>
				--><!--
			</jsonConverters>
			--><!--
				Set the enabled attribute to true to get Stack, TargetSize and Source 
				information if an exception has been thrown.
			--><!--
			<debug enabled="false"/>
			--><!--
				This is the default configuration used with Ajax.NET Professional. You
				can put there your static JavaScript files, or remove the path attribute
				to completly disable the files.
			
				<scriptReplacements>
					<file name="core" path="~/ajaxpro/core.ashx" />
					<file name="prototype" path="~/ajaxpro/prototype.ashx" />
					<file name="converter" path="~/ajaxpro/converter.ashx" />
				</scriptReplacements>
			--><!--
			--><!-- <encryption cryptType="" keyType="" /> --><!--
			--><!--
				Set the enabled attribute to true to enable the use of an Ajax.NET Professional
				token. This will send a token to the client that will be used to identify if the
				requests comes from the same PC.
			--><!--
			<token enabled="false" sitePassword="password"/>
			--><!--
				The oldStyle section can be used to enable old styled JavaScript code or
				functions that are not used any more.
			--><!--
			<oldStyle>
				<includeMsPrototype/>
			</oldStyle>
		</ajaxSettings>
	</ajaxNet>-->
	<location path="ajaxpro">
		<system.web>
			<httpHandlers>
				<add verb="*" path="*.ashx" type="AjaxPro.AjaxHandlerFactory,AjaxPro.2"/>
			</httpHandlers>
			<!--
				If you need to have Ajax.NET Professional methods running on the
				login page you may have to enable your own authorization configuration
				here.
			-->
			<!--
			<authorization>
				<deny users="?"/>
			</authorization>
			-->
		</system.web>
	</location>
	<!--
		If you are using Ajax.NET Professional with forms authentication you may need
		to allow ASP.NET to have access to following three files.
	-->
	<!--self adding--><!--
	<authentication mode="Forms">
		<forms loginUrl="Login.aspx" protection="All" path="/"/>
	</authentication>-->
	<location path="ajaxpro/prototype.ashx">
		<system.web>
			<authorization>
				<allow users="*"/>
			</authorization>
		</system.web>
	</location>
	<location path="ajaxpro/core.ashx">
		<system.web>
			<authorization>
				<allow users="*"/>
			</authorization>
		</system.web>
	</location>
	<location path="ajaxpro/converter.ashx">
		<system.web>
			<authorization>
				<allow users="*"/>
			</authorization>
		</system.web>
	</location>
	<system.web>
		<authentication>
   <forms loginUrl="Login.aspx" />
  </authentication>
  <compilation debug="true"/></system.web></configuration>