PDA

View Full Version : Server side de-buging techniques



Jim Spence
20-Sep-2007, 04:04 PM
I'm looking for ideas on how to debug my Dataflex server-side code.

Since this is Ajax, I don't use the DAW debugger.

Showlns and messageboxes do not seem to work.

I am aware of the Debug mode for my ASP as discussed in the Help, but
am really looking to debug the dataflex procedures and functions.

Currently I use Direct_Output to write to a text file.

Any other ideas would be welcome. TIA

Anders Ohrt
21-Sep-2007, 02:37 AM
> I'm looking for ideas on how to debug my Dataflex server-side code.
>
> Since this is Ajax, I don't use the DAW debugger.

Why not? The server side code is plain old VDF .exe, so use the debugger.


> Showlns and messageboxes do not seem to work.

You need to enable desktop interaction for the WebApp Service.

// Anders

Jim Spence
21-Sep-2007, 02:19 PM
In Vincent Oorspong's reply to the Eddy Kleinjan's March 23 post, he
mentions the problems that can arise with using the DAW debugger with
ajax. That is is why I do not use it.

Thank you, Anders, for pointing out the IIS setting for DAW WebApp
"Allow service to interact with desktop".
When my application is run using WebApp, the shlowln window appears
but then immediately dissappears, so I need a messagebox to
temporarily keep the shlowln window visible. When my application is
run using DAW debugger, the showln window is persistent. Interesting.

Vincent Oorsprong
22-Sep-2007, 03:53 AM
Jim,

In a perfect world you should do all the debugging at the development
machine and if a real server is needed use a test server. But if all of this
does not help to solve the problem you need to debug on the real server
taking all the disadvantages for granted.

--
Regards,
Vincent Oorsprong
Data Access Europe B.V.
http://www.dataaccess.nl

Bob Worsley
22-Sep-2007, 01:14 PM
Jim, on occasion when I've reverted to a showln, I've had to put a sleep 1
or 2 just after it to keep it on the screen long enough to be read or in
extreme cases an inkey. And by all means, use the debugger. You will have
to click through the errors, or if you get a page not found error or the
page won't display, just hit F5 and it will reappear. One of these days
they'll figure out a remedy.
Bob

"Jim Spence" <Jim.Spence@hcss.com> wrote in message
news:r658f3ttf9g4q0lqn4qj5j5aqfhv7qr1df@4ax.com...
> In Vincent Oorspong's reply to the Eddy Kleinjan's March 23 post, he
> mentions the problems that can arise with using the DAW debugger with
> ajax. That is is why I do not use it.
>
> Thank you, Anders, for pointing out the IIS setting for DAW WebApp
> "Allow service to interact with desktop".
> When my application is run using WebApp, the shlowln window appears
> but then immediately dissappears, so I need a messagebox to
> temporarily keep the shlowln window visible. When my application is
> run using DAW debugger, the showln window is persistent. Interesting.
>
>

Raphael Theiler
24-Sep-2007, 06:30 AM
There's a browser-extension called Firebug for Firefox... it sometimes helps finding bugs, etc... you can watch all the xml/ajax-requests on a page and view the source, browse DOM, etc.

http://www.getfirebug.com/

well... as far as I'm concerned this extension is only for firefox not for IE... but I'm sure there is something similliar for IE too ...



On Sat, 22 Sep 2007 10:53:23 +0200
"Vincent Oorsprong" <vincent.oorsprong@reply.at.newsgroup.nl> wrote:

> Jim,
>
> In a perfect world you should do all the debugging at the development
> machine and if a real server is needed use a test server. But if all of this
> does not help to solve the problem you need to debug on the real server
> taking all the disadvantages for granted.
>
> --
> Regards,
> Vincent Oorsprong
> Data Access Europe B.V.
> http://www.dataaccess.nl
>
>


--
Raphael Theiler <raphael_nospam_@black-rat.no-ip.com>

Jim Spence
24-Sep-2007, 07:55 AM
Thank you everyone for your responses.

What I'm hearing is that despite the errors associated with having to
switch back and forth between the ASP instance of my WebApp.exe and
the Webservice instance of my WebApp.exe, I should still be able to
get valuable debugging help from the DAW Debugger.

I am just evaluating the WebApp with Ajax framework - no worries about
me putting debug code, or simply debugging, on a production server.

Firebug with Firefox is indeed an excellent tool. The ability to step
through the javascript, view the DOM, and see the Ajax requests to
server and server response is most helpful.

Thanks for the tip of using Sleep instead of messageboxes to extend
the appearance time of shlowln's (needed when using real WebApp server
in stead of DAW debugger) . This is *much* smoother and less
confusing/distracting.

Thanks again.