Static destruction in UWP c++

The c++ static destructors seem to never execute for me during UWP app termination, as I expect they should. I am unable to break and step through them in the debugger.
I did some search, and there are people asking essentially the same thing here and there - why isn't my destruction code being executed? - and there is not a proper definite answer that I can find.

There are resources describing the UWP app lifecycle, and how an app would be suspended and then possibly terminated. The suspended > terminated transition is pictured as passive, so much that it is even omitted from some of the state diagrams. While this probably makes sense from the abstract Lifecycle of a Managed App standpoint, the implementation side of things remains undocumented.

Is UWP really not required to execute all the code prescribed by the language standard? Or if it does, how do I see that in the debugger?

https://learn.microsoft.com/en-us/windows/uwp/launch-resume/app-lifecycle#app-execution-state

Fay Wang - MSFT 5,206 Reputation points

2020-08-18T05:14:27.28+00:00

Based on this document, it mentions your implementation type can't have a private destructor, the benefit of having a public destructor is that it enables deferred destruction. Maybe you could try to use final_release to notifying the implementation that it's time to clean up and then in turn calls the page's destructor. For more information about it, you could refer to this part.
Андрей Вахрушев 96 Reputation points

2020-08-20T13:24:15.983+00:00

Thank you but I am not trying to extend managed winrt types .

Share via

Static destruction in UWP c++