Oh. What a great idea! Actually, one of the primary reason that I created a "generic" class libray instead of using oleg guide which uses J directly ... is to facilitate debugging from inside Visual Studio .NET and continuing into a J session. This strategy actually allows for production level debugging. I mean, I normally just distribute J.EXE and J.DLL and load the script at runtime. For cases where theres a problem, I would then just bring along my laptop with a full install of J and when I login into the system, there is a hardwired switch (if (user == 'alex) then debug=true) which calls the Session in DEBUG mode and displays the full J session. I just then add make sure that the debugger is displayed (dbg 1) and add "dbstopme ''" into the script. I'll add a chapter of this to the JWiki version. Thanks.
________________________________ From: [EMAIL PROTECTED] on behalf of bill lam Sent: Sat 8/2/2008 10:12 PM To: General forum Subject: Re: [Jgeneral] J-VB.NET wrapper Alex Rufon wrote: > ps. > > I would appreciate any comments/suggestions/violent reaction to the new > guide. I don't have any experience in this subject. However I would like to know how to debug those scripts across the boundary. For example if it is possible to set break-point or fire-up the J debug window when error occur, the same that can be done in native J session. regards, ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
