MSDN Retired Reference Documentation

After more than a decade, both Microsoft Developer Network (MSDN) and TechNet have been retired by Microsoft. The retirement is done after migration of the entire collective data. The retirement is followed by releasing a more up to date Microsoft Docs as a cloud-based line.

Why MSDN and TechNet are retired?

It was obvious that changes needed to be made and web experience must be modernized. The initial approach that Microsoft conducted was making evaluation to their current content configuration of MSDN and TechNet. Either one of them are developed on over a decade-old weak codebase with an old distribution and operation infrastructure. Those elements were not built to be able to operate on cloud system.

  1. Modernizing New Development

Not only focusing on the experience, they also crack down on the content development and the way of developers using it. People have spoken to Microsoft go the extra miles of creating compatible script with rich-feature content. This is intended to help them put solutions into practice of their business’ issues. Microsoft understood that the existing platform for content have to be uncomplicated for people to study and set out the solutions.

As the Enterprise Mobility Documentation project has been conducted, more documents were transferred to the latest Microsoft Docs website. A number of features involve mobile-compatible and responsive web design, navigation development on website, reading time estimation on articles, and support for notation. It also includes the capability to switch the web themes between light and dark.

  1. What does the New Windows Docs Offer?

Some would state that the retired services have yet operating on cloud for years. Indeed, they have. However, those systems were heavy, unresponsive, and outdated. Microsoft wanted to develop something without using anything that already exists as replacement. Many developers are happy that Microsoft are improving the knowledge-based system and responding to what MSDN or TechNet lack of.

For example, perhaps you are currently learning to build up application on Windows by using Entity Framework. Model View Presenter (MVP) pattern is the recommended design to do that. However, you might find some articles about MSDN that mention retired content of MVP. This might confuse you whether to get used to MVP or just apply it in the WinForms. You might also wonder if there is a more recommended design pattern you must apply.

  1. What Must We Learn?

The answer is you must keep at using MVP as the supervising controller when applying on the windows forms development. Why there are retired content is for the reason that Microsoft is really devoted in the new Windows operating system and Metro Style apps. In the next development, you must build apps by using C# program, C++ language, Windows Presentation Foundation, JavaScript and HTML5. Therefore, it seems sensible to at least gain knowledge of those.

Although Windows forms development is not officially retired, you should not really look forward to Microsoft’s attention. You may want to be taught with at XAML and MVVM because the models of every design pattern for user interfaces are no different. For that reason, understanding model-view controller, presenter, or view model will help you comprehend the others.

Latest posts by Harris Barkins (see all)

Leave a Reply

Your email address will not be published. Required fields are marked *