This post was written by Wade Pickett
We are happy to announce ASP.NET documentation and guidance has been migrated to docs.microsoft.com!
Better Together and Great Features
This brings the ASP.NET documentation together with ASP.NET Core, C#, Entity Framework Core, Azure, Visual Studio, C++, and SQL on Linux.
docs.microsoft.com will allow for a consistent experience across documentation sets, in addition to supporting:
- Community contributions
- Social sharing
- Global localization supporting 45 languages
- Responsive mobile design
- Side-notes and comments
- Real-time table of contents filter
ASP.NET documentation is open for contributions in GitHub!
ASP.NET Core docs and now ASP.NET docs are open and available in GitHub where you can contribute to the docs and code samples directly or notify the community (which includes our teams here at Microsoft) of a doc issue.
You can also see what doc projects are under way and get involved to discuss approach, scope, and priority.
Take a look at these current projects and issues lists to discover community group efforts you might be interested in:
ASP.NET Core:
.NET Core:
There will be a big focus on the docs.microsoft.com site to continue to update both the content and site features. See up to date announcements here: https://docs.microsoft.com/teamblog/.
MSDN will be joined with docs.microsoft.com or it wil remain separate ?
And Visual basic .net….? And SPANISH…?
Because you give so little or no support to these themes using visual basic net …? Besides that they do not take into consideration the SPANISH language …..
Will the current links to the current MSDN pages be redirected to the new address? (ex. https://msdn.microsoft.com/en-us/library/015103yb.aspx ).
Most likely there are thousand of other sites on the net that point to the current MSDN URLs..
Will I be taken to the right place if I hit F1 while in Visual Studio? This was broken for a long time in the Visual Studio 2010 timeframe and there doesn’t seem to be any plans to maintain an offline copy that can be quickly consulted. As much as I like the Docs site, letting the Help function die on the vine is hardly encouraging.
Hi Cosmin!
We are working to get all of the remaining .NET content on MSDN to open documentation in GitHub and published on docs.microsoft.com. Here is an introduction to what we are doing with docs.micrsoft.com, why and how it related to MSDN and TechNet: https://docs.microsoft.com/en-us/teamblog/introducing-docs-microsoft-com. It essentially comprises what has been announced so far.
Thanks !
same question here, what will happen with F1 help key in VS jumping to MSDN?
MSDN has worked just fine for me so far.
Not needed:
> Social sharing (I guess this is a feature for MS employees that only have friends working at MS?)
> Responsive mobile design
> Global localization supporting 45 languages (can you find people willing to translate all of it and translate it well? And will be using Greek variable names be the next step in programming patterns? Because .NET Framework functions are in English and if you don’t know English having a documentation in Greek will not help)
> This brings the ASP.NET documentation together with ASP.NET Core, C#, Entity Framework Core, Azure, Visual Studio, C++, and SQL on Linux.
On Linux? Why? Couldn’t Linux users visit MSDN so far?
SQL on Linux is a new technology, like other technologies mentioned in this line, who’s documentation will move to DMC.
I wish I could download all the docs to my disk and view them in Help Viewer and especially to have local copy synced with online docs.
1. I hope F1 key will work correctly in VS in the near future.
2. My English is bad, but I prefer to read technical documentation in English. Please ***remove automatic translation*** altogether – it is useless.
3. Please remember my language preference. I’m on page https://docs.microsoft.com/en-us/. Notice selected culture in the URL. My browser has pl as the first preferred culture, en-us as second. I’m clicking on ASP.NET link – so far so good. Now I’m clicking on any link from ASP.NET Core tab. Those links are without culture in the URL, for example https://docs.microsoft.com/aspnet/core/getting-started and I’m redirected to https://docs.microsoft.com/pl-pl/aspnet/core/getting-started. Now on every page I see “Ta zawartość nie jest dostępna w Twoim języku.” (This content is not available in your language). If I want to read something about good old .NET I’m redirected to MSDN library, and usually I see texts translated automatically by Bing. I’m asking once again – please don’t do that! I hope that nobody will have a suggestion to change default culture in browser preferences. It is not an option because some pages display completely different content for different cultures – it is often used as poor geolocation API 🙂