| Su | Mo | Tu | We | Th | Fr | Sa |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | 6 | |
| 7 | 8 | 9 | 10 | 11 | 12 | 13 |
| 14 | 15 | 16 | 17 | 18 | 19 | 20 |
| 21 | 22 | 23 | 24 | 25 | 26 | 27 |
| 28 | 29 | 30 | 31 |
Browse archives
Syndicate
.net
WHY MONO IS NOT YET READY FOR MY BALLS
Submitted by reeses on Thu, 2005-12-01 14:55. | .net | balls | mono | programmingI've been working with .NET lately, first with JScript .NET, and now with C#. I'm writing a simple, simple application that does some stuff, and can run either on the command line, or via some Windows scheduling mechanism. I.e., either as a service or using Windows Scheduler.
There's this great property called System.Environment.UserInteractive in .NET that tells you if the application was executed interactively. This is a great opportunity to decide where to dump the output of your application. If it's true, spew to System.Console. If it's false, write to a file or, in the case of Windows, to the beautiful, beautiful Event Log, available via System.Diagnostics.EventLog, even -- no work necessary!