Blog
Technologies in .NET
In this blog I will explain about the different types of technologies of .NET.
The technologies figuring most prominently in the .NET vision are six key protocols or technologies that the World Wide Web Consortium (W3C), the European Computer Manufacturers Association (ECMA), Microsoft, and IBM have already accepted or are currently considering as standards.
XML, the W3C standard for formatting structured data according to a set of rules, lies at the core of .NET. Configuration files use XML. Five namespaces in the .NET class library are devoted to creating and querying XML streams and documents. (A namespace is a string identifier, wrapping classes to reduce the potential of class name conflicts across multiple dynamic-link libraries or DLLs.)
Simple Object Access Protocol (SOAP), a proposed W3C standard built on XML, is designed to define communication between loosely coupled applications across any platform. .NET's Web services implement SOAP over Hypertext Transfer Protocol (HTTP) as the default protocol.
Web Services Description Language (WSDL), another proposed W3C standard, describes what functionality a Web service provides and what arguments and methods are available to the consumer.
Universal Description, Discovery and Integration (UDDI) is a means for providing a directory of Web services. It allows providers to advertise Web services and consumers to locate them. There are plans to submit this specification, which IBM and Microsoft have adopted, to a standards body in the future.
VB is the new and premier programming language of .NET. Heavily influenced by C++ and Java, it is a powerful, object-oriented language that will feel familiar to developers migrating from those languages. Proof of the elegance of vb will be evident through this book.
The Common Language Infrastructure (CLI), which is currently before the ECMA for acceptance, is an umbrella that covers the definition of .NET and numerous subspecifications that make up the comprehensive, robust framework. As this is the heart of the chapter, the CLI and its various components will be dealt with in detail in subsequent sections.