Web.config Atlas and Ajax?

If you created your project with the "ASP.NET AJAX-Enabled Web Site" template you already have everything you need in the Web.config, if your project is a normal ASP.NET project then the easiest way of configuring your Web.config is by creating a website with the Ajax-Enabled template and then copy all the relevant parts into your own file.

Things have changed since the time of Atlas, check these links for information about webservices:

http://www.asp.net/ajax/documentation/live/tutorials/ExposingWebServicesToAJAXTutorial.aspx

http://www.asp.net/ajax/documentation/live/tutorials/ConsumingWebServicesWithAJAXTutorial.aspx

Hope this helps,
Elias.

So you cant use Atlas script with Ajax? I want to be able to do some examples from a book on Atlas but It doesnt recognise this sort of stuff: (see below). Is there a way i can merge the Atlas web.config and Ajax.config? As my site is already filled with the latest Ajax stuff. I cant understand why Mircosoft would get rid of functionality. ?

<scripttype="text/xml-script">

<page xmlns:script="http://schemas.microsoft.com/xml-script/2005">

<components>

<textBox id="txtFirst" />

<textBox id="txtLast" />

<button id="cmdOK">

<click>

<setProperty target="txtFirst" property="text" value="" /><setProperty target="txtLast" property="text" value="" />

</click>

</button>

<label id="spanFirst">

<bindings>

<binding dataContext="txtFirst" dataPath="text" property="text"

transform="ToString" transformerArgument="Your full name is {0}" />

</bindings>

</label>

<label id="spanLast">

<bindings>

<binding dataContext="txtLast" dataPath="text" property="text"

transform="ToString" transformerArgument="{0}." />

</bindings>

</label>

</script>

Believe me I feel your pain, at the time of the "change" I was working in a big application (I know it was my fault for using pre-beta code) that used several in-house Atlas Toolkit controls (at the time the Toolkit had just a few controls) , then I had two options stick with Atlas or convert my application, so I took the bullet and convert it, and let me tell you it's worth it, at first some of the changes didn't make any sense (if you look for the posts at the time you'd find this used to be a very hot topic for everyone) but in the process I've found they were for the best, in my opinion ASP.NET Ajax is much more stable than Atlas, I suggest, especially if you are beginning with Ajax that you drop Atlas and use ASP.NET Ajax, especially since as I remember the go-live license of Atlas is about to expire.