Contents tagged with .NET

  • Why developers shouldn't test their own software...

    My new wife (6 weeks today!) got her new business cards through her company's web-based application, and they say she now works for the "IT Department". Which was a bit of a surprise, considering that she's a clinical research technician for a large pharamceutical company.

  • A belated "thanks!"

    I've been involved in a number of developer conferences over the years and one of the biggest joys of doing these shows can be the people you meet (also one of the biggest...er...challenges as I recall a fellow who followed me off the stage, into the men's room, and then out the door into a cab before I asked "are you going to the airport too?").

  • VB6 Migration BOF at TechEd

    I'm the host (the TechEd schedule says "speaker" <sigh>) for "Migrating VB6 to VB.NET" at TechEd on Tuesday night from 6:30 to 7:30. Of course, we're going to talk about migrating applications, not the VB product itself...

  • "The debugger is not properly installed"

    I too have been a victim of this dreaded problem, likely caused by installing and uninstalling various beta versions of .NET 2.0 frameworks and tools. A great post by Gregg Miskelly (a dev on the VS debugger team) offered tons of promising looking tips, none of which worked. (note: Does anyone know how to interpret the output of DebuggerDiagnostics.exe?).

  • When Alan talks...

    I mentioned Alan Cooper's keynote at the patterns & practices Summit a couple of weeks back. Alan's talk about "Ending the Death March" was - as expected - outstanding. Here's a picture from the kickback room after his talk with some of our speakers - including Ward Cunningham, Gregor Hohpe, and Rocky Lhotka (headless, on the left) - sitting with Alan and some of attendees:

  • VSLive gets a strong endorsement

    Julie just IMed me to point out that Chris Sells blogged that "I Think VSLive Is *It*". I've been working with Fawcette for a long time - this was my 12th annual show in SF with them - and along the way I guess I just took that for granted.

  • Security piece finally makes it to MSDN

    It took more than a year, but a piece I wrote reviewing "best practices" security principles as applied to the well-known .NET "reference" applications (PetShop, F&M, Duwamish) finally made it onto MSDN last week. As you might imagine, the security aspects of these applications don't stand up well when a strong light is shown on them. And yet...what else is there? How are developers, designers, and architects supposed to deal with security when all they have to look at is simple marketing-oriented demos or 2,000 pages of detailed guidance, with nothing in between?