Trace application flow easily

UWP applications are compiled using .NET Native compiler as detailed here.
This process gives many advantages over JIT compilation:

• -Up to 60% performance improvement on cold startup times
• -Up to 40% performance improvement on warm startup times
• -Less memory consumption of your app when compiled natively
• -No dependencies on the desktop .NET Runtime installed on the system
• -Since your app is compiled natively, you get the performance benefits associated with native code (think C++ performance)
• -You can still take advantage of the industry-leading C# or VB programming languages, and the tools associated with them
• -You can continue to use the comprehensive and consistent programming model available with .NET– with extensive APIs to write business logic, built-in memory management, and exception handling.

This brings a side effect: Since app is compiled natively and logged StackTrace information is lost resulting in a series of meaningless series of entries like:

SharedLibrary!<BaseAddress>+0x38449f at
SharedLibrary!<BaseAddress>+0x3842cd Exception_EndOfInnerExceptionStack at
SharedLibrary!<BaseAddress>+0x384405 at
SharedLibrary!<BaseAddress>+0x3bd80d at
SharedLibrary!<BaseAddress>+0x3c1f45 at

that tells you nothing about what happened until reported exception, so the only real solution is to keep track of your workflow using custom made logging like:

but this is absolutely tedious and repetitive, so we can simplify it using a good old C# trip based on coupling using keyword and IDisposable.

Let’s create a TraceSession class this way

With this class we can log any part of our code this way:

Much more easier and readable since all you have to do is essentially to write your code inside using block, if you paired this with a Visual Studio code snippet that generates initial code skeleton implementation becomes nearly invisible.