MSDN feature suggestions
Have an idea for how we can improve the overall experience on MSDN? If so, we’d love to hear it. You can submit a new idea or you can upvote and comment on existing ideas. Suggestions, comments, and votes will be reviewed directly by the engineering teams who are responsible for building MSDN.
This site is for feature suggestions and ideas, not for submitting bugs or to get support. To file a bug or get support, visit MSDN troubleshooting and support.
Thanks from all of us on the MSDN Engineering team!
-
840 votes
-
Have better explanations for MSDN library topics
Many of the topics are very poor documented or documented with meaningless information which can be understood from the name of the class or property.
290 votes -
Syntax highlight on the website msdn.com
Please , make the website User Friendly.
The code looks terrible , because it is in black color . Why aren't you using any syntax highlight ? Look at the other sites with c# or any code . They highlight the CODE , and then it becomes readable.
This website is good , and the tutorials and examples are awesome, but the fact that there is not SH , makes me skip msdn.com website and look for another page.
279 votes -
Date stamp all articles in order to make it easier to know how how fresh the information is.
Date stamp all articles in order to make it easier to know how how fresh the information is.
218 votesThanks for your suggestion, Larry. We’re reviewing how we might be able to do this across this Library.
-
PLEASE fix the site navigation! Hire someone who can organize all the content.
The tree on the left always reflects incomplete info on the topic. I use Google to search MSDN. As an example, why are these in different places?
http://msdn.microsoft.com/en-us/library/hh510230.aspx
http://msdn.microsoft.com/en-us/library/dn135328(v=sql.110).aspx163 votesThanks for your suggestion, Vlad. We’re exploring different navigational models for the Library.
-
Give Code Example with Screen Shots.
Examplain and Give Code examples with screen shots. In the examples there are steps and code deployment which are lack of screen shots. The screen shots (output result) should be also there.
129 votes -
MSDN Site should be a responsive site, as your microsoft.com site is.
MSDN Site should responsive site, as your microsot.com site is.
66 votesMany areas in MSDN are already responsive. The Library it’s in our to do list
-
add an option to run the sample program
It will be nice if there is an option attached to every sample program that is provided in the documentation, so it comes handy to check the results by oneself
47 votesThat’s the general direction we are going. We just released Office 365 APIs documentation that features interactive APIs to Try REST calls from the page (e.g. Try buttons under GET request at http://msdn.microsoft.com/en-us/office/office365/api/mail-rest-operations#MessageoperationsGetmessages) and a Sandbox to run and play with code samples (e.g. Open button under JavaScript samples at http://msdn.microsoft.com/en-us/office/office365/howto/common-mail-tasks-client-library) . At this point the Sandbox is only capable to run JavaScript, but more languages and more APIs are coming soon… stay tuned!
(for more information see Brian Harry’s blog http://blogs.msdn.com/b/bharry/archive/2014/10/28/teched-europe-2014-news.aspx)
-
Fix the links in the MSDN documentation.
All too many MSDN articles contain links to internal Microsoft documentation that are no longer valid. I realize this is a Sisyphean task given constant changes to MS web structure, but it is critical nonetheless.
47 votes -
Add 1 or 2 small example with each property and method.or Add some detail explaination of property and method
when user go through the library, he/she found that method or property detail given at site is not sufficient to understand the concept.to solve this
1. Add more detail in explanation of property or method
2. Give reference link to understand properly, currently provided reference link is not relevant
3. Add the some small example in the property or method explaination47 votes -
Please make a settings at MSDN site to never ever ever display articles translated to Russian or any other language
Please make a settings at MSDN site to never ever ever display articles translated to Russian or any other language.
I'm Russian but it is very hard to read articles that were translated to Russian.46 votes -
Please add screen shot because "Picture is more than 1000 words"
Please add screen shot because "Picture is more than 1000 words".
43 votes -
provide screenshots and examples
This is new but...provide screenshots with examples
31 votes -
please give some real life programming examples to illustrate the use of oops concept in c#
The example given gives an idea. But how this concepts are applied in some real life concepts please explain.
and give some programming examples that uses all the oops concepts together in a particular program.25 votes -
Show me related content within the MSDN Library
When I visit a Library article I would like to see other related articles within the Library. Very often I find the reference docs, but then it's difficult to find more conceptual articles, or vice versa.
24 votes -
Where content is declared to be retired, it would be great if it was listed as obsolete or provided links to updated\superceding content
Where content is declared to be retired, it would be great if it was listed as obsolete or provided links to updated\superceding content.
23 votes -
Add simple code examples with sample inputs and sample outputs.
Add simple code examples with sample inputs and sample outputs like if you were explaining it to a baby or a non-technical person.
23 votes -
give a download link above the article
give a download link above the article
22 votes -
Organize SDK Reference Material by Technology and Layers
When developing systems using a particular technology, it would be helpful and more productive to be on a sub-site that only provides reference material, examples, community feedback, usage, and bug reports related to that technology. No links on a sub-site would catapult you into material that is not relevant to that site (as happens so frequently today).
Organizing these sites by layers and always showing the layer you are at would provide additional visibility into how technologies are structured. For example: DDK, Native NT, Windows API (formerly Win32 API), .NET, etc. This same organization technique could also be used to…
20 votes -
add more dynamics videos for getting started, especially in regards to the development environment; where there are none
specific commonly used functions, methods, ways of doing things so that learning C/AL code becomes easy not hard......
20 votes
- Don't see your idea?