Sams Teach Yourself .Net in 21 Days

By Jason Beres

• Table of Contents
  • Copyright
  • About the Author
  • About the Technical Editor
  • Acknowledgments
  • We Want to Hear from You
  • Introduction
  • Week 1: At a Glance
  • Day 1. Introduction to the Microsoft .NET Framework
  • Day 2. Introduction to Visual Studio .NET
  • Day 3. Writing Windows Forms Applications
  • Day 4. Deploying Windows Forms Applications
  • Day 5. Writing ASP.NET Applications
  • Day 6. Deploying ASP.NET Applications
  • Day 7. Exceptions, Debugging, and Tracing
  • Week 1. In Review
  • Week 2: At a Glance
  • Day 8. Core Language Concepts in Visual Basic .NET and C#
  • Day 9. Using Namespaces in .NET
  • Day 10. Accessing Data with ADO.NET
  • Day 11. Understanding Visual Database Tools
  • Day 12. Accessing XML in .NET
  • Day 13. XML Web Services in .NET
    • What Are XML Web Services?
    • Creating Your First Web Service
    • Consuming XML Web Services
    • Summary
    • Q&A
    • Quiz
    • Exercises
  • Day 14. Components and .NET
  • Week 2. In Review
  • Week 3: At a Glance
  • Day 15. Writing International Applications
  • Day 16. Using Macros in Visual Studio .NET
  • Day 17. Automating Visual Studio .NET
  • Day 18. Using Crystal Reports
  • Day 19. Understanding Microsoft Application Center Test
  • Day 20. Using Visual SourceSafe
  • Day 21. Object Role Modeling with Visio
  • Week 3. In Review

Q&A

1. Web services are cool. Are they efficient? It seems like a lot of XML coming down the pipe.

   Web services are a little chunky in file size. The main benefit of Web services is they are cross-platform and cross-language. If saving every bit of network bandwidth is an issue and you're running a complete Microsoft server and client solution, you should look at .NET remoting using binary TCP formatters. .NET remoting is highly efficient.

2. How does early binding occur? How does .NET know all the methods in the Web service?

   When you reference the ASMX file and add the WSDL to your solution, Visual Studio .NET creates a proxy class that's built in the language of your project and contains all the properties and methods that are read from the WSDL file. If you click the Show All Files button on the Solution Explorer toolbar, you'll see a Reference.Map file with the attached Reference.vb or Reference.cs file that contains the information that Visual Studio .NET needs to accomplish early binding.

3. I'm hungry for more! Where can I get hard-core Web services information?

   There are tons of great resources on the Web. Check the following links for examples and Web service information:

   http://www.msdn.microsoft.com/webservices/

   The At Your Service column on MSDN is also great:

   http://www.msdn.microsoft.com/library/default.asp?url=/library/en-us/dnservice/html/service09032002.asp

   Dan Wahlin also has great resources, including information about using the Google Search Web service and the Amazon.com Web services, at

   http://www.xmlforasp.net/content.aspx?content=codebank&codeType=webservices

Share This