Answered by:
Debugging print preferences application
Question
-
I'm writing DCA(device companion application) for v4 printer driver using XAML and C#. When application stops at breakpoint, I can't evaluate values of local variables and if I press F5 to continue execution it stops and fly-out window is disappeared. It seems that this behavior is caused by fly-out nature of print preferences dialog. Can you suggest a solution for this problem? Is there any way to debug DCA applications?Tuesday, January 24, 2012 9:19 AM
Answers
-
You can use remote debugging to evaluate the values in the flyout. You can find a publicly available remote debugger for VS11 here. http://www.microsoft.com/download/en/details.aspx?id=27540
Deploy that on your remote machine and set the target of your deployment as the remote machine in VS11 under the Debug-><project> Properties dialog.
- Edited by Minglei HuangMicrosoft employee Wednesday, February 8, 2012 7:43 PM
- Proposed as answer by Minglei HuangMicrosoft employee Wednesday, February 8, 2012 7:44 PM
- Marked as answer by Sergey_M Tuesday, February 21, 2012 3:59 PM
Wednesday, February 8, 2012 7:43 PM -
You could also use the simulator
- Marked as answer by Sergey_M Tuesday, February 21, 2012 4:00 PM
Thursday, February 16, 2012 2:17 AM
All replies
-
You can use remote debugging to evaluate the values in the flyout. You can find a publicly available remote debugger for VS11 here. http://www.microsoft.com/download/en/details.aspx?id=27540
Deploy that on your remote machine and set the target of your deployment as the remote machine in VS11 under the Debug-><project> Properties dialog.
- Edited by Minglei HuangMicrosoft employee Wednesday, February 8, 2012 7:43 PM
- Proposed as answer by Minglei HuangMicrosoft employee Wednesday, February 8, 2012 7:44 PM
- Marked as answer by Sergey_M Tuesday, February 21, 2012 3:59 PM
Wednesday, February 8, 2012 7:43 PM -
You could also use the simulator
- Marked as answer by Sergey_M Tuesday, February 21, 2012 4:00 PM
Thursday, February 16, 2012 2:17 AM -
Thank you for the response, but is this only solution? I think it isn't convinient way to debug such applications.Friday, February 17, 2012 1:09 PM
-
It is very slowly, especially when working on virtual mashines.Friday, February 17, 2012 1:37 PM
-
Well, the flyout has to disappear or else it would sit on top of visual studio when you are debugging. So it seems the only options are to have two machines or use the simulator.
Since you are using a virtual machine, you can try using another virtual machine as the remote debugging target.
- Proposed as answer by Eric Hanson-MSFTModerator Saturday, March 3, 2012 2:47 AM
Friday, February 17, 2012 9:17 PM -
I try to use simulator, two machines but debugging is not fully possible. When I try to debug remotely window disappear.Wednesday, July 25, 2012 3:43 PM