I have a VB.net project created in Visual Studio. The project works properly. However, I install it on my customers' system by logging in using remote desktop (they are in a different state). The program is written to launch every hour on the hour. I also put the .exe in the Startup folder so if the server reboots, the program will launch automatically.
All of that works fine. But the problem is that, because I logged in using rdp to install the package, as soon as I log out, the program closes and, consequently does not run hourly as it is supposed to. If I log back in, the Startup folder launches the program again so it looks like it was running all along, but the files that are supposed to be created on the hour, were not created. If I click the exit button to get out of remote desktop, rather than logging out, the program continues to run and gives me hourly file creation. But that is not really an acceptable workaround.
What I am wondering is if it is possible to create the install package so this program runs as a service and will not be affected by my remote desktop user login?