如何调试ServiceStack服务方法？

Question

I am using the JsonServiceClient to test a self-hosted service to the database. The client is receiving an empty array without the 8 records that are in the database. My problem is that if I put a breakpoint in the Get method of the service, it never fires.

Here is the code for the get method:

    public PracticesResponse Get(PracticesGetRequest request)
    {
        var parm = Request.QueryString.Get("source");
        var source = Uri.UnescapeDataString(parm);

        var response = new PracticesResponse
        {
            Practices = Repo.GetBySource(source).ToArray()
        };
        return response;
    }

If I put a breakpoint anywhere in the code, it never fires, so I can't tell whether my query parameter isn't being processed correctly, or my repository isn't getting wired up, or what. If I break execution on the line of code that calls the JsonServiceClient get method and attempt to step into it here:

var dto = Client.Get<PracticesResponse>("/practices?source=Desire%20%Map");
Assert.That(dto.Practices.Length > 7);

the debugger processes the call without stepping in and the next break is on the Assert.

Here is a link to simple Visual Studio application that exhibits exactly the same behavior when I try to step into the JsonClient.Get method.

How can I get inside this method to see what is going on?

Answer 1

If the breakpoint never gets hit in debug mode than either the code you think is getting fired is not being executed or the VS.NET debugger is not properly hooked up. But this is normally only an issue in ASP.NET applications where you need to restart the AppDomain by "touching" and resaving the Web.config or can also be that the source code is out-of-sync with what's being debugged (normally an issue with trying to debug compiled .dlls with out-of-sync .pdb's).

Since this is a self-hosted my guess is that the code is just not getting hit. Can you expand your question to provide the full Request DTO with any custom routes defined, the code you're using to call the Service as well as the raw HTTP Request / Response (which you can get with Fiddler) which will show what's happening underneath. Also double-check to make sure that your Service is inheriting the Service class or implements IService .

On Service design I would rename the Request DTO into something more readable like GetPractices and instead of manually fetching the parameter from the QueryString to just read it from the Request DTO, also if you're only going to specify the return type in one place it's better that it's annotated on the Request DTO that way the return type information is also available on the client, eg:

PracticesResponse response = client.Get(new GetPractices { Source = src });

And I would re-write the Server to something like:

public class GetPractices : IReturn<PracticesResponse> 
{
    public string Source { get; set; }
}

public object Get(GetPractices request)
{
    return new PracticesResponse {
        Practices = Repo.GetBySource(request.Source)
    };
}