MSDN Code Gallery

The 64-bit versions of Windows 7 and Windows Server 2008 R2 support more than 64 Logical Processors (LP) on a single computer. New commodity systems are now appearing that leverage non-uniform memory access (NUMA) architectures. Within the near future, a system with 4 CPU sockets, 8 processor-cores per socket and with Simultaneous Multi-Threading (SMT) enabled per core, will achieve 64 Logical Processors. Many high-end server-class solutions may need to be architected with NUMA awareness in order to achieve linear performance scaling on such systems. Parallel Computing and High Performance Computing solution developers may also find NUMA awareness essential for performance scalability.

With the Windows Web Services API (WWSAPI), you can connect your C/C++ client applications with web services. You can also create C/C++ server-side web service end-points. WWSAPI is new with Windows 7 (client) and Windows Server 2008 R2 (server). WWSAPI is also back-ported to all formally supported versions of Windows (client and server). The WWSAPI runtime library (WebServices.dll) is a native-code implementation of WS-* family of protocols for SOAP based web services. WWSAPI enables several solution scenarios and benefits including: 1. Implement web services in native C/C++ code on both Windows client and server. C/C++ application developers have often requested this platform technology capability but were previously forced to write their own or interface their native-code solutions with managed-code wrappers. 2. Achieve interoperability with web services implemented using Windows Communication Foundation (WCF), ASP.NET XML Web Services, and even services implemented using non-Microsoft implementations of WS-* libraries. 3. Construct web services with minimal service startup time and minimal process working-set dependencies. 4. Use web services implementations in resource-constrained deployment environments. 5. Avoid native-management interop scenarios with potentially costly marshalling side-effects.

With the release of Windows Server 2008, the Server Core installation option was introduced. This new option made it possible to run only the base operating system along with a minimum of optional features and roles. Consequently, Server Core has become quite successful as a network services host OS. Windows Server 2008 R2 introduces further enhancements that enable Server Core to also be leveraged as an Application host OS. There are unique considerations to be aware of when developing applications intended to run on a Server Core installation of Windows Server 2008 R2. If you are a native-code developer (using primarily C/C++), you need to be sure that the machine in which the application will run has the necessary runtimes. Likewise, if you are a managed-code developer (using primarily C#/VB.NET), then you must be certain that the target machine has the required .NET Framework installed. For both, managed and unmanaged developers, it is also imperative to have the WoW64 execution layer if you will be using executable binaries that are 32-bit (with R2, Windows Server is now 64-bit only). In this segment, you will learn how to install various requirements that your applications may need in order to successfully execute.

Windows PowerShell is a Windows command-line shell designed for ease-of-use not only by system administrators but also for application and system developers. The shell includes an interactive prompt and a scripting environment that can be used independently or in combination. PowerShell V2 is available by default with both R2 and Windows 7 and, via an optional update, previous versions of Windows. For Developers specifically, Windows PowerShell in combination with the Windows Management Infrastructure (WinRM, WS-Management, WMI) provides a great way to automate server hosted solutions. For example, if you implement all your administration logic via PowerShell, then layer the MMC GUI over the top (i.e. MMC calls PowerShell to get the work done) - you will have given your Enterprise customers the absolute best of all worlds; GUIs, scripting, and delegated, remote automation. Unlike most scripting shells, which accept and return text, Windows PowerShell is integrated with the .NET Common Language Runtime (CLR) and the .NET Framework, and thus deals in .NET objects instead of just text strings. This fundamental change in the environment brings entirely new tools and methods to the management and configuration of Windows. Application Developers may extend their solutions with custom PowerShell based object models which integrate seamlessly with platform management solutions. Like many shells, Windows PowerShell gives you access to the file system on the computer. In addition, Windows PowerShell providers enable you to access other data stores, such as the registry and the digital signature certificate stores, as easily as you access the file system. Version 2 of Windows Powershell introduces an array of new features including remote sessions, an integrated script environment, debugging tools, and much more.

This resource page describes a sample near real time classification application that builds on the File Classification Infrastructure (FCI) in Windows Server 2008 R2. This sample tool uses public FCI api to demonstrate one possible way for implementing near real time classification solution. The code sample is developed using C# and Visual Studio 2008. The sample includes a Visual Studio project file that can be used to compile and run the code. This sample shows 3rd party developers how to interact with FCI in Windows Server 2008 R2 for the purposes of extending the inbox functionality. This sample functionality is targeted at enabling customers and partners to implement a complete end-to-end scenario with a little investment in code that builds on in-box FCI capabilities.