Quite clearly when I said "app.config" I meant "web.config" - but what I posted above is the correct way to change the Web Service URI Endpoint behaviour from being hardcoded to being stored in a *.config file.
On Fri, Jan 22, 2010 at 7:04 AM, Brandon Betances <[email protected]> wrote: > You guys gotta pay attention: 1.) he said hes using asp.net so he wont have > an app.config file. 2.) guy about u pretty much said that. > > if the iis server is on another box you might want to change the uri of the > service to the server thats actually running the service. it probably > shouldnt be localhost anymore, or might not have that exact path > > On Thu, Jan 21, 2010 at 10:11 AM, Shameem A. Sathar Thalapurath > <[email protected]> wrote: >> >> Hello, >> Change in web.config file. >> >> Best Regards, >> Shameem >> >> > Date: Wed, 20 Jan 2010 23:50:15 -0800 >> > Subject: [DotNetDevelopment] web reference not working >> > From: [email protected] >> > To: [email protected] >> > >> > Dear all hope you all doing well , >> > >> > We've implemented some SOAP client code on our ASP.NET site that calls >> > up a remote service. Implementation was basically done by using Visual >> > Studio "Add Web Reference" wizard. >> > >> > Code works perfect locally (from Visual Studio), but fails on >> > production web server with >> > error : " An error occurred while trying to make a request to URI >> > http://localhost:3943/signdoc/InkToPng.asmx . This could be due to >> > attemptig to access a server in a cross domain way wothout a proper >> > cross donain >> > policy in place or policy that is unsuitable for SOAP service. " >> > >> > how can i change this locally added web reference so that it can work >> > on remote site where the site is uploaded. >> > >> > Thanks & Regards, >> > Mr. shrinivas mada >> >> ________________________________ >> Your E-mail and More On-the-Go. Get Windows Live Hotmail Free. Sign up >> now. >
