Loading User Information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading User Information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements


hillr hillr
  • IE8: Dev Tools

    To ship is to choose.  I know how it goes.  Smiley
  • IE8: Dev Tools

    Why don't the developer tools show the HTTP response headers like Kothari's web dev helper?  Seems like an unfortunate omission or is it in there and I'm just not finding it?
  • Mike Barnett - Getting started with Code Contracts in Visual Studio 2008

    My guess is because any expressions (a == b || c != d) you put in an attribute (as a string) can't be verified by the compiler.   Any errors wouldn't be noticed until runtime.
  • Expert to Expert: Erik Meijer and Jeffrey Snover - Inside PowerShell

    IIRC Jeffrey said at his PDC session that CTP3 would be available in the December/January timeframe.

  • Visual Studio Debugger Tips & Tricks

    Data breakpoints is something I definitely miss.  Where you have properties in your own code it is easy enough to set a breakpoint in a setter.  But where the code isn't your own (think slot in an array or entry in a List<T>), it sure would be nice to be able to set a breakpoint on write.
  • A Lap around "Oslo"

    Where is the Intellipad download?
  • Microsoft .NET Framework: CLR Futures

    If I'm reading this right, finally having a way to generate useful minidumps for managed code will be a welcome addition.

  • Inside Parallel Extensions for .NET 2008 CTP Part 1

    Did you guys enable DRM on the high def WMV?  While I was viewing the HD WMV on Vista x86 SP1, mfpmp.exe (Media Foundation Protected Pipeline exe) consistently sucked down about 15% of my (single-core) CPU cycles.  Sad
  • Scott Hanselman: Value of Writing Windows PowerShell Cmdlets

    Good interview.  It is helpful to see how PowerShell is being utilized out in the wild (and in a commercial application no less).  BTW I have a bit of hard time with verb names also.  I think that it is really helpful to have a list of verbs and the corresponding PowerShell verb e.g delete/erase --> remove.  In fact, this might be a handy cmdlet to have (Get-StandardVerb -name delete --> remove).  However I think we might be a bit too stingy on the number of verbs.  Trust me, I don't want to see the verb list get too big but something like search (or find) is just such a common concept that one of the two (search or find) should be a verb IMO.
  • Windows PowerShell: Origin and Future

    +1 for what dot_tom says. And +1 for the request for VS Orcas to allow Pre/Post Build events to be executed as PowerShell script. 

    I've played with PowerShell since the early, early betas (post PDC 2003) and it has been my primary shell since September 2005.  I think the name is very fitting because it sets expectations appropriately.  PowerShell is very powerful but it takes a bit of investment to learn.  It is definitely not like your father's shell.  However that investment pays big dividends as you are then able to solve quite complex and/or tedious tasks with PowerShell very easily. 

    I totally agree with Bruce on WMI.  It seemed mysterious and weird to me until PowerShell totally lowered the barrier to entry with Get-WmiObject.  Now I'm blown away by how much information there is about a computer in WMI.  Since then I've taken those PowerShell learnings and have used them in my production C# code.

    As a .NET developer I really appreicate the REPL (read-eval-print loop) nature of PowerShell.  I rarely have to write one-off VS projects (ConsoleApplication42 anyone?) to experiment with some .NET type or formatting string.  This saves me quite a bit of time.  Most developers realize that to get ahead and set themselves apart from the average developer is to have mastered the right toolset.

    I've said this before and I'll say it again, it strikes me as ironic that one of the most innovative products to come out of Microsoft in the past year is a new command line interface.