Share via

Working with ASP.NET Applications

  • Article

Working with ASP.NET Applications

This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.

Microsoft® ASP.NET is the next version of ASP and provides a new programming model and infrastructure for building scalable, secure, and stable applications. ASP.NET is a compiled environment based on the Microsoft .NET Framework and applications can be authored in any .NET-compatible programming language, including Microsoft C# and Microsoft Visual Basic® .NET.

The functionality of Collaboration Data Objects (CDO) Component Object Model (COM) components, CDO for Exchange 2000 Server (CDOEX), CDO for Exchange Management (CDOEXM), and CDO for Workflow (CDOWF), can be exposed to ASP.NET applications through the COM interoperability feature of the .NET Framework. The CDO COM components can also be exposed to remote applications and users through XML Web services.

By default, the worker process for ASP.NET (Aspnet_wp.exe) runs under the local machine account to restrict access to domain resources and provide a more secure environment. This will cause an error if you try to run or debug an ASP.NET application on a domain controller or a backup domain controller. On a domain controller, all user accounts are domain accounts and not local machine accounts, so Aspnet_wp.exe fails because it cannot find a local account named "localmachinename\ASPNET".

The following sections discuss:

Using XML Web Services on Exchange

Running ASP.NET on a Domain Controller

Send us your feedback about the Microsoft Exchange Server 2003 SDK.

Build: June 2007 (2007.618.1)

© 2003-2006 Microsoft Corporation. All rights reserved. Terms of use.