RE: For Microsoft Partners and Customers Who Can't Download or Access

I've never had a bit of problem accessing MSDN, MSDN2, or MSDN Downloads
except on the day Vista was added to downloads - I had to click the link a
whole 6 times before I slipped into the queue. Considering the beating the
Microsoft servers took on that day, I feel pretty darn lucky at that. I
access MSDN and MSDN downloads on at least 6 different PCs, including Windows
2003 server, Windows XP, and Vista operating systems.

While I can't talk about all browsers, anyone who is developing for Windows
must certainly have access to IE6 or IE7 so, as far as I am concerned, it
matters little if other browsers work with MSDN or not. As it is, I have
made at least a quick test of MSDN on FireFox 1.5 in the past with no obvious
problems.

As for your statement that you are a professional, I disagree. While you
are wrong about your assertions, pretty much across the board, it is not the
fact that we disagree on those assertions that me think you're not very
professional at all. If you believe the sites to be flawed, I accept that it
is your privilege (not your right) to post your concerns here but it's not
what you're saying, it's how you're saying it.

I wonder if all those customers you list and quote on your website would
have the same respect for your professionalism if they saw this immature and
seemingly out of control rant.

Dale
--
Dale Preston
MCAD C#
MCSE, MCDBA


"clintonG" wrote:



To all Microsoft partners and customers who have been unable to download
recently or access ASP.NET documentation from the msdn2 website and for all
of those customers who have been lied to and misled by some of the sleazy
MVPs and the lying cockroaches that Microsoft has working for the company...

Microsoft has serious problems with their servers and websites. The entire
MSDN server farm and all download resources MSDN manages has been FUBAR for
at least two months now and longer in fact. The failures started way back
when Visual Studio 2005 was released. At least it is correct to say that is
when these recent failures began to be discovered by those who have paid
Microsoft thousands of dollars for MSDN subscriptions but have not been able
to download resources they paid for.

This is also widely known and discussed to some extent within other
newsgroups hosted by Microsoft and has become a serious problem for
developers who can not access the ASP.NET 2.0 documentation from the
dysfunctional msdn2.microsoft.com website. Yet, Microsoft has done what?

Like cockroaches Microsoft staff have lied and scurried away from the
problem without an honest acknowledgement of the problem and a concerned
attempt to at least explain what the company is doing to resolve these
failures.

So be prepared to continue to be lied to and misled by some of the MVP
cockroaches that use these newsgroups. The same will be true of the
so-called Product Managers who are closer to the problem and even less
honorable than the slime that function as MVPs. In other words, when the
cockroaches from tech support, Microsoft Product Managers, and some of the
slimier MVPs try to suggest you have a problem with your machine do not
allow them to manipulate you and put you to work for hours and perhaps days
wasting your time with troubleshooting. Their favorite lie is to suggest
people have a problem with the cache on the local machine. This has been
proven to be a lie by many people.

When this first occurred with Visual Studio 2005 -- I TRUSTED -- Microsoft
support and fell for the lies the cockroaches told. I was actually working
with Tier Two support who sent me troubleshooting scripts and documents I
had to carefully follow so I could run the scripts in order. I ran scripts
for those cockroaches for SIX HOURS and then the cockroaches told me we had
to start all over because the cockroaches said they sent me the wrong
scripts. I had enough of that ca-ca de toro and later that same evening
POOF! downloading started working again on any and all machines on my
network.

Because I consider myself a professional -- with integrity -- I have
recently once again tested and replicated Microsoft's recent server failures
on three different well maintained and service packed machines running XP
Pro, XP Home and Windows 2000 using IE6, IE7, FF1.5, FF2 and Opera9 because
I want to make sure I have done due diligence before the bottle rocket goes
off.

The msdn2.microsoft.com website is FUBAR and so is the Express Suite
website(s). MSDN Subscription Downloads continue to be FUBAR.

This is Microsoft's problem and the cockroaches the company has working for
it do not have the integrity to acknowledge this problem let alone
cooperatively help people understand what they are doing to try to resolve
the problem -- but -- a young lady from corporate sales called me the other
day as I am involved with the partner program and she did indeed ask about
this at my request and she returned to the phone to tell me "yes, my boss
just acknowledged there is something wrong with MSDN servers but I am not
technically skilled so I can't explain further."

I am asking everybody adversely affected by these failures to start
demanding a reasonable response to these failures.

<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://clintongallagher.metromilwaukee.com/
MAP http://wikimapia.org/#y=43038073&x=-88043838&z=17&l=0&m=h



.