Today I used the .NET task to write some nifty code 😎 and wanted to exit my method at some point using an errorlevel.
Normaly I use the Environment.Exit(-1) to exit my app with an error, so I did in the .NET task.
Guess what happened? The Visualcron service stopped 😢 instead of exiting my method.
I could start the service again and connect to it using the client, but I would recommend people not to use this function if you still want to use Visualcron.
Edited by moderator
| Reason: Not specified
Uses Visualcron since 2006.