The latest Ajax .NET DLLs can be downloaded from www.schwarz-interactive.de.

You can refer to the following sites for additional details and simple Ajax examples:

http://www.nikhilk.net/AtlasScriptManager.aspx

http://www.west-wind.com/presentations/scriptcallbacks/sample/default.aspx

http://atlas.asp.net/docs/Walkthroughs/GetStarted/Basic.aspx

http://aspadvice.com/blogs/garbin/archive/2005/12/22/14432.aspx

About the Author
Mahalakshmi Ramachandran
Software Engineer, Iron Speed, Inc.

ASP.NET.4GuysFromRolla.com: An Extensive Examination of Web Services: "An Extensive Examination of Web Services Index
An Extensive Examination of Web Services is a multi-part article series spanning several months. Listed below are the current 'parts,' along with a very brief synopsis and the date published.
Part 1 - Examines the basics of Web services, what Web services are, and the technologies and standards that serve as the underpinnings of Web services. (October 8th, 2003)
Part 2 - Examines creating Web services using Visual Studio .NET. Looks underneath the hood of the code created by VS.NET. (October 15th, 2003)
Part 3 - Examines creating a client application that consumes a Web service. Discusses the purpose and structure of a WSDL document, along with creating and using proxy classes to consume a Web service. (November 5th, 2003)
Part 4 - Examines the utility of Web services and common scenarios where Web services make sense. A business-oriented look at Web services. (November 19th, 2003)
Part 5 - Takes an in-depth look at XML serialization, which is the process of converting a data type, such as an integer, array, or custom class, into its XML representation, and back again. Every time a message is passed to or from a Web service, XML serialization transpires. (December 17th, 2003)
Part 6 - Looks at sending metadata to a Web method through the use of SOAP headers. Examines defining and accepting a SOAP header on the Web service end, and looks at sending a populated SOAP header from the client. (December 31st, 2003)
Part 7 - Examines how the incoming and outgoing messages to a Web service can be programmatically modified via SOAP Extensions. (January 21st, 2004)
Part 8 - Learn about the Web Service Enhancements (WSE) and Microsoft's free class library for implementing"

Some remoting references

REF-1 .NET Remoting Customization Made Easy by Motti Shaked
REF-2 MSDN online: Remoting Example: Hosting in Internet Information Services (IIS)

REF-3 MSDN online: Remote Object Configuration

REF-4 MSDN online: Asynchronous Programming Overview

REF-5 Other MSDN references:
'Asynchronous Delegates Programming Sample'
'Asynchronous Remoting'
'Asynchronous Programming Overview'
'Lifetime Leases'
REF-6 SoapSuds vs. Interfaces in .NET Remoting by Ingo Rammer


REF-7 Hosting Remote object in IIS � A Remoting sample by Sandeep Alur

REF-8 MSDN online: Remoting Example: Lifetimes

REF-9 Remoting Tutorials

  

15 Seconds : Web Services Security in The .NET Framework: "ASP.NET Impersonation
An understanding of ASP.NET impersonation is important before going into the details of authorization and authentication. Therefore, first we will discuss ASP.NET impersonation in this section.
Before delving into the details of ASP.NET impersonation, I would like to clarify one important point that many folk are not aware of. Actually there is one instance of aspnet_wp.exe per processor that serves all the Web applications hosted on a box. This worker process always runs under the security context defined by the tag. The aspnet_wp.exe creates a separate thread, called worker thread, for servicing each client request. We have to distinguish between the server process and the worker threads in order to understand the impersonation and security details of ASP.NET.
With ASP.NET impersonation, the thread servicing the client request can optionally execute with the identity of the client. Let me explain it in detail.
IIS always maps a user request to some Windows account; in case of anonymous access, this is IUSR_machinename account or any other account that has been defined to be used with anonymous access; in the case of Windows authentication, this is the account whose credentials are provided by the Web site user. After successful authentication, IIS forwards this logged-in user's identity to the ASP.NET worker thread. Now the ASP.NET worker thread has the following three options:
It can run under the identity defined by the tag.
It can run under the client identity passed to it by IIS.
It can run under the identity of the user whose credentials have been listed for impersonation.
Now the decision depends on the impersonation settings for the ASP.NET application.
If impersonation is enabled and any specific Windows account ha"