![]() | |
![]() |
| | Thread Tools | Search this Thread | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| |||
| |||
|
|
You're running your new web service as a File based web project. That's why it's running under cassini (also known as the "ASP.NET development server"). This little web server starts up on demand on a random port. That's why sometimes it's there, sometimes it's not. Using cassini for development is basically a bad idea as it runs with the permissions of the user (and since they're a developer that's usually Administrator) and not the limited permissions that we applications usually enjoy. So the best thing to do is to go back to using good old IIS: - Setup a virtual directory in IIS and point it to your web service's folder, e.g. http://localhost/myservice/ - Go into your web projects settings by right clicking on the project and choosing 'Property Pages'. - Select the Start Options menu item. - Select 'Use custom server' and enter the url of the virtual directory you configured into the Base Url field (e.g. http://localhost/myservice/). Now, you can debug and VS2005 will attach to IIS and you can hit the virtual directory at any time. Josh http://www.thejoyofcode.com/ |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
| |