October 2004 Entries
A Halloween Tale of Distributed Monsters

The nightmares of an architect’s past
leave little hope for this tortured cast.
As development nears the midnight hour,
your .NET solution is losing power.
Keyboards and mice are thrown about,
as an overstressed coder suddenly screams out.
The distributed monsters are creeping near,
for these mere mortals, there is plenty to fear.

Enterprise Services is the Frankenstein,
a sinister member of the DCOM line.
So many parts stitched to each other,
problems abound - one after another.
Your blissful job you can lay to rest,
this wicked brute will destroy the best.
If a working system you happen to contrive,
you’re sure to yell “It’s Alive! It’s ALIVE!”

Remoting you tried once upon a time,
but you soon perceived he’s not sublime.
Nice enough in his normal form,
but the Werewolves soon begin to swarm.
There’s no silver bullet to kill this beast,
you’ll think of security last but not least.
Much to dread about this scary fellow,
leave him alone or he’ll serialize you yellow.

Our Dracula Web Services has his sex appeal,
but the promise of immortality is not real.
Dark vampires lurk and angle brackets fly by,
eager to suck your bandwidth dry.
Garlic-throwing geeks at their nerd dinners,
silver-crosses and wooden splinters,
Who will save us from SOAP over HTTP,
from distributed monsters, set us free!

None other than Indigo, our Van Helsing,
sanity, scalability and interop you bring.
“Stop this nonsense” he says with a roar,
“Distributed systems are no more!
Services! Services is what it’s all about!
Tightly-coupled never works out.”
Escape now from your distributed mess,
With Indigo you’ll do more with less.

 

Ways to Protect Yourself Against the ASP.NET Vulnerability

There are several ways you can protect yourself against a possible ASP.NET Vulnerability:

  • Use UrlScan to block suspicious URLs before they even reach ASP.NET.
  • Follow the steps in this KB article (887459) to put code in your Global.asax files to block potentially dangerous URLs.
  • Add an HttpModule to your web.config or machine.config file that accomplishes the same thing in the KB article.

    The nice thing about the first and third options is you can cover an entire server with one step. If you don't have control over the server, you can protect your individual ASP.NET application using the second option.

  • An Exciting Week

    This week has been exciting to say the least. Earlier in the week, I was named a Regional Director along with Scott Watermasysk, Doug Seven and Jonathan Goodyear. Last night, I went out and celebrated with my family and Kevin and Kathy Schuler.

    After returning home, I checked my email and found out I received a Microsoft MVP award in the Visual Developer - ASP/ASP.NET community. So, now I have another excuse to celebrate.

    I'm really proud of both the Regional Director appointment and the Microsoft MVP award. The activities that are involved are my absolute favorite things to do related to my job. There is no better feeling when someone tells me after a presentation or a blog article or some other interaction that it really helped them understand a concept or technology or provided them some new insight.

    Thank you to those at Microsoft and to everyone in this community that put in a good word for me. These two awards are really motivating for me.