The .NET Framework enables developers to create great Web applications with the help of ASP.NET and other technologies. Integrated into the Windows Server 2003 Family, the .NET Framework is the infrastructure for .NET. The .NET Framework incorporates the common language runtime and a unified set of class libraries that include Windows Forms, ADO.NET, ASP.NET, and other capabilities. Language-neutral, the .NET Framework lets developers build applications and services in virtually any programming language, including Visual C++, Visual Basic JScript, and Visual C#. The .NET Framework provides a fully managed, protected, and feature-rich application execution environment, simplified development and deployment, and seamless integration with a wide variety of programming languages. Note: This feature is not available in 64-bit versions of the Windows Server 2003 Family.
The Application Verifier tool tests and verifies application functionality running on an operating system, helping administrators to identify potential issues before migration. The Application Verifier detects subtle issues, such as heap corruptions and compatibility issues.
ASP.NET is the engine for Web-based applications and XML Web services and is part of the class library in the .NET Framework. It brings rapid application development to the server. ASP.NET pages use a compiled, event-driven programming model that improves performance and enables the separation of application logic and user interface.
Internet Information Services (IIS) 6.0 takes advantage of operating system settings to support bandwidth throttling. Administrators can now enable throttling for individual host-header sites, which allows IIS 6.0 to send responses for a given site in parallel. By contrast, IIS 5.0 serialized each response.
The common language runtime is a software engine that provide a more secure runtime environment by reducing the number of bugs and security holes caused by common application-programming errors. As a result, applications become more reliable, fewer vulnerabilities remain for malicious attackers to exploit, and the environment is better protected against untrustworthy code from outside sources. When a piece of code is ready to run, the common language runtime ensures that it can run without error, verifies that the current security permissions are appropriate for it to run, and makes sure that the code does not carry out any actions that are inappropriate. Note: This feature is not available in 64-bit versions of the Windows Server 2003 Family.
A new Compatibility Mode feature ensures out-of-box compatibility for many popular applications. Compatibility Mode technology provides an environment that more closely reflects the behavior of Windows 95, Windows 98, Windows NT 4.0, or Windows 2000 operating systems. These modes resolve several of the most common issues that prevent older applications from working correctly. Applications experiencing problems after migration benefit from starting in one of these compatibility environments. Advanced users can also take advantage of this technology to create solutions for their own applications.
Component Services is a set of services based on extensions of the Component Object Model (COM) and on Transaction Server (an earlier release of a component-based transaction processing system). Component Services provides threading and security, transaction management, object pooling, queued components, and application administration and packaging.
The euro is now used as the default currency symbol for users selecting the Euro setting. Earlier country and regional currency symbols are available but require user action.
Indexing Service provides a fast way for users to search for information locally or on the network. Users can search in files in different formats and languages, either through the Search command on the Start menu or through HTML pages that they view in a browser.
Internet Information Services (IIS) 6.0 is a full-featured Web server that provides the foundation for Web-based applications and XML Web services in Windows Server 2003 R2. IIS 6.0 offers a dedicated application mode, which runs all application code in an isolated environment. IIS 6.0 also supports Web gardens, in which a set of equivalent processes on a computer each receive a share of the requests normally served by a single process, achieving better multiple-processor scalability.
The Message Queuing feature helps developers build and deploy applications that run more reliably over networks, including the Internet. Applications that support message queuing can interoperate with a variety of applications running on different platforms, such as mainframe computers and UNIX-based systems.
Non-Uniform Memory Access (NUMA) features ensure that memory accesses are local to a node wherever possible and limit any software degradation caused by the NUMA architecture. As processor clock rates continue to increase and put pressure on processor bus architectures, scaling is addressed by implementing multiple processor buses. This approach can result in an architecture consisting of processors and memory arranged in smaller subsystems called nodes. Processor access time to memory in other nodes is longer than access time to memory in the same node. As a result, non-uniform memory access occurs across the system, which is the origin of the NUMA architecture name. The longer access times to other nodes can create software performance degradation. NUMA support in Windows Server 2003 R2 allows the operating system to limit degradation by scheduling threads from the same process on processors that are in the same node and allocating all memory requests within the same node as the proc
Telephony Application Programming Interface 3.1 (TAPI 3.1) unifies IP and traditional telephony to enable developers to create computer telephony applications that work as effectively over the Internet or an intranet as they do over a traditional telephone network.
Universal Description, Discovery, and Integration (UDDI)
Universal Description, Discovery, and Integration (UDDI) is an industry specification for publishing and locating information about Web services. Some products in the Windows Server 2003 Family include UDDI Services, a Web service that provides UDDI capabilities for use within an enterprise or across organizations. UDDI Services is not included with Windows Server 2003 R2, Web Edition. In addition, Windows Server 2003 R2, Standard Edition, supports only stand-alone installations of UDDI services. Distributed installation support is available with Windows Server 2003 R2, Enterprise Edition, and Windows Server 2003 R2, Datacenter Edition. In a stand-alone installation of UDDI services, both the UDDI Web server component and the UDDI database component are installed on a single server. In a distributed installation, UDDI components are distributed across multiple servers.
In Internet Information Services 6.0 (IIS), a Web garden is an application pool with multiple worker processes that serve the requests routed to that pool. Web garden affinity can be configured among the worker processes serving the pool and a given set of processors on a multiple-processor computer. Through the use of Web gardens, Web applications become more scalable, because a software lock does not block all processors in the multiple-processor computer. If one worker process serving an application pool experiences a shutdown, other work processes remain available to serve content and take over for the locked worker process.
Winsock Direct is now available in all versions of Windows Server 2003 R2. Applications that use Winsock perform faster and with less overhead when they communicate across a system area network. When a system area network in place, Winsock Direct streamlines communications among distributed components.
;
imageSwap(Img1,"/windowsserver2003/images/collapse.gif","/windowsserver2003/images/expand.gif","Collapse","Expand")
){kind=link}
;
imageSwap(Img2,"/windowsserver2003/images/collapse.gif","/windowsserver2003/images/expand.gif","Collapse","Expand")
){kind=link}
;
imageSwap(Img3,"/windowsserver2003/images/collapse.gif","/windowsserver2003/images/expand.gif","Collapse","Expand")
){kind=link}
;
imageSwap(Img4,"/windowsserver2003/images/collapse.gif","/windowsserver2003/images/expand.gif","Collapse","Expand")
){kind=link}
;
imageSwap(Img5,"/windowsserver2003/images/collapse.gif","/windowsserver2003/images/expand.gif","Collapse","Expand")
){kind=link}
;
imageSwap(Img6,"/windowsserver2003/images/collapse.gif","/windowsserver2003/images/expand.gif","Collapse","Expand")
){kind=link}
;
imageSwap(Img7,"/windowsserver2003/images/collapse.gif","/windowsserver2003/images/expand.gif","Collapse","Expand")
){kind=link}
;
imageSwap(Img8,"/windowsserver2003/images/collapse.gif","/windowsserver2003/images/expand.gif","Collapse","Expand")
){kind=link}
;
imageSwap(Img9,"/windowsserver2003/images/collapse.gif","/windowsserver2003/images/expand.gif","Collapse","Expand")
){kind=link}
;
imageSwap(Img10,"/windowsserver2003/images/collapse.gif","/windowsserver2003/images/expand.gif","Collapse","Expand")
){kind=link}
;
imageSwap(Img11,"/windowsserver2003/images/collapse.gif","/windowsserver2003/images/expand.gif","Collapse","Expand")
){kind=link}
;
imageSwap(Img12,"/windowsserver2003/images/collapse.gif","/windowsserver2003/images/expand.gif","Collapse","Expand")
){kind=link}
;
imageSwap(Img13,"/windowsserver2003/images/collapse.gif","/windowsserver2003/images/expand.gif","Collapse","Expand")
){kind=link}
;
imageSwap(Img14,"/windowsserver2003/images/collapse.gif","/windowsserver2003/images/expand.gif","Collapse","Expand")
){kind=link}
;
imageSwap(Img15,"/windowsserver2003/images/collapse.gif","/windowsserver2003/images/expand.gif","Collapse","Expand")
){kind=link}
;
imageSwap(Img16,"/windowsserver2003/images/collapse.gif","/windowsserver2003/images/expand.gif","Collapse","Expand")
){kind=link}