@Shayan_Anique: It was taped pre-GA (3rd Oct). My laptop is now Windows 8.
@dentaku: Try Best Buy. They are definitely selling the OS and devices. And there is always the MS Stores - if there is one nearby, it is worth the trip.
If you can wait a week or so, you should see a new wave of x86/x64 touch devices hit the stores - the OEMs are releasing the rest of their models just before Thanksgiving.
It's correct - it just got reposted here as the other post was associated with //build/, and not Defrag Tools. The plan was to post the //build/ video last week and post a new episode this week, but we got too far behind schedule. The WinDBG series will return next Monday - with an episode on SOS.
Just watched all 34 episodes back-to-back. (Power was out in the office so I thought I'd make the most of the day).
Wow, what a great series. I'm a Win32 C++ guy, with little UI or C# experience, and I followed along easily with all the concepts Bob presented. I'm enthused to write my own app now - just need an idea... Maybe something to do with my series "Defrag Tools"? Tip of the day/week perhaps?
@felix9: The Defrag Tools series arose as a spinoff of Defrag Show so that troubleshooting tools in general could be covered at depth. We did a lot of research in the forums and this was one of the posts we paid a lot of attention to. Golnaz (our great studio operator) organized Brad to tackle the managed code aspect of windbg in his series (http://channel9.msdn.com/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment) - while we were planning Defrag Tools.
On Defrag Tools, we're being more generic than Brad's series and are talking about the basic commands and the underlying OS constructs you need to know about. We'll defer to Brad's series for specific (deep) managed code debugging tips. We will and do cover the basics (next week is all about getting SOS loaded - for example) of managed debugging.
This is a show for you - steer us in the direction you want us to go... If you want more than 10 episodes on WinDbg, tell us that and we'll hold off transitioning to xperf and will keep on producing windbg content for you. Chad and I both train the user and kernel mode courses within Microsoft and can easily continue to dive deeper and wider - from the physical hardware, up through kernel mode, through user mode and up in to high constructs like managed and WinRT application code.
@James: we have 5 in the bag and still at least 3 more to tape to just cover the basics. I expect another 5-10 after that on advanced stuff.
The main issue with reducing the courses down to a show format is the inability to interact with the students. When we get in to some particular concepts (breakpoints come to mind), we'll provide examples that you can (and should) repeat at home - as showing it once won't suffice.
The other struggle for Chad and I is doing all of the debugging with public symbols and extensions - we have internal tools that rely on private symbols that get us to root cause within seconds (this is how OCA and WER scale). Its a training exercise for us too to do it the public way!
Next week is loading SOS, then there are 2 on kernel, then 3 on useful commands. Well then go on to scenario based episodes using advanced techniques.
Multi-process - will be sure to cover that .. It's not too hard if you use the right tool.
The content is hard - yep wrong word - it is just information overload as you say - and we plan to keep it that way abd never miss a deep dive in to a concept.
Once all this is done, we'll cover xperf - which is debatable more powerful than the debugger.
Thanks for watching.
[Update: 2012-10-26: This is fixed in ProcDump v5.1]
Due to a bug in ProcDump v5.0, when using -x <folder> <appusermodeid>, some applications get "RPC server not available" exceptions and then fail. The workaround is to debug the package (not the app) and manually activate the application.
procdump.exe -ma -e 1 -f "" -x c:\dumps <packagename>