Hi,

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.

Regards,
Erik

---

I have never used Environment.Exit, but isn't that a pretty brutal way of ending the application? Isn't it better to return int or throw an exception?

Thomas

Environment.Exit is stopping the hosting process and as VisualCron is executing your .NET code you will exit that application. I suggest you throw an exception instead.

---

I'll change (already did) my code to prevent this from happening again. An Exception is a good solution.

Regards,
Erik

---