Profiling WCF service using net.tcp binding

[jbernard]

I am trying to profile an IIS-hosted WCF service which supports both a http and a net.tcp binding.
The profiling session works fine when the client connects to the service using http but the client fails to connect using net.tcp://localhost/...

Does .NET Memory Profiler support profiling web services using the net.tcp connections?

[Andreas Suurkuusk]

If you run your service under .NET Memory Profiler it should function as normal, albeit a bit slower. The possibility to use a TCP binding should not be affected.

We will create a test project using a WCF TCP binding and see if we can reproduce the problem. However, if you have a test project reproducing the error (which you can share with us), that would make it easier for us to locate the problem. You can contact us at support@scitech.se if you can provide us with a repro.

What settings are you using when your profile your service? Is the unmanaged resources tracker enabled?