I tend to do all my debugging through page explorer in Visual Studio but this video certainly opened my eyes on a lot of features that I didn't know even existed in F12 especially the browser emulation for Windows 10 mobile.
Very interesting and enjoyable. Like the previous posters I too wold love to see more videos at this depth.
Fantastic idea of using a separate store for each universal app so you can page the whole thing out as one block when it is tombstoned/suspended.
One question - aside from the increased complexity, why is the memory compression not done on the modified list pages stage rather than the PF? It seems to me that all that is being achieved is you are using memory to make a compressed page file in memory, however this just adds to the memory pressure on the system which means more pages have to be moved to the PF.
I would be interested in others opinions on whether testing is only for purist and textbooks and is not practical in real world applications.
While "unit testing" seems great in theory, I struggle to see that it adds much value to larger applications. Basically it is lots of work to try and get code coverage and building fakes for very little return. Maybe it is just because as an old developer in my early days, my testing was "did it compile?"