Web Services Developer Center: Web Service Basics: XML Web Services Basics

Web Services Developer Center: Web Service Basics: XML Web Services Basics: "What Is an XML Web Service?
XML Web services are the fundamental building blocks in the move to distributed computing on the Internet. Open standards and the focus on communication and collaboration among people and applications have created an environment where XML Web services are becoming the platform for application integration. Applications are constructed using multiple XML Web services from various sources that work together regardless of where they reside or how they were implemented.
There are probably as many definitions of XML Web Service as there are companies building them, but almost all definitions have these things in common:
XML Web Services expose useful functionality to Web users through a standard Web protocol. In most cases, the protocol used is SOAP.
XML Web services provide a way to describe their interfaces in enough detail to allow a user to build a client application to talk to them. This description is usually provided in an XML document called a Web Services Description Language (WSDL) document.
XML Web services are registered so that potential users can find them easily. This is done with Universal Discovery Description and Integration (UDDI). "

Web Services Interoperability and Integration - New home for the Topic at MSDN

Web Services Developer Center: Web Services Interoperability and Integration: "Web Services Interoperability and Integration
Welcome to the Web Services Interoperability and Integration page on MSDN. This page is dedicated to providing you information for ensuring your Web services applications will work across different platforms and toolsets. "

Hey guys, check out this page at MSDN, a new one for the Webservices interoperability and related issues.

Web Services Developer Center: Web Services Protocol Workshops .. check out the page for latest in ur area

Web Services Developer Center: Web Services Protocol Workshops: "Web Services Protocol Workshops
Web Services Protocol Workshops (Workshops) are events that you can attend to learn about and give feedback on advanced Web Services protocol specifications (WS-* specs).
There are two types of Workshops: Feedback and Interop. In Feedback Workshops, the authors of a specification discuss the content of the specification and solicit feedback from attendees. In Interop Workshops, companies with implementations of a particular Web Service specification come together to test the interoperability of their implementations with others.
Although all companies (end users and vendors alike) are welcome to attend any Workshop, Interop Workshops are hands-on events primarily aimed at developers who are implementing specifications."

Web Services Developer Center: Management Specifications Index Page

Web Services Developer Center: Management Specifications Index Page: "Management Specifications Index Page
Brief
A key distributed application area is the management of systems and devices. Web services offer a strong foundation for building robust and interoperable systems management solutions"

This specification describes a general SOAP-based protocol for managing systems such as PCs, servers, devices, Web services and other applications, and other manageable entities.

Must read for every Developer in Dotnet...

Cutting Edge: Binary Serialization of DataSets -- MSDN Magazine, October 2004

Cutting Edge: Binary Serialization of DataSets -- MSDN Magazine, October 2004: "The ADO.NET DataSet object plays an essential role in most of today's distributed, multitiered applications. Instances of the DataSet class are used to move data across the tiers and to exchange data with external services. The DataSet has most of the features needed to represent real-world business entities.
First, the DataSet is a disconnected object�you can use it without a physical connection to the data source. In addition, the DataSet provides a rich programming interface. It supports multiple tables of data, accepts relations defined between pairs of tables, and allows you to enumerate its contents. Last but not least, the DataSet is a fully serializable object. It can be serialized in three different ways�to a standard .NET formatter, to an XML writer, and through the XML serializer."

SQL Server Developer Center: Using an ADO.NET DataSet as a Reporting Services Data Source

SQL Server Developer Center: Using an ADO.NET DataSet as a Reporting Services Data Source: "Reporting Services provides access to SQL Server, Oracle, ODBC, and OLE DB data sources as part of its standard features. For many reporting scenarios, connecting to a database and running a query is all that is needed to get all the information you need to report upon. But what happens if you want to use a DataSet as your data source? For example, maybe you already have a middle tier that processes your data to conform to your business logic and produces a DataSet as a result. Or maybe you don't, but you nonetheless want to manipulate your raw data prior to reporting in ways that are a better fit for a Microsoft Visual Basic or C# implementation than a SQL implementation, and a DataSet would be the logical end result of such processing. Well, fortunately, it is possible to do this. It is even relatively easy, once you work out what parts of the data processing extension interfaces really have to be implemented to wrap up a DataSet in a way that Reporting Services can use. "

Visual Basic Developer Center: Database Developer Corner: Calling

Visual Basic Developer Center: Database Developer Corner: Calling: "As most of you realize, converting your VB6 apps to the .NET platform isn't as simple as recompiling. Partly because of this, 'legacy' VB6 apps are likely to be with us for some time. Still, there's no impenetrable wall separating COM-based VB6 and .NET technology. COM Interop provides you backward compatibility, but you also have forward compatibility as well. In this month's column, Carl Ganz discusses two ways to take advantage of the power of .NET while still continuing to maintain your legacy VB6 apps.
Suppose you've created a class in a .NET assembly that retrieves data from a table and runs a series of complex calculations to produce, say, a salesperson's commission. This commission calculation class can service the .NET application it was designed for as well as your legacy application. Or, perhaps you needed to rewrite the legacy commission class and decided to do it in .NET. In the following example, we'll examine something much simpler than a commission calculation algorithm. Our sample class has two properties, First and Second, and one method, AddTogether (see Listing 1). "