I really, really hate to complain about a very large piece of software because I understand the difficulties involved in developing such a thing. I also donâ€™t like offending people, as I know when people say â€œx sucksâ€ and there is an author of x then that author canâ€™t help but get their feelings hurt. However, I feel like the community features are an afterthought at Microsoftâ€™s MSDN site, and Iâ€™m really tired of trying to deal with it. Maybe someone will read this and fix it, but I doubt it.
First, I donâ€™t understand why MSDN is so slow. I understand itâ€™s a large site servicing thousands of connections per minute, but so is Amazon and somehow I donâ€™t have 10-second delays when accessing that. OK, fine, Amazon targets a different audience and perhaps their software can be optimized. That doesnâ€™t explain why if I simultaneously try to visit a blog hosted on Blogger and MSDN, the MSDN blog is still loading 10 seconds after the Blogger page is done loading. This is true for all parts of the MSDN site: blogs, forums, newsgroups, technical documentation. Whatâ€™s the deal?
Next, some community features. The forum software is pretty neat, but new categories are added at a glacial pace and theyâ€™re really dated. The VS 2008 forums were clearly marked for â€œdiscussion of the Visual Studio Codename Orcas Betaâ€ at least until VS 2008 SP1 was released. Iâ€™m just glad thereâ€™s a couple of them devoted to WPF. However, so far Iâ€™ve got about 4 active questions with 0 replies; at least in the WPF design time forum (which they still call by its codename for some reason) it looks like the only way you have a chance of getting a reply is to ask a simple question like, â€œI havenâ€™t opened Visual Studio yet and I need to. How do I do this?â€ So far the most use Iâ€™ve gotten out of these forums is a good place to arrange my thoughts while I arrive at the solution myself.
The managed newsgroups are worse. As part of the MSDN subscription my company purchased, weâ€™ve got guaranteed response times to questions on the MSDN managed newsgroups. Except it doesnâ€™t look like theyâ€™ve updated their newsgroups in a while; thereâ€™s no newsgroups for WPF and not even a really good-looking place to pretend is associated with it. That doesnâ€™t matter though, because itâ€™s impossible for me to configure my MSDN managed newsgroups account.
If you want to get the guaranteed response you paid for, thereâ€™s a process you go through to associate an alias with your MSDN account. I presume this is so some automated tool they have can ping an appropriate person to find someone that can respond to the question. Since June 2007, when I tried to access this page, Iâ€™d get an error message after a 2-3 minute delay; the message basically said â€œsomething unexpected happen; try again in 10 minutesâ€. A couple of weeks ago, I got tired of it and used the concierge chat to see if maybe I was doing something wrong; it turns out the â€œConfigureâ€ link was broken for everybody and it had to be fixed. Go figure; a crucial link on a feature they charge money for was completely broken and it went nearly 2 years unnoticed. It got fixed in a couple of days, I configured a posting alias, then realized that I had found the answer to the question I wanted to ask through trial and error anyway. Today, I needed to ask a question, so I double-checked that my alias was configured. â€œNo alias configured.’â€ Huh. Weird. So I tried to configure it again. â€œWeâ€™re sorry, this alias is already in use.â€ Huh. Real weird. So I tried another alias: the old one with a 1 on the end. 5 minutes of waiting later, â€œThere was a problem connecting to the registration service. Try again in 10 minutes.â€ Hey, this sounds familiar! 10 minutes later, I try again with the new 1-suffixed ID. â€œWeâ€™re sorry, this alias is already in use.â€ CURSES! So it seems that if I try to register an alias, it fails for an unspecified reason. However, it does get so far as to registering the alias because after I get that unspecified error the next error tells me that my posting alias is already in use. Shouldnâ€™t this be a transaction thatâ€™s rolled back on failure?
I tried the concierge chat again, and the person confirmed this is a â€œknown issue with volume license subscribersâ€ and is â€œintermittentâ€. Funny, Iâ€™ve been barred from this feature for more than a year and itâ€™s described as an â€œintermittentâ€ issue. I wonder if thereâ€™s a word for the practice of selling a service but making it so difficult to obtain the service that itâ€™s not used? Surely someoneâ€™s been in trouble for it.
Iâ€™m genuinely frustrated here. The best resource for information about programming is other programmers, and MS has the framework in place to create a really great community of developers. However, theyâ€™ve chosen to needlessly obfuscate the communication process to the extent that Iâ€™m getting better answers from programming accidents than the MS â€œcommunityâ€.
Also protip if any MS employees decide to reply (occasionally it happens!): if you want me to contact you by email it is dreadfully important that you leave an email. Someone responded to some WPF comments I had one time and expressed an interest in an email discussion, but didnâ€™t leave an email. No email on his blog either. If you donâ€™t leave contact information I canâ€™t contact you.