Don’t put 2 lines of code throughout your project. Put that code in a global module and call that. Much more maintainable. But AFAIK, you’ll have to visit every method and place the call to your global method.
There is no fast way to do what you describe in the IDE. If you are comfortable hacking up project files, you can do what you are describing using a combination of command line tools and other text editors… but if all you are trying to do is figure out where the expensive parts of your code are learn about and use the profiler.
@Paul Lefebvre I checked the Profile Code menu item, ran the project, accessed the part of the project with the expensive code, hit the stop button in the IDE. Unfortunately, no Profile section appears in the Navigator of the IDE. I restarted Xojo and still can’t get the Profile section to appear. I don’t see any other steps here : Any thoughts?
@Markus Winter Yes, and I’m open to other ways to debug compiled webapps, but if there is no obvious expensive code seen in the Profiler when profiling the app locally, but sections of the app still bog down in the compiled version on the webserver, I’m not sure of another way to track down expensive compiled webapp code, aside from adding code to every method to log it’s execution completion time, etc.