Forgo the command-line wsdl. Exe utility - it's much easier in Visual Studio itself. If you're using VS 2008 or later, right-click on your project, select Add Service Reference and point it to the WSDL on the server you'll be connecting to (e.
G blahblah.com/service.asmx?WSDL ) and it will generate the proxy classes and connection parameters in an app. Config file.
Forgo the command-line wsdl. Exe utility - it's much easier in Visual Studio itself. If you're using VS 2008 or later, right-click on your project, select Add Service Reference and point it to the WSDL on the server you'll be connecting to (e.g. blahblah.com/service.asmx?WSDL) and it will generate the proxy classes and connection parameters in an app.
Config file. From where you are, instantiate an object of the proxy class it generated (make sure the namespace it generated is included with a using statement) and make sure it is bound to an endpoint: BasicHttpBinding binding = new BasicHttpBinding(BasicHttpSecurityMode. None); binding.
MaxReceivedMessageSize = int. MaxValue; EndpointAddress address = new EndpointAddress("http://webservices.blahblah.com/service.asmx"); MyService service = new MyServiceClient(binding, address); and then invoke the remote methods on it: try { service. DoSomething("someParameter"); if (service.GetSomeStatus()) { } } finally { (service as IDisposable).Dispose(); } For VS 2005 or earlier, use Add Web Reference and the rest of the procedure is similar.
Thank you for the awnser, but I can't do it in this way because I don't have the URL to where im going to connect my web service. – ben Nov 4 '10 at 15:31 Gotcha. Then rewind somewhat and let me rephrase.
Consider using svcutil. Exe over wsdl. Exe, but that will be what you need to use, only having a file with WSDL in it.
The problem at this point will be that you can't execute the web service without knowing your endpoint (URL) connection at some level. How are you expecting the service call to execute? – Jesse C.
Slicer Nov 4 '10 at 15:57 Isnt it possible to create public web services where anyone can connect to it? Then its impossible to know the endpoints URL? Maybe I forgot to tell you that I'm the server that's going to recieve calls and not the client.
– ben Nov 4 '10 at 16:13 On that note, you're not needing to generate a client proxy with svcutil or wsdl - that's up to the people calling your web service. Once you write your service and publish it somewhere (you need to put it on a server somewhere, there's not just a public place for web services to be dropped, AFAIK), your users will know that somewhere and connect to it. – Jesse C.
Slicer Nov 4 '10 at 16:21.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.