<asp:ScriptManagerProxy runat="server" ID="smpMyProxy"> <Services> <asp:ServiceReference Path="~/MyServices/MyService.asmx" /> </Services> </asp:ScriptManagerProxy>
That works all fine and dandy, but no profiling info is shown for the web method call. Note that I have plenty of profiler calls throughout the web method, like this:
Using (MiniProfiler.Current.Step("MyService.MyWebMethod")) ' Yada yada... End Using
Maybe I have an old profiler and the new one supports this scenario? Or maybe this scenario isn’t supported at all? Is there some workaround?