Automatically updating webreference in client, while debugging webservice on the same machine

Automatically updating webreference in client, while debugging webservice on the same machine by NL-Loek

Closed

as Fixed

Type:	Bug
ID:	303796
Opened:	10/10/2007 6:58:13 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

I have a solution containing a webservice and a webclient.
They both run in IIS.
When I am debugging services and have hit a breakpoint and then click any file in the service-client project Visual Studio attempts to update the webreference, with no apparent timeout.
Obviously, since I'm debugging the IIS process, Visual Studio hangs until I do IISRESET.

Details (expand)

English

Visual Studio Code Name "Orcas" (Beta 2)

Windows Server 2003

English

I have a solution containing a webservice and a webclient.
They both run in IIS.
When I am debugging services and have hit a breakpoint and then click any file in the service-client project Visual Studio attempts to update the webreference, with no apparent timeout.
Obviously, since I'm debugging the IIS process, Visual Studio hangs until I do IISRESET.

Visual Studio is unresponsive until IIS is reset.

No automatic updating of webreferences while debugging.
A timeout for the update of the webreference.

Posted by Microsoft on 10/12/2007 at 4:10 PM

Thanks for reporting this issue. Due to we are in late product cycle, we will conside for service pack.
This is not a hang. The updating will timeout after around 30 seconds, but it is not a ideal experience.
At the same time, after you change the service signature in the .asmx page and save it, you can switch to client web which will invoke the updating. You can update the client side code first and then start to debug the asmx.
Thank you,
Visual Studio Product Team

Posted by Microsoft on 10/12/2007 at 9:21 AM

Thank you for submitting this issue. We have postponed it for consideration in a future release of the product. We will consider in future planning.

- The Visual Web Developer Team.

Posted by Microsoft on 10/10/2007 at 6:58 PM

Thank you for your feedback. We are currently investigating. The investigation process normally takes 7-14 days. If this issue is urgent, please contact support directly (see http://support.microsoft.com).

If at any time your issue is closed unsatisfactorily, you may edit your issue via Connect and change the status to “Active.”

Thank you,
Visual Studio Product Team