Disco file in asp.net

Undesired Name? Append Query trying not to add duplicate records to new table. Follow us! Get the Latest Bytes Updates. By using this site, you agree to our Privacy Policy and Terms of Use. Arpan A Discovery file named "Calculator. Thanks, Arpan Sep 5 '06 Juan T. Llibre re: I have the. Thanks, Arpan Sep 5 '06 Arpan I have the.

Llibre re: I do have. Thanks, Arpan Sep 5 '06 This discussion thread is closed Start new discussion Replies have been disabled for this discussion. NET Framework Explainations of wsdl, disco, proxy 2 posts views Thread by microdevsolutions last post: by. Net website that use some webservices. Do I need to upload them on my webserver? I tried to remove the folder containing those files from the webserver, and the website happily continued to being able to use the webservice.

Anyway I'm not an expert about webservices. This is the first time I need to deploy something that use a webservice, so, please, take this answer "as-is" Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Ask Question. Asked 7 years, 7 months ago. DISCO can define a document format along with an interrogation algorithm, making it possible to discover the Web Services exposed on a given server.

This is an XML file that describes the web service. There are very few instances where someone writes this by hand, as each vendor has a tool to create it. Consider WSDL the contract for the service. Once published, you should not change exposed methods.

DISCO - discovery. This is the file that helps. NET discover local services. So what do you do? This is where web services help out. In short, Web Services are pieces of program logic that are programmatically available via the Internet. By allowing data interchange in the standard XML format, anybody can pick up the data and use it. Basically, you can author a web service and make its properties and methods available to other developers across the web, without writing vast amounts of documentation for an API or distributing DLLs to everyone who wishes to use them.

The service receives the request, processes it, and returns a response. An often-cited example of a web service is that of a stock quote service, in which the request asks for the current price of a specified stock, and the response gives the stock price. This is one of the simplest forms of a web service in that the request is filled almost immediately. A Web Service is defined as "a component of programmable application logic that can be accessed using standard web protocols".

It's basically a component, or an assembly in ASP. NET, that can be accessed over the web. The concept of sending messages between servers or remotely calling functions is not new. SOAP makes it possible for applications written in different languages running on different platforms to make remote procedure calls RPC effectively, even through firewalls.

SOAP calls use port 80, which makes it possible to call procedures that exist behind firewalls. We can use ASP. NET to create a web service on the. NET platform, and can be built using any. NET language.

The reasoning for choosing ASP. NET for this purpose is quite logical. We don't need to reinvent the plumbing -- that is, at a high level, the capability to serialize our data as XML, transport the data using HTTP, and de-serialize the XML back to meaningful data. Instead, we want a framework that makes building web services easy, allowing us to focus on the application logic, not the plumbing.

NET provides this framework for us. Building web services using ASP. Web services built using ASP. NET will have. It is the end point for accessing your web services. NET runtime when a request to the service is made.

How do you explain to others, the functions that your web service exposes and the parameters each function accepts? You might do it informally by writing a document that provides this information, or you might simply verbalize it for someone who needs to invoke your web service. This informal approach has at least one serious problem: When a developer sits down to build a client for your web service, his development tool for example, Visual Studio.

NET cannot offer him any help, because that tool has no idea about the web service's functions and parameters. Providing a formal description in a machine-readable format solves this problem. Every web service must have a WSDL. The WSDL supplies the detailed information about the web service's functionality and how to access this functionality, to the clients.

You can access a web service from within an application, by creating a web service proxy class. The Microsoft. The word "consume" in this context means, to use the web service, to call the web service and to send it the appropriate information as parameters, to receive information back from the web service formatted as SOUP message, and then to be able to display that information.

Using Wsdl. The proxy class encapsulates all the complexities of calling a web service, so that you as the consumer of the web service don't have to know SOUP, don't have to know where the web service resides, don't have to know anything about how to take XML message and deserialize it into a set of classes.

All that you have to know is, this is actually all done for you by the proxy class. Basically what you can say is, a proxy class serves as an intermediate between the web service provider and the web service consumer. So whenever the client application calls a web service method, the application actually calls a corresponding method in the proxy class. This method takes the name of the web service method that is being called and its arguments, and then formats them so that they can be sent as a request in a SOAP message.

The web service receives this request and executes the method call, sending back the result as another SOAP message. When the client application receives the SOAP message containing the response, the proxy class decodes it and formats the results so that the client application can access them. The information is then returned to the client.

The proxy class has the same methods and properties of the web service class, but it it does not contain the actual implementation. It simply acts as a 'go-between' your code and the web service, so that you don't have to deal with the complicated details of the web service in XML. The proxy class contains methods that can make either synchronous or asynchronous calls to web services. Synchronous methods are represented by the name of the actual method call, and asynchronous methods are represented by the name of the method call preceded by Begin and End.