Debugging n-tier Silverlight Business Server and Data Access Layers

Gareth posted on Friday, August 14, 2009

Firstly, I apologise for what might be deemed quite a newbie question that could be answered if I trawled through all of the posts on the forum, however I am currently on the train for the next 2 hours with very limited data access and I'm stuck! So I thought a quick post and direct reply would help.
Ok, so I've got my n-tier Silverlight app compiling and executing however when I bring up my product list page the busy icon appears briefly as expected and then nothing happens, no data appears.
Now I want to debug at the Business Server and Data Access layers but I am finding myself at a loss on how to get that working. Naturally I can get as far as the client async call being sent off but how do I pick up the event the other side?

Do I need to create a separate project, or attach to some other process? I couldn't see anything in the process list.

Any pointers would be appreciated so that I don't have to sit on this train doing nothing for the next couple of hours.

Cheers,
Gareth.

sergeyb replied on Friday, August 14, 2009

If your server is hosted inside the same web project as silverlight app, you do not need to anything, just setup breakpoints inside server classes.

Sergey Barskiy
Principal Consultant
office: 678.405.0687 | mobile: 404.388.1899

Microsoft Worldwide Partner of the Year | Custom Development Solutions, Technical Innovation


-----Original Message-----
From: Gareth [mailto:cslanet@lhotka.net]
Sent: Friday, August 14, 2009 10:16 AM
To: Sergey Barskiy
Subject: [CSLA .NET] Debugging n-tier Silverlight Business Server and Data Access Layers

Firstly, I apologise for what might be deemed quite a newbie question that could be answered if I trawled through all of the posts on the forum, however I am currently on the train for the next 2 hours with very limited data access and I'm stuck! So I thought a quick post and direct reply would help.
Ok, so I've got my n-tier Silverlight app compiling and executing however when I bring up my product list page the busy icon appears briefly as expected and then nothing happens, no data appears.
Now I want to debug at the Business Server and Data Access layers but I am finding myself at a loss on how to get that working. Naturally I can get as far as the client async call being sent off but how do I pick up the event the other side?

Do I need to create a separate project, or attach to some other process? I couldn't see anything in the process list.

Any pointers would be appreciated so that I don't have to sit on this train doing nothing for the next couple of hours.

Cheers,
Gareth.

Gareth replied on Friday, August 14, 2009

Hi Sergey, thanks for your reply. That's initially what I thought would be the case and I've tried it but none of the breakpoints fire. Maybe I need to recheck that they are project references?

Gareth

sergeyb replied on Friday, August 14, 2009

Sounds like a plan. Make sure you have project dependencies setup as well.

Sergey Barskiy
Principal Consultant
office: 678.405.0687 | mobile: 404.388.1899

Microsoft Worldwide Partner of the Year | Custom Development Solutions, Technical Innovation


-----Original Message-----
From: Gareth [mailto:cslanet@lhotka.net]
Sent: Friday, August 14, 2009 11:24 AM
To: Sergey Barskiy
Subject: Re: [CSLA .NET] RE: Debugging n-tier Silverlight Business Server and Data Access Layers

Hi Sergey, thanks for your reply. That's initially what I thought would be the case and I've tried it but none of the breakpoints fire. Maybe I need to recheck that they are project references?

Gareth

Gareth replied on Monday, August 17, 2009

Well that made no difference. Everything was set-up correctly.
Even Rocky's demo 3-tier projects don't work for me or fire any breakpoints on the server side.
However, I've just installed his new 3.8 alpha version and guess what... it's all working.
I'm guessing it might be something to do with a pure Silverlight 3.0 installation and not having come via SL 2.0.

Cheers,
Gareth.

CyclingFoodmanPA replied on Monday, August 17, 2009

I had this problem also inititally.  What you have to do is to select the Debug option on the menu of VS, then attach to the server process #.  For example, if you are debugging the Rolodex example, you would set your breakpoints, run the application, the go back to VS and select debug, attach to process 2430.

 

HTH

RobKraft replied on Monday, December 07, 2009

Thanks for this post! I'd just like to clarify that when you attach, don't look for 2430 in the ID column of the list of processes, look for a process with ... "Port 2430" in the Title column. Probably Process "WebDev.WebServer.Exe", Title="ASP.NET Development Server - Port 2430"