An ongoing blog run by the managers of the online and offline MSDN Subscriptions program.
Browse by Tags
All Tags »
UX Updates (RSS)
-
The subscriber community provided GREAT feedback and suggestions on the design of the new subscriber downloads experience that we released in July. We were able to incorporate many of your suggestions into the final design, and the feedback we received Read More...
|
-
RSS Feed is now available for new MSDN Subscriber Download content Alternative Navigation through the A-Z Product Family List Page (see the link in the right rail from http://msdn.microsoft.com/subscriptions/downloads ) And - starting soon we will also Read More...
|
-
We have been taking note of your input on the new UI - positive and negative - and we are looking at changes we can make in the short and longer term to address the feedback. The first pain point we heard was the missing "New in Downloads" list, and we Read More...
|
-
There are now links to a list of New Subscriber Downloads on the MSDN Subscriptions Home Page and the MSDN Subscriber Downloads Page. The links are live on the English pages now and they will be added to the international sites in the next few days. We Read More...
|
-
We have a lot of reports that Visual Studio Professional Subscribers are not seeing any downloads besides the MSDN Library - we are looking at this right now. Sorry for the hassle. Read More...
|
-
As of 20:00 (8:00PM US PDT), the new Subscriber Downloads and Product Keys UI is live for MSDN and TechNet Subscribers. There are a few site-wide (all MSDN and TechNet) CSS issues that were noticed in advance of the release, that will continue to be looked Read More...
|
-
April 10 0930AM (US PST): Deployment activities are now underway. We expect this will take several hours to fully complete - probably late afternoon or early evening (US PST). ___________________________ In a post a few months back I told you about the Read More...
|
-
3/5/08 UPDATE : We did not launch the new platform last week as we had expected to. We decided we should delay because the data re-architecting and validation was taking longer than we had anticipated. Additionally we identified a few usability issues Read More...
|
