Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community

At 08 JUL 2008 10:01:18PM Dave Harmacek wrote:

Back in the old days of OI 3.75 I could debug a misbehaving web application by placing a DEBUG in the code and watch it respond to my web requests. This was running OICGI.EXE in Local Mode, of course.

Now, with OECGI2.EXE running dynamic engines with a D license I can't debug since I can't see the engine from the desktop.

How do I debug a "modern" OI-based web application?

Dave


At 09 JUL 2008 01:44AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:

The easiest way is to tell OECGI2 to use a specifically named engine server and to launch OI on the desktop with /SN=WhateverYouToldOECGIToUse. We typically use /SN=DEBUG.

The Sprezzatura Group

World leaders in all things RevSoft


At 12 JUL 2008 10:04AM Dave Harmacek wrote:

Thanks, finally found when the engine was presenting an error to the bit bucket and fixed it.

Dave

View this thread on the Works forum...

  • third_party_content/community/commentary/forums_works/62f949469a65c4c185257481000b1b05.txt
  • Last modified: 2023/12/30 11:57
  • by 127.0.0.1