| .NET My Services and Visual Studio .NET |
| MSDN |
| Visual Studio .NET allows you to create .NET My Services clients quickly and easily by handling the actual interaction with the Web Service on your behalf, allowing you to maintain a high-level view of your application and not have to dig down into the actual XML data that's being passed around. In order to appreciate the value that Visual Studio .NET brings to the development process, it helps to take a closer look at the protocols used by .NET My Services and other Web Services, and the costs of handling these protocols manually. |
|
| An introduction to Web Service Security using WSE - Part I |
| The Code Project |
| This article explains the first steps to build secure Web Services. It introduces the WSE specification and a first authenication mechnism based on username identifiction and password validation. |
|
| An introduction to Web Service Security using WSE - Part I |
| The Code Project |
| This article explains the first steps to build secure Web Services. It introduces the WSE specification and the easiest authentication mechanism based on username identification and password validation. |
|
| ASP.NET Web Service |
| The Code Project |
| We can now use ASP.NET to create Web Service that is based on industrial standards included XML, SOAP and WSDL. This is a basic introduction to building Web services. |
|
| Authentication of a Web Service Using Microsoft .NET Passport |
| MSDN |
| This article discusses the issues encountered during the development of the authentication component for the ColdStorage sample Web services |
|
| Consuming an XML Web Service |
| DotNetJunkies |
| An XML Web Service consumer is an application that invokes the methods of an XML Web Service made available by a provider; the consumer feeds on the data derived from the XML Web Service provider. A consumer application may be another Web application, XML Web Service, Windows desktop application, or any other type of application with access to the XML Web Service using HTTP. |
|
| Consuming an XML Web Service |
| DotNetJunkies |
| An XML Web Service consumer is an application that invokes the methods of an XML Web Service made available by a provider; the consumer feeds on the data derived from the XML Web Service provider. A consumer application may be another Web application, XML Web Service, Windows desktop application, or any other type of application with access to the XML Web Service using HTTP. |
|
| Creating a Custom Web Control To Consume an XML Web Service |
| 15 Seconds |
| This article provides you with instructions on how to use a simple text editor and the DOS prompt to create a Web server control that gets its data from an eXtensible Markup Language (XML) Web service and simply displays the results on the page. This is very useful since the actual Web server control is a single package. All you need to do is provide people with your assemblies (.DLL files), and then they can simply drag and drop your Web server control onto their pages and the control will take care of the rest. This makes for a very modular approach at site design because it encapsulates many of the redundant tasks normally encountered when developing any type of Web application. |
|
| Implementing NTLM Authentication for Your ASP.NET Web Services |
| DotNetJunkies |
| Everybody knows that you can't prompt a user for authentication when accessing a Web service. But like many things that "everybody knows", it ain't necessarily so, as this article explains. |
|
| Improve XML Web Services' Performance by Compressing SOAP |
| DotNetJunkies |
| In this article, Mike covers compression of SOAP messages, using in-memory data compression, that are transferred over a network during an XML Web service request/response cycle. XML/SOAP is a text stream that can be compressed up to 80%, substantially decreasing the amount of data transferred, making this a viable solution in a variety of applications. |
|
| Integrating an HTML returning C# Web Service with our Websites |
| C#Today |
| In this article, Andrew Krowczyk discusses a relatively simple but useful Web Service that fulfills the following scenario. Lets say for example, Yahoo decided to write a Web Service that would allow anyone with a website to integrate a Recent News box into their own site. The data would be generated by Yahoo or its Content Provider, but would add the capability for anyone to encapsulate this piece of functionality into their own site seamlessly. As Andrew shows us, this is quite easy to do using .NET Web Services. |
|
| Interoperating Java, VB6, and .NET Web Services |
| C#Today |
| In this article, Catalin Tomescu illustrates the integration and interoperability of web services. He creates a Tax Calculator web service, which integrates two existing applications: a State Tax Calculator and a Federal Tax Calculator. To further complicate things, the two web services that our tax calculator integrates are built using different technologies the state tax calculator application is built using Apache SOAP for Java and the federal tax calculator application is built using Visual Basic 6.0 and the MS SOAP 2.0 Toolkit. Finally, we see how to call our Tax Calculator web service from a variety of clients - a C# console application, a VB 6 console application, and an ASP.NET web application. |
|
| Licensing Your ASPNet Web Services |
| DotNetJunkies |
| While ASP.Net makes building powerful SOAP based web services quick and easy, their usefulness in a business context is limited until one can effectively license those web services. Licensing requires the ability to examine each method invocation, determine whether or not the call is being made by a valid client and then reject or allow the call based on that determination. This article will explain one way to use Visual Studio .Net to tackle this issue. Specifically, we’ll explore using a combination of cu |
|
| New Features for Web Service Developers in Beta 1 of the .NET Framework 2.0 |
| MSDN |
| Check out the improvements in productivity, performance, extensibility, and standards support in Microsoft .NET Framework 2.0. |
|
| Regasm2.exe - The .Net/COM+ Installation Tool |
| The Code Project |
| This article describes how to design, build and install .Net Application into the COM+ Catalog without using the ServicedComponent class in your application. The solution shows retrieving the assembly and class attributes (included custom) from the assembly file and their storing into the COM+ Catalog Objects using the C# language. |
|
| Reliable XML Web Services |
| MSDN |
| Among the various FAQs about building XML Web services, reliability falls into the top five issues facing developers implementing decentralized Web services. The problem space, when broken down into small pieces, is not that difficult. So, this month I decided to jump off into the extreme area of building reliable XML Web services. |
|
| Retrieving Data from Web Services using Standard HTTP 1.1 Compression |
| DotNetJunkies |
| HTTP 1.1 protocol introduced standard ways of compression using gzip or deflate algorithms supported by web servers. Initial tests shown that average compression ratio 10:1 can be easily achieved with large SOAP messages (for instance ADO.NET DataSets with multiple rows). Such reduction of data size cannot be ignored - it's not 10 nor 20 percent but 90% of data size that can be reduced. |
|
| Retrieving Data from Web Services using Standard HTTP 1.1 Compression |
| DotNetJunkies |
| This very interesting article demonstrates how to reduce network bandwidth while using Web Services by using standard HTTP 1.1 compression techniques. |
|
| Using the Web Services and COM+ Event System in the .Net Application |
| The Code Project |
| This article describes how to integrate the Web Services into the COM+ Event System in the .Net Application using the C# language. I am using a simple example of the Web Services in the Publisher/Subscriber scenario, which it will publish the Log Message to the subscriber. |
|
| Using Web Services for Remoting over the Internet |
| The Code Project |
| This article describes a design and implementation (C#) of the Remoting over Internet using the Web Service as a gateway into the Remoting infrastructure. The Web Service Gateway (Custom Remoting Channel) allows to enhance the remoting channel over Internet and its chaining with another heterogeneous channel. Consuming a remote object over Internet is full transparently and it doesn't require any special implementation from the remoting via intranet. The Web Service Gateway enables to create a logical model of the connectivity between the different platforms and languages. Before than we will go to its implementation details, let's start it with usage and configuration issue. For some demonstration purpose I will use a MSMQ Custom Remoting Channel (MSMQChannelLib.dll), which I described in my previously article [1]. I am assuming that you have a knowledge of the .Net Remoting and Web Service. |
|
