@loverboy: What do you mean? Did they get stripped in a post?
(Yes, codemachine has a great debugger extension)
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
@Ben: To avoid ProcDumpExt executing .loadby sos mscorwks/clr & .cordll -l, after detecting the CLR present, make this environment variable and set it to 0.
setx PROCDUMPEXT_LOADCORDLL 0
In a version of ProcDumpExt I'm running (v7.7), it doesn't do the loading if SOS is already loaded. I'll look in to releasing it after I make sure all the new functionality isn't Microsoft Internal.
I'm a fan of MOCA based networking. You use your TV cabling as the network backbone - at about 100Mbps at each port, and 200-300Mbps on the backbone. I have a Netgear based solution with 4 units - but it isn't sold anymore. Motorola sells a similar system:
@RonaldLP: I've reported it to Mark.
@DarkWalker: Both PCs are a Surface Pro (v1). Larry's has a skin on it. Rob's has some stickers.
@s3curityConsult: Seen the news on that too. Our position wasn't clearly stated in that interview. The test in question tests scenarios that aren't our focus for various (good) reasons.
Correct, the DLL is no longer mapped in to the process VA Space. The kernel keeps a record of the modules ever loaded, and the dump is written with this metadata. .dumpdebug will show you the record in the dump metadata streams.
@Anatoli: Yep, need to do that still. It's on the to-do list.