>>Can't suck me in with your (re)interpretations.
>
>I've heard enough people use the arguement that it probably won't work right just cause its MS, and thought thats what you were implying. Sorry if thats not what you meant

I wasn't talking about "a bug".

Let's put it this way, I like to be optimistic (as you seem to be), but optimism won't get the job done when you're in a crunch. (And I've paid my money; I have no choice; I have to use "wawa" for at least the next year, whether I like it or not).

Office XP and "wawa" is one thing, but when you're dealing with umpteen different products/components (like MSDN Universal), the odds of component failure increases (significantly ?). I'm not zeroing in on "a bug"; it's the procedural aspects that concern me. For all I know, the "commercial distributions" may wind up being flawless; there's more of a "public image" thing involved there.

In general though, I find the handling of MSDN (Universal) subscriptions rather sloppy; eg. missing product keys, deleted FoxPro knowledge bases, "expired software", the mishandling of "MS passport" and MSDN subscription/IDs, etc.

(If you want to assume that every day is a "new day", fine ... but I still base some of my decisions/opinions on past experiences. Do you really think that programmers not getting access to their tools would make news ? Do you think a couple of thousand "Office Users" would ?)

Anyway ... for the most part, the (old) "MSDN system" was working for me; if I needed IMMEDIATE access to something in my suite to address a customer issue, I could do it. Past experiences indicate that this new level of "wawa" is not going to keep things simple, and insure my ability to respond to User needs is unfettered.

(And the day will come when I need to reinstall "everything" 10 times over in order to shake out a hardware problem; I build/upgrade my own).

I have yet to hear of one instance of "MSDN Subscription piracy". Leave well enough alone.

And give me a break on the price increase; I use MSDN to "promote" MS; I'm not writing Linux software. It's like having to pay (more) for a company car.