Hi have been using ria services since july ctp, currently I have migrated to PDC bits, before it I had no problems debugging at all however now with a new project created from scratch using the bits (and VS 2008) I come with the first issue: when trying to load something from database using a Query operation it takes so long just to come with a problem calling the domain operation, it is a just in time debugger dialog that did not appear before, I was used to caching the exceptions right from the client or from the server since I'm debugging using IIS too, but it does not seem like the operations exceptions get cought but pass trhough to Internet Explorer and there there is no one to catch it so the just in time debugger popup, ok then when I finally get the service to respond I can finally do fast queries without taking so long, however after a while again the jit debuging popup after a long wait.

On my testing I have crome across a conclusion that is something related debuging this kind of projects locally (RIA Services + EF + IIS), I have tested to access my application from outside my network and there is only bells and whistles no problem geting data

There is no problem if I query the service from a local WPF application using service references either, no problem at all

Fiddler does not bring any usefull information, when the service does not respond there is no response back at all to Fiddler to catch, or the response is back when I stop debugging, don't know why is that

So anyway this looks like if the service delays to wake up, even when I type the svc url from browser sometimes it delays like 3 minutes to respond, subsequent queries are fast, that's the same behaviour when using the Silverlight application, when it takes too long there is a timeout exception

 Could someone explain how to fix the just in time dialog to not appear again and why accessing my app from outside network works better than debugging locally?

thanks