Note that there are some explanatory texts on larger screens.

plurals
  1. POVisual Studio 2010 Professional - Problem Unit-Testing Web Services
    primarykey
    data
    text
    <p>Have created a very simple Web Service (asmx) in Visual Studio 2010 Professional, and am trying to use the auto-generated unit test cases. I get something that seems quite familiar on this site:</p> <p>The web site could not be configured correctly; getting ASP.NET process information failed. Requesting <a href="http://localhost:81/zfp/VSEnterpriseHelper.axd" rel="nofollow noreferrer">http://localhost:81/zfp/VSEnterpriseHelper.axd</a> return an error: The remote server returned an error: (500) Internal Server Error.</p> <p><a href="https://stackoverflow.com/questions/260432/500-error-running-visual-studio-asp-net-unit-test">500 Error Running Visual Studio ASP.NET Unit Test</a></p> <p>I have tried:<br> 1. Running the tests on IIS rather than ASP.NET Development Server<br> 2. Adding and then removing the XML fragment to my Web Service's .config file<br> 3. Giving the MACHINE\ASPNET account Full control to the local folder</p> <p>My current questions:<br> 1. Why am I being bothered with this instrumentation / code coverage DLL, when this doesn't seem to be something that ships with Visual Studio 2010 Professional? Is there any way I can turn it off?<br> 2. I'm placing the node under in Web.config - is that the correct node?<br> 3. Is it possible to bind to a web service without using the webby test attributes?</p> <p>I've seen other people advising making the Web Service as light-weight as possible. I'm trying to call it with jQuery / AJAX / JSON, so being able to debug the actual web service would be really helpful.</p> <p>Best wishes,</p> <p>Ben</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload