oreilly.comSafari Books Online.Conferences.


AddThis Social Bookmark Button

Understanding WinFX in Longhorn
Pages: 1, 2, 3

Primary Application Models

The Primary Application Models describe the type of applications you can build, which include:

  • Windows client applications
  • Web applications and web services
  • Data systems
  • Mobile applications
  • Console applications and Windows services

Client Applications

As shown in Figure 4, the Client Applications model contains two main namespaces, System.Windows and System.Windows.Forms. If you are a .NET developer, you should be familiar with the System.Windows.Forms namespace, which allows you to write generic Windows applications using Windows Forms. In Longhorn, you can leverage on the new presentation subsystem known as Avalon, through the System.Windows namespace.

Figure 4
Figure 4. Namespaces for client applications.

Web Applications and Web Services

For ASP.NET web applications and web services, you use the System.Web namespace (see Figure 5). In Longhorn, a new, web-services technology known as Indigo is available. Both types of applications share the same namespace.

Figure 5
Figure 5. Namespace for web applications and web services.

Data Systems

The next-generation Windows File System is known as WinFS and you can programmatically access the file system through the System.Storage namespace (see Figure 6). For database access, you can use the System.Data.SqlServer namespace to connect to the next release of SQL Server, code-named Yukon. (Yukon has since been renamed to SQL Server 2005 to better reflect its release date).

Figure 6
Figure 6. Namespaces for WinFS and SQL Server 2005.

Mobile Applications

For mobile applications, you can use the System.Windows.Forms namespace (.NET Compact Framework) for devices like Pocket PC (see Figure 7). You can also use the System.Windows namespace for special mobile PCs (such as the Tablet PC).

Figure 7
Figure 7. Namespaces for mobile applications.

Command Line and Windows Services

If you are writing console applications, you can use the System.Console namespace. For Windows Services (previously known as NT Services), you use the System.ServiceProcess namespace (see Figure 8).

Figure 8
Figure 8. Namespaces for console and Windows Services.

Pages: 1, 2, 3

Next Pagearrow