So here's the deal.
I'm attempting to use Visual Studio to connect to an AXIS web service. Unfortunately, the Web Service does not have a public WSDL file available on the server. I know the location of the Web Service, but it will not let me open the WSDL file from a browser.
Luckily, I do have a local copy of the WSDL file that the server is using. Now I know I can use SVCUTIL.EXE to build a class of the local WSDL file that can be accessed with Visual Studio. However, I need to know how to use the generated class to run services with the server.
Normally, I can use Visual Studio's "Data Source" tool to point it to the right web address and have it take care of the hard stuff, but because the server is trying to hide the web service, how do I connect Visual Studio to the server?
Specific examples in C# would be greatly appreciated.
Thank you very much.
I'd just host the wsdl on your local IIS... point the "Add Service Reference..." wizard at the WSDL hosted locally, then use the application's ".config" file to re-direct the service reference to the actual URL.
Related
I am trying to create a Web service client through Hosted wsdl file in visual studio but am unable to do it as am new to web services.
so does any one know, how to do this?
I tried it by adding service references.
also tried by Adding Command in Visual studio like
wsdl /l:CS /protocol:SOAP http://localhost/OIDServer/OIDServer.asmx?WSDL
but no use.
I have been through tons of threads and am unable to find the correct answer for my question. I have created a very simple WCF service on my development machine using visual studio 2010. The service works correctly when using VS to host it. I have even had success creating a small c# application to consume this service. However I now need to move this service to IIS on my work's development server. I have tried following several guides online but nothing has worked so far. Any help would be greatly appreciated.
if you are able to execute your wcf service using WCFTestClient successfully and not on IIS
that means problem is in endpoint configuration. I suggest have a look once again endpoint suggestions.
Using Web Deploy to publish from Visual Studio to a remote web server requires additional installation of Web Deploy on the server http://www.iis.net/learn/install/installing-publishing-technologies/installing-and-configuring-web-deploy
Visual Studio generates an output log during the web deploy publish that may have additional information on why it is failing. Sometimes there are permission issues to work through as well http://blogs.iis.net/krolson/archive/2009/11/04/using-iis-manager-accounts-for-web-deployment-tool-msdeploy-delegation.aspx
You can also generate a Web Deploy Package with Visual Studio and manually deploy it to the server http://msdn.microsoft.com/en-us/library/dd465323(v=vs.110).aspx
most of the time i add web reference of web service and give the path of asmx file but now i am using a UPS web service and may be this web service was developed by another technology. there is no any asmx file concept. they provide wsdl file and i just add the web reference and paste the file path of wsdl file there. i compile my project and got no error. my apps is running fine but when i create a setup project of that apps and install on another machine then i am getting object reference error. so i just do not understand why it is not running on another machine when i install it from setup but it is running fine when i run it from my machine IDE. so please guide me what i am missing. what i need to do when i will be working with wsdl and that will run fine on remote machine where wsdl file not exist.
Check if there is an App.config in your Setup project included where the link to your WSDL is set and check if you have that if the link to your WSDL exists on the PC where you are installing.
And if that does not work you can always try to convert the WSDL to a DLL with the help of this site.
Basically, I have a web Service which I developed. I then went down to the installation site to install the web Service and a handheld app which uses it.
Problem is, I came back off site, and now need to change some things with the handheld app and web Service, and send it to them (site is hundreds of miles away).
I can change the web service fine, but how can I change the web reference to that web service, on the handheld app? its pointing to a location that does not exists as there is no remote access to their servers.
How can I trick Visual Studio into updating the web reference to get my LOCAL objects, but compiling to keep the web reference that only exists on THEIR local servers?
You can configure the url that the webreference is using by setting it to dynamic. It will add the url to the config.
Also see: http://www.codeproject.com/KB/XML/wsdldynamicurl.aspx
I have a web service project and simple test application. I can debug the web service from Visual Studio 2008. However, there exist a real client application, but it is on another machine. ASP.NET Development Server does not allow connections if they are not from localhost, or so it seems. Is there a way to debug a web service, if client application is on another machine?
Edit
The tool that I used is Trace Utility from Microsoft SOAP Toolkit. Further explanation can be found here (works on XP; see continuation story for Windows 7 solution). There was problem with it though. My remote client fetches the WSDL first, and then creates URL based on values in soap tags found at the end of WSDL. So client gets redirected to localhost, which is not good.
I found my problem though, but I'll leave the question open until I find the time to try debugging via IIS.
Install a virtual directory into the IIS on your local machine. If you don't have IIS, install it. Once IIS is installed and configured on your local machine, you should be able to use either the IP or create a dns alias for that IP to access the web service that way.
I'm using SoapUI basic version to fake the SOAP requests to the web service, which is running in debug mode in Visual Studio, from the local computer.
You can use IIS (or Cassini Web server) - for debugging, attach VS 2008 to correct process (for example w3p.exe(IIS6 or greater) or aspnet_wp.exe(IIS 5)).