Webservices references

  • Thread starter Thread starter Craig G
  • Start date Start date
C

Craig G

we have a small pocketpc application that uses a webservice to connect to
SQL2000

everything works fine until we try to build a customer version. we just
overwrite the existing references using the customers IP address where the
webservice will reside. but as are network is not able to see the IP address
it creates an error.

is there a way around this or do u just overwrite every instance of the IP
address in the reference.map and .disco files?

any help would be greatly appreciated.

Cheers,
Craig
 
Hey

If you cant see the ip address, chances are that your application cant see
the ip address either. I think this is more network configuration than
dotnet.

Hope you get the problem solved :)
 
cheers for the reply - ill try to make it a bit clearer. i cant see the IP
address as its a server out on site.

the application all runs fine in house. i reference the server which the web
service resides on. the development environment then acknowledges this web
service exists. you then build the application, package & deploy -
everything works fine

but how do you reference the customers server which is on-site and has the
web service already installed??

in order for the application to be able to pick it up. id need to take a
development environment PC out on site reference the customer server, then
build the application, package & deploy onto the Pocket PC

Cheers,
Craig

its more how do you create a reference to a webservice for the
 
In code, you can change the Web service URI using the URL property. Store
the "live" address in a config file of some description and at runtime read
the file and assign the correct endpoint.

--Neil
 
Ok, i see your problem now.

I have never tried doing this, so actually i wouldnt be of much help here. I
keep all my webservices on the same server for all of my customers, and then
its no problem.

But this is a really good question though. I would really love to hear a
good answer on this one. A lot of people must have these needs.

A "not so fancy solution" could be configuring a machine the same way as the
server, and then build the application. But this would demand you to change
the config for each customer. Thats not a good solution.

Anyone?
 
nice one Neil tanks very much!!


Neil Cowburn said:
In code, you can change the Web service URI using the URL property. Store
the "live" address in a config file of some description and at runtime read
the file and assign the correct endpoint.

--Neil
Click to expand...
 
Back
Top