"Aaron [SQL Server MVP]" wrote in message
news:eb**************@TK2MSFTNGP15.phx.gbl...
:> Here's the new link:
: >
:
http://msdn.microsoft.com/library/en...f33a651779.asp
:
: Oh great. I love when they change all the URLs and leave orphans out
there.
: The least they could do is have the 404 pages triggered correctly.
:
: Anyone feel like going through 47 FAQ articles and updating URLs?
I'd do it but not for free or you could always write a script to do it.
(O:=
Perhaps there should be a ASPFAQ re: history of ASP reference links, why
they change and how often. Perhaps they're on a schedule and we just don't
realize it.
: I don't
: have a problem with the changes to the KB format, because that's all in a
: function (as long as the KB # stays the same, of course). Destination
URLs
: where the page names actually change, that's nothing short of a royal
PITA.
It sounds like MSFT is not taking their own advice about never testing in
production. I wish they would take these people and put them on repairing
issues with IE and quit worrying about changing links. Why does this happen
anyway? Did someone look at the link and say, "You know, that link is just
not making it for me. What would be better would be this _____________"
And someone else says, "Ya', that looks better but Aaron's gonna' be PO'd!"
To which she responds with, "Ya', I know... *giggle* ... but it's just too
good. LET'S DO ITTTTTTTTT!!!!"
Or, perhaps it is just because Steve's brother-in-law needs a job? (O:=
http://msdn.microsoft.com/library/de..._vbom_seso.asp http://msdn.microsoft.com/library/en...f33a651779.asp
After looking at them side-side, I have to agree, the new one is a lot more
attractive. Don't you agree?