We test our application and its various versions from different testing shortcuts for each environment. Today, we were experimenting with creating a Progress OpenEdge Application Run Configuration.
When we run our application it starts up, but then just immediately shuts down as if the wait-for is completely ignored. Are the Run Configurations only designed to support running an application with a GUI for .Net UI?
"You can run anything."
I beg to differ.
The debugger doesn't even stop. The splash screen pops-up, then disappears, then the application being run just closes.
Is it just this one program? Can you run something simple with just a message statement?
"Is it just this one program?"
It's my application. I am specifying our start-up program which launches other things and then does a WAIT-FOR. It just seems to never stop and wait.
"Can you run something simple with just a message statement?"
"You may know this, so forgive the repetition but the debugger in PDSOE *requires* a breakpoint in order to stop (unlike the standalone/classic debugger which stops first and waits for you)."
Correct. BUT.. the break-point doesn't stop it. So, I put in the traditional DEBUGGER:INITIATE and DEBUGGER:SET-BREAK. It flashes and then disappears.
Do the Run Configurations require everything to be in your project?
Turn on clientlog. This link my help.
Ok, we've gotten to the bottom of it.
It has to do with:
"There’s a wrapper program that is called before your program, but it doesn’t do much."
"That has a wait-for in it."
Ok. Unrelated. :)
It had to do with our call-stack inspection to see if our app was already running. The fact that our startup was being run by another procedure seemed to confuse our function.
So, the Run Configurations does seem to work as expected. I stand corrected.