.net 2.0 - webservice  
Author Message
arkiboys





PostPosted: ASMX Web Services and XML Serialization, .net 2.0 - webservice Top

Hi,
Using .Net 2.0
I have created webservices inside a project. These services are in a solution on my machine which I am developing.
To reference these services, I use Add Web Reference, webservices in this solution (Because the services are saved in my local machine).
At what stage should I place these webservices in the virtual directory of a webserver
Should these webservices be developed in a virtual directory on my local machine as opposed to in the local C drive as it is now

The intension is that others be able to see these webservices as they are being developed.
For an example, from my machine to reference one of the webservices, this is the path I use:

http://localhost:2144/inTest.asmx

does this mean that other developers to reference this webservice should use:

http://MyMachineName:2144/inTest.asmx

Thanks



.NET Development23  
 
 
timvw





PostPosted: ASMX Web Services and XML Serialization, .net 2.0 - webservice Top

You could configure your WebProject to use IIS (VirtualDirectory) instead of the Visual Studio development server (Project properties, under the Web tab if i'm not mistaken)...


 
 
kbradl1





PostPosted: ASMX Web Services and XML Serialization, .net 2.0 - webservice Top

I would setup a versioning plan as you don't want others directly testing your constantly changing code. You are liable to introduce bugs, sometimes on purpose to add new functionality and you don't wnt to interfere with their testing.

Periodically, maybe once a week, I would publish the web service project to a virtual directory on your test server (i.e. http://testserver/TestWebService/inTest.asmx ). Let the othe developers know your planned schedule so they can update and re-test their code when you have finished testing yours.

Using http://MyMachineName:2144/inTest.asmx is a bad idea because tihs port may change (if you have dynamic port set) and your machine my be off or Visual Studio may be closed and then that path won't work for others.