#Xojo program arguments zip file

It is important to be able to test in this environment as permissions and folders change. To see the debug log messages right in the IDE click on the icon. You can either stop the service here or use the stop button in the Xojo IDE. Running services.msc will show you the service _test (at the top of the list) is running. This time you’ll see args(0 & 1), but args(0) is the program executable while args(1) is the service name. Now select run paused, right click on the executable and select Send To ServiceDebug. If you run this normally you will see args(0 & 1) are printed to the debug log and both will be the name of the executable file. Replace the contents of the RUN event with: To test this out create a new project using the Empty Service template. Copy the shortcut to %APPDATA%MicrosoftWindowsSendTo and you’re ready to roll!

#Xojo program arguments zip file

The utility accepts the executable path as its argument, creates a service “_test” and starts the service.Īfter downloading the zip file expand it somewhere and create a shortcut. The source for the Xojo project is included. I have written a little utility that allows me to right click on the debug executable and automate the service creation and startup. Now you’re debugging your app while it runs in service mode.Īll of this takes time, and having to create/start the service each time slows down debugging considerably. To do this, you can Select Run Paused from the project menu, then create the windows service and start it.

When working with Windows services you’ll want to debug the application while it’s running as a service.