how to debug in InfoPath?

[pating]

i'm using InfoPath 2003 toolkit for .Net but when i run my program, i can't
debug it. i placed a breakpoint in the codes for a button (OnClick) and when
i clicked the button, it does what the codes are supposed to do but i can't
debug. i guess i just need to set something, but i dont what. thanks.

 

[Kalyan Reddy]

Hello

try inserting <debugger;> in the code wherever you want to debug

 

[S.Y.M. Wong-A-Ton]

Set VS.NET's mode to "Debug" instead of "Release".

 

[pating]

i'm already running my project in debug mode (using vb codes). but when i run
it, a message appears, "Unable to attach to application 'Microsoft Internet
Explorer' (PID:3712) on machine 'Pating'. Do you want to continue anyway?"
(where 'Pating' is my computer name i think). When i pressed Yes, a message
appears again saying "Unable to attach to machine 'Pating'. Do you want to
continue anyway?". And when i choose Yes again, the preview window now
appears. But i cant debug it. Thanks anyway.
I'm actually using Visual Studio .Net (ASP.Net and VB.net) for almost 4
years now, and its my first time to use InfoPath, and i have a LOT of
questions. I'll post my other questions later. Thanks again.

 

[pating]

Where should i place <debugger;> in my codes again? Im using VB codes in my
project.
Here is a sample of my codes. Its in the OnClick event of a button, where
i'm typing any text in the txtInput textbox and when i press the button, i
want to place that value + a period in the txtOutput. I'm just trying the
code coz my form will be needing some computations, that is why i want to
debug my program.
Thanks!

Dim nodTargetIn As IXMLDOMNode =
thisXDocument.DOM.selectSingleNode("/my:myFields/my:txtInput")
Dim nodTargetOut As IXMLDOMNode =
thisXDocument.DOM.selectSingleNode("/my:myFields/my:txtOutput")
nodTargetOut.text = nodTargetIn.text + "."

 

[S.Y.M. Wong-A-Ton]

Debugging InfoPath in VS.NET is pretty straightforward by setting breakpoints
and starting the application. There is no need to attach the debugger to a
running process, if that is what you tried to do. If you didn't try to do
that, I suspect that the message you are getting could be due to a security
setting. Are you a member of the administrators group? Are you debugging
remotely or locally? Are you a member of the necessary security groups used
for debugging? How tight are your IE security settings? Etc. etc.