I've got a windows service that I have to profile in production because I can't simulate the load pattern that is causing problems in a test environment.
I'm using the commandline dotMemory tool. I need to see allocation data so i can identify the direct causes of allocations without guessing. To do this i need to use the Back Traces tab but when I profile this tab isn't available. Can you provide a commandline example of how I would profile a windows service in a way that includes the data needed to inspect backtraces please?
Currently trying: dotmemory start-windows-service ServiceName