M
Mike Fechner
Guest
My primary test environment for Web Client targeted applications is a prowin32.exe session not connected to any database – running out of the R-Code and on the same folders as the development environment. This is in particular helpful, as the WebClient (to my knowledge) is not debuggable. The second test environment is the same as above, but running the webclient executable _prowc from a webclient installation. There is absolutely no need to use the Web Client Application Assembler for a developer to test the application at an early stage. So I usually never mess – at this early stage – with an existing Intellistream setup of the application. You mentioned the challenge of messages written to the AppServer logfile: baretail and the like are your friend here!
Continue reading...
Continue reading...