08.01.2015 Views

Beginning Web Development, Silverlight, and ASP.NET AJAX

Beginning Web Development, Silverlight, and ASP.NET AJAX

Beginning Web Development, Silverlight, and ASP.NET AJAX

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

156<br />

CHAPTER 7 ■ .<strong>NET</strong> 3.0: WINDOWS COMMUNICATION FOUNDATION<br />

WCF <strong>and</strong> Productivity<br />

As mentioned earlier, there are many technologies available for building distributed<br />

applications. From Microsoft alone, you can use COM+, .<strong>NET</strong> Enterprise Services,<br />

MSMQ, .<strong>NET</strong> Remoting, <strong>Web</strong> Services, <strong>and</strong> <strong>Web</strong> Services Enhancements (WSE), to name<br />

just a few. Each of these requires different domain knowledge <strong>and</strong> different programming<br />

skills.<br />

WCF incorporates all of these into a single programming model, reducing this overall<br />

complexity <strong>and</strong> making it easier for the developer to focus on the business logic that you<br />

are paid to produce. Additionally, this allows you to combine each of these technologies<br />

into an application in ways that may not be possible today. As you work through this<br />

chapter, you’ll see how, through configuration changes in .config files, you will be able<br />

to finely control different services that may have required reams of code before WCF!<br />

Figure 7-1 shows the pre-WCF stack of technologies that can be used to build connected<br />

applications.<br />

These technologies are described in the following list:<br />

ASMX <strong>Web</strong> Services: You’ve used this throughout this book. It is a technology that<br />

makes web services easy to implement <strong>and</strong> deploy. It includes the basic <strong>Web</strong> Services<br />

technology <strong>and</strong> interoperability stack, allowing for stateless connected applications<br />

that use SOAP to communicate with clients <strong>and</strong> servers on Microsoft or other technology<br />

stacks.<br />

WSE: As web services have evolved, so have the st<strong>and</strong>ards that implement them. New<br />

requirements have brought about new st<strong>and</strong>ards in security, addressing, <strong>and</strong> more.<br />

Microsoft continually updates WSE to bring these st<strong>and</strong>ards to ASMX services.<br />

Messaging: The System.Messaging namespace in the .<strong>NET</strong> Framework allows programmatic<br />

access to Microsoft Message Queuing (MSMQ). This allows developers to build<br />

messaging-oriented middleware applications where reliable delivery of messages<br />

between systems is paramount.<br />

Remoting: The System.Remoting namespace in the .<strong>NET</strong> Framework allows object<br />

sharing across the network, giving remote users access to application classes,<br />

objects, <strong>and</strong> more. This also provides location transparency, easing distributed<br />

application development.<br />

Enterprise Services: The System.EnterpriseServices namespace in the .<strong>NET</strong> Framework<br />

allows programmatic access to a set of classes that allow you to build<br />

enterprise-grade applications that use COM+ to support critical systems<br />

functionality such as transactions.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!