I couldn't agree more about the importance of unit
tests. I don't know what Jamie had to do to hack the
Express product. However, the company that writes the
software gets to decide the licensing for it. And if
they also say you can't reverse engineer it, that's
their choice. I'm guessing he would have known he was
crossing the line on that. We all can petition all we
want but we don't get to just ignore their rules because
we think they're wrong.
MS is being lame about this. He should definately be an
MVP.
I'm not the greatest fan of the MVP award. I tend to
think that it is riddled with bias because you are not
necessarily recognised for the furtherence of computing
in general, but rather for the furtherance of Microsoft
and its take on computing. Don't misunderstand me - I'm
a big fan of the .NET Framework and I've built my career
around it. However, I do not aspire to become an MVP
because I will feel as though I would have sold out.
If anything, guys like Cansdale should be given a
lifetime MVP designation (same with folks who build
NDoc, NAnt, etc...).
That's a shame.
I've asked my lead what the hell 'MVP code of conduct'
means, because I certainly don't know what it is.
If what you suggest is true, it's a major blow for the
MVP program. People should be awarded for their
community work, and if that work is noteworthy, they
should get the reward. I mean, they also awarded an
ad-ware seller. Was that a good move? I don't know, but
is that of any particular relevance, not according to
me.
I use testdriven.net every day and I like it. That
doesn't mean the author of the tool should get an MVP
status per se, but it sure doesn't mean the MVP title
should be withdrawn because of it as well, especially
because he IS a community leader.
Hell, we are the community and I guess that we all agree
on the fact that he should be MVP.
How 'bout it Microsoft?
This bothers me. Both as an MVP and a daily user of
TestDriven.NET. It's a fantastic tool and it's one of
those rare tools that's on my list of "install always
and everywhere". I totally disagree wtih MS on this and
think they made a mistake. The fact that Jaimie figured
out how to get free tools running with the free IDE and
made it available, is stellar. While I understand MS
took a position that they didn't want people building
addins for the express SKUs, I think it's wrong to
chastise people for it. I'm sure if Roland and his
excellent GhostDoc tool had the same exposure that
TD.NET did, he might be facing a cease and decist notice
as well. It's sad that MS takes this approach with
people that make contributions to the community. Now I'm
afraid that since I built a better mousetrap for
SharePoint (my SharePoint forums) will I get looked down
as a guy who doesn't play well with others and sent to
the minors? Bad decision on MS and I'm sure this isn't
the last we've heard of it.