References in Visual C#

Maker PDF-417 2d barcode in Visual C# References

PDC 2003 Sessions Session slides and downloads from PDC 2003 Located at MSDN Home PDC 2003 - PDC Central Agenda and Sessions Sessions

List of Books on Building Web Services Using .NET Web Services Developer Center This page lists books about Web services in general and about building Web services using .NET in particular. Located at MSDN Home Web Services Home Understanding Web Services Books

Newsgroups Related to Web Services, Web Services Enhancements, and Indigo microsoft.public.dotnet.framework.webservices microsoft.public.dotnet.framework.webservices.enhancements microsoft.public.windows.developer.winfx.indigo Find more newsgroups at MSDN Home MSDN Newsgroups.

http://msdn.microsoft.com/newsgroups/default.aspx dg=microsoft.public .dotnet.framework.webservices.enhancements

Orchestrating XML Web Services and Using the Microsoft .NET Framework with Microsoft BizTalk Server Ulrich Roxburgh (Microsoft) Whitepaper (February 2002) Located at MSDN Home MSDN Library Enterprise Development Windows Server System Microsoft BizTalk Server

Attributes MSDN Online Articles Provides an overview of Reflection attributes and custom attributes Located at: MSDN Home MSDN Library .NET Development Visual Studio .NET Visual Basic and Visual C# Reference Visual C# Language C# Language Specification

http://msdn.microsoft.com/library/default.asp url=/library/en-us/ cpguide/html/cpconaccessingcustomattributes.asp

SERVICE-ORIENTED ARCHITECTURE (SOA) represents a new and evolving model for building distributed applications. Services are distributed components, which provide well-defined interfaces that process and deliver XML messages. A servicebased approach makes sense for building solutions that cross organizational, departmental, and corporate domain boundaries. A business with multiple systems and applications on different platforms can use SOA to build a loosely coupled integration solution that implements unified workflows. The concept of services is familiar to anyone who shops online at an eCommerce web site. Once you have placed your order, you have to supply your credit card information, which is typically authorized and charged by an outside service vendor. Once the order has been committed, the eCommerce company then coordinates with a shipping service vendor directly to deliver your purchase. ECommerce applications provide another perfect illustration of the need for a service-oriented architecture: If the credit card billing component is offline or unresponsive, then you do not want the sales order collection process to fail. Instead, you want the order collected and the billing operation to proceed at a later time. Figure 1-1 provides a conceptual workflow for an eCommerce business that uses multiple services to process orders.

1

Figure 1-1. Service-based workflow for an eCommerce business SOA is like other distributed architectures in that it enables you to build applications that use components across separate domain boundaries. SOA uses Web services as application entry points, which are conceptually equivalent to the proxy and stub components of traditional component-based distributed systems, except that the interactions between the Web service provider and consumer are more loosely coupled. SOA is also unique in that it incorporates those factors that are critically important to business: service reliability, message integrity, transactional integrity, and message security. In the real world, business cannot rely on services that may process requests if they receive a request that they can understand. Businesses require more certainty than this. It is a given that disparate systems may be up or down at various times, or that different systems may differ in their responsiveness due to varying loads. However, none of this is an excuse for allowing service request messages to simply drop away into the void, or to go unanswered. Furthermore, there can be no ambiguity as to how a service must be called. If a system publishes its capabilities as a Web-enabled service, then it needs to clearly document how the service must be called. SOA will address many of the availability and scalability issues in today s applications. Most applications implement a rigid synchronous communication model with a linear workflow model that is highly susceptible to failures at any point in the workflow. SOA assumes that errors can and will occur, and so it implements strategies for handling them. For example, if a service fails to accept a message request the first time, the architecture is designed to retry the delivery. And if the service is entirely unavailable (which should never occur in a robust SOA), then the architecture is designed to avoid possible catastrophic failures that may disrupt the entire service request. SOA improves reliability because temporary failure in one part of the workflow will not bring down the entire business process.