There is a big problem with UI modification, that is, "you cannot automatically enter a single step server." Failed to debug remote procedure. This usually means that there is a problem when you make a remote call to a WCF call that does not start debugging on the server.
Why the problem occurred:
It is because we have modified something in the source code, but when the client invokes it, it is generally invoked in the configuration file for the WCF service:
<endpoint address= "http://localhost:5734/Service.svc?wsdl" binding= "BasicHttpBinding" bindingconfiguration= " Basichttpbinding_default "contract=" Itoo. UINonQueryProperties.Contracts.IUINonQueryPropertiesService "name=" Basichttpbinding_services "/>
The first possibility:
This error is that your WebService code is not in our local, and WCF calls, you cannot step in. This is delivered through remote data and cannot be entered in one step.
We can build the DLL file (the code that will serve the server) and reference it through vs compilation.
The second possibility:
When we generally use a WCF service that is invoked through a configuration file, one possibility is that the name of our service is wrong, for example:
<%@ ServiceHost language= "C #" debug= "true" service= "Itoo. UINonQueryProperties.WCFService.UINonQueryPropertiesService "codebehind=" Service.svc.cs "%>
This name is not written in the wrong, and you have to publish the name of the class must be consistent.
The third possibility:
Call, I changed the server-side code, and the client was not updated in a timely manner. Let's take a closer look at this question:
The quickest way I use it is in the C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP. NET Files\vs\39f299e2\e5e2d867\assembly\ dl3\062f62f1\66fadec8_f180d001 "folder, we can update the file ITOO.UINonQueryProperties.BLL.dll file.
You cannot automatically enter a single-step server. Failed to debug remote procedure. This usually means that debugging is not started on the server