UPDATE: GotDotNet Workspaces Troubles Solved, RTFM anyone?
The stunning Betsy Aoki, the Community Program Manager for MSDN and TechNet emailed me earlier with details on my recent GotDotNet troubles. (Reminder, I met Betsy at a recent Nerd Dinner. She found me to be dapper, and preceded to be cyber-stalked by one Phil Weber ;) )
Betsy has kindly pointed out that most of the GDN problems are caused by what she calls "unclean Passport cookies." I'm unclear on why I'm unclean, but a clear of the browser cookies and cache and a little mercurachrome cleared the whole thing right up.
She has also seen fit to update the GotDotNet FAQ with all the details on how to fix troubles you may have.
Turns out that not all that fails to glitter fails on the server-side, if I may mix my metaphors. The new GDN FAQ has good information that solved my problem; do spread the word to people in need of assistance.
About Scott
Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.
About Newsletter
http://www.mercurochrome.org/
Love your blog!
Comments are closed.
Thanks for the update. I've had this problem numerous times in the past, and usually get an email from Betsy telling me to clear my cache and logout of passport, etc...
I don't want to be too negative, especially about a free service, but this seems to me to indeed be a problem with GDN on the server side, or at least a problem with Passport auth in general. It's not enough to have a FAQ that instructs the user to do a bunch of stuff to get the site to work.
You just can't ask your users to jump through so many hoops, just to see the site. Or they'll leave.
I enjoy your blog. Keep up the good work!
-Brendan