system.diagnostics

We initially didn't use any logging or debug tracing but after spending few weeks to trace down some data corruption we decided to put required Debug.Write and Trace for production and Debug.Assert So now question is What is the best practice to use debug and trace logging. I am just looking for some thing generic. public void AddRectodatabase(object record) { Debug.WriteLine(record.ToString()); Trace.WriteLine(record.ToString()); // Add it to databse Debug.Assert(true, "Use this on case by case basis"); } Is this good enough for general purpose, am i doing anything wrong in there? We want to

On Windows 8.1 you go into the task manager and check the list of processes, there are two lists: - One for "Apps", which are visible foreground apps - One for "Background processes", which are processes running in the background My end goal is to time how long it takes an application to load. When the application is still loading, it appears in "Background processes". However, once loaded, it appears in "Apps". This is going to be my criteria on what constitutes an app finishing loading. I am using a System.Diagnostics.Process object to try to accomplish this. However, I am struggling to come

I've been trying to work with ETW in .net 4.0. I have started using Microsoft EventSource Library 1.0.4-beta ( https://www.nuget.org/packages/Microsoft.Diagnostics.Tracing.EventSource ) Here is the code i written for generating events for my application. [EventSource(Name = "Samples-EventSourceDemos-EventSourceLogger")] public sealed class EventSourceLogger : EventSource { public static EventSourceLogger Log = new EventSourceLogger(); public static string GetManifest() { return GenerateManifest(typeof(EventSourceLogger), null); } [Event(200, Level = Microsoft.Diagnostics.Tracing.EventLevel

I'm trying to run the Windows System Assessment Tool (winsat.exe) using the following code: System.Diagnostics.Process WinSPro = new System.Diagnostics.Process(); System.Diagnostics.ProcessStartInfo WinSSInfo = new System.Diagnostics.ProcessStartInfo(); WinSSInfo.FileName = "cmd.exe"; WinSSInfo.Arguments = "/k winsat.exe"; WinSPro.StartInfo = WinSSInfo; WinSPro.Start(); This code works if I only call cmd.exe, and even if I call regedit.exe it still works. However, when I try to call winsat.exe as a argument of cmd.exe, it fails. The command prompt shows this: 'winsat.exe' is not recognized as

In my web.config I have: <system.diagnostics> <switches> <add name="logLevelSwitch" value="1" /> </switches> </system.diagnostics> Is there a way that I could call, for example: System.Diagnostics.TraceSwitch["logLevelSwitch"] to get the current value? Once you've defined the switch value in your web.config file, it's easy to get this value from your application by creating a TraceSwitch with the same name: private static TraceSwitch logSwitch = new TraceSwitch("logLevelSwitch", "This is your logLevelSwitch in the config file"); public static void Main(string[] args) { // you can get its