JohnLudlow

@Nikolai:Tell that to the PCL creation wizard!

Here's looking forward to the full featured version.

The assumption that seemed apparent from comments in the video was that mobile apps are the main concern. Personally, I'm not writing mobile apps. Even when I'm writing a reusable library, I'm generally not targeting Windows Phone but rather just ".NET".

For that reason alone it'd be good to see a more complete version that is closer to the original PEX, but simpler to use and more robust.

Another reason is that I still have to deal with .NET 3.5 code, so having a version of this that works with .NET 3.5 (but in a VS2012 project) would be great.

@gduncan411: Great minds think alike, eh?

I wonder how hard it would be to hook some motors up to the wheels, and have a NetDuino controlling the whole thing...

@gt65345: There's a pretty good show on .NET debugging with windbg http://channel9.msdn.com/Series/-NET-Debugging-Stater-Kit-for-the-Production-Environment

Won't complain if the Defrag Tools folks cover it in more detail as well though

@windev, are those crashing sample apps you have available? It might be useful to follow along and see if we get the same results (t'would confirm the debgging tools are set up properly on our boxes) and also play more with some of the scenarios you've demoed.

The video seems to bug out at 31:57.  Is anyone else having this issue or is it just me?

@windev: Hi Andrew.  That makes sense.  WinDbg is not a small topic, so it's good that you're covering it in detail

Thanks & keep up the good work

AppVerifier would seem like a good topic for next week

I want to use two space, I really do.  But our doc and UX people shout at me when I do that, so I kind of got out of the habit.  WIth all respect to Bill, his main argument is "good typographers say this and that so there".  I've never actually heard a good argument for using only one space after a full stop (period).

Using two spaces is better, and it's actually important now than in the days of typewriters.  Why?  Because with the proportional fonts we use these days, the space is typically narrower than in monospaced fonts (where the space if obviously the full with of a character), so a single space is not as effective at giving the "that sentence is done, here's the next one" message.  The full stop should do that, yes, but it's often missed or ignored as a printing artifact or mark on the screen. 

It seems like a small thing but if it alters the meaning of a piece of text because the reader doesn't realise they're now looking at a different sentence then the text has failed to do its job.

Pretty sure the VS2010 profiler has memory profiling.  Not sure if it's the best memory profiler, but pretty sure it's there.

But PerfView gives an obscene amount of information, and can be run without Visual Studio (you can drop it onto, say. an IIS box where an ASP.NET app is running and profile away) so it's still a win.