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?
Check your projects debug settings and make sure the right project (i.e. the web project) is set as the startup project. Sometimes the Silverlight project gets set as the startup project which causes debugging to be weird.
As strange as it would seem the problem is likely solved when I rerun the project immediatly after I run it for debugging the first time, the first time is when it just hangs there waiting response, the second time goes fast and gets the data, is this a
bug?
I used to research on this issue, and glad to know you have the issue solved, about "first time takes longer time", I got some information from this post:
Is there anyway to avoid this service 'cold start', it's putting my development time through the roof waiting 2 minutes for a simple service to 'start up'.
keoz
Member
75 Points
81 Posts
WCF RIA Services migration painfull debugging
Dec 15, 2009 10:04 PM | LINK
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
WCF ria Service silverlight local debugging
www.cigisoft.net
@cigisoft
ColinBlair
All-Star
29935 Points
5031 Posts
Re: WCF RIA Services migration painfull debugging
Dec 15, 2009 10:37 PM | LINK
Check your projects debug settings and make sure the right project (i.e. the web project) is set as the startup project. Sometimes the Silverlight project gets set as the startup project which causes debugging to be weird.
Upshot Blog
ColinBlair on Twitter
MVVM and RIA Services
keoz
Member
75 Points
81 Posts
Re: WCF RIA Services migration painfull debugging
Dec 16, 2009 12:06 AM | LINK
Hi Colin yes the startup project is the web project associated with the client xap file
www.cigisoft.net
@cigisoft
keoz
Member
75 Points
81 Posts
Re: WCF RIA Services migration painfull debugging
Dec 17, 2009 03:48 AM | LINK
-
www.cigisoft.net
@cigisoft
keoz
Member
75 Points
81 Posts
Re: WCF RIA Services migration painfull debugging
Dec 17, 2009 03:51 AM | LINK
www.cigisoft.net
@cigisoft
keoz
Member
75 Points
81 Posts
Re: WCF RIA Services migration painfull debugging
Dec 17, 2009 04:11 AM | LINK
As strange as it would seem the problem is likely solved when I rerun the project immediatly after I run it for debugging the first time, the first time is when it just hangs there waiting response, the second time goes fast and gets the data, is this a bug?
www.cigisoft.net
@cigisoft
nangua
Contributor
5288 Points
862 Posts
Re: WCF RIA Services migration painfull debugging
Dec 23, 2009 04:14 AM | LINK
Hi,
I used to research on this issue, and glad to know you have the issue solved, about "first time takes longer time", I got some information from this post:
http://forums.silverlight.net/forums/p/35033/105543.aspx
I wouldn't say it's a bug, but clearly it's not a good experience.
keoz
Member
75 Points
81 Posts
Re: WCF RIA Services migration painfull debugging
Dec 23, 2009 03:03 PM | LINK
Thanks looks like is the same with WCF traditional services as expected, I hope "cold-start" debuging will be fixed anytime soon
www.cigisoft.net
@cigisoft
NVenhola
Member
2 Points
7 Posts
Re: WCF RIA Services migration painfull debugging
Jan 21, 2010 02:44 PM | LINK
I have the same issue.
Is there anyway to avoid this service 'cold start', it's putting my development time through the roof waiting 2 minutes for a simple service to 'start up'.
Sam Minnella
Member
14 Points
13 Posts
Re: WCF RIA Services migration painfull debugging
Jan 22, 2010 09:54 PM | LINK
Not a bug, give me a break! Why would the first request to a service take 2 or 3 minutes?