Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Well, after a lot of futzing about, I eventually figured this out. The problem was caused by my using the same assembly in the web app as is used in the service (I used a different portion of the assembly in the web app). This caused a class that is part of a data contract and that I had modified for the service's use to be different in the web app's compiled assembly than the service was publishing. This in turn caused the service reference to fail to generate the client proxy. Without the client proxy, my web app code showed errors and so I never tried to compile the solution. The simple answer was to build only the common assembly in the web app (which works) and then the service reference generated the proxy properly. Imagine how perplexed I was to have a single data member of a class be the demonstrable cause of the problem, but its name, data type, position in the code, etc. had no effect on the problem! Anyway, probably bad design to be reusing this assembly anyway - likely better to consume this information from the service itself. As a final note, the reason that the winform app worked was because I also use the same assembly in the winform app and it was always being kept up-to-date when I compiled the app, so the changes never conflicted. Hope this helps someone in the future. As a side note to Microsoft - any error information about this conflict would have helped immensely in trouble-shooting, though I grant that it is probably not a common scenario.</p>
 

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