Msdn Windows

[Ena Marklund]

MicrosoftDeveloper Network (MSDN) was the division of Microsoft responsible for managing the firm's relationship with developers and testers, such as hardware developers interested in the operating system (OS), and software developers developing on the various OS platforms or using the API or scripting languages of Microsoft's applications. The relationship management was situated in assorted media: web sites, newsletters, developer conferences, trade media, blogs and DVD distribution.[citation needed]

MSDN's primary web presence at msdn.microsoft.com was a collection of sites for the developer community that provided information, documentation, and discussion that was authored both by Microsoft and by the community at large. Microsoft later began placing emphasis on incorporation of forums, blogs, library annotations and social bookmarking to make MSDN an open dialog with the developer community rather than a one-way service.[2] The main website, and most of its constituent applications below were available in 56[3] or more languages.

MSDN Library was a library of official technical documentation intended for independent developers of software for Microsoft Windows. MSDN Library documented the APIs that ship with Microsoft products and also included sample code, technical articles, and other programming information. The library was freely available on the web, with CDs and DVDs of the most recent materials initially issued quarterly as part of an MSDN subscription. However, beginning in 2006, they were available to be freely downloaded from Microsoft Download Center in the form of ISO images.[4][5][6]

Visual Studio Express edition integrated only with MSDN Express Library, which was a subset of the full MSDN Library, although either edition of the MSDN Library could be freely downloaded and installed standalone.

In Visual Studio 2010 MSDN Library was replaced with the new Help System, which was installed as a part of Visual Studio 2010 installation. Help Library Manager was used to install Help Content books covering selected topics.

In 2016, Microsoft introduced the new technical documentation platform, Microsoft Docs, intended as a replacement of the TechNet and MSDN libraries.[7][8] Over the next two years, the content of the MSDN Library was gradually migrated into Microsoft Docs.[9] In 2022, Microsoft Docs was itself incorporated into Microsoft Learn. MSDN Library pages now redirect to the corresponding Microsoft Learn pages.[citation needed]

Each edition of MSDN Library could only be accessed with one help viewer (Microsoft Document Explorer or other help viewer), which was integrated with the then current single version or sometimes two versions of Visual Studio. In addition, each new version of Visual Studio did not integrate with an earlier version of MSDN. A compatible MSDN Library was released with each new version of Visual Studio and included on the Visual Studio DVD. As newer versions of Visual Studio were released, newer editions of MSDN Library did not integrate with older Visual Studio versions and did not even include old/obsolete documentation for deprecated or discontinued products. MSDN Library versions could be installed side-by-side, that is, both the older as well as the newer versions of MSDN Library could co-exist.[citation needed]

MSDN Forums were the web-based forums used by the community to discuss a wide variety of software development topics. MSDN Forums were migrated to an all-new platform during 2008 that provided new features designed to improve efficiency such as inline preview of threads, AJAX filtering, and a slide-up post editor.

Social bookmarking on MSDN Social was first launched in 2008, built on a new web platform that had user-tagging and feeds at its core. The goal of the social bookmarking application was to provide a method whereby members of the developer community could:

The initial release of the application provided standard features for the genre, including a bookmarklet and import capabilities. The MSDN web site was also starting to incorporate feeds of social bookmarks from experts and the community, displayed alongside feeds from relevant bloggers.[18]

MSDN Gallery was a repository of community-authored code samples and projects. Launched in 2008, the purpose of the site evolved to complement Codeplex, the open-source project hosting site from Microsoft. MSDN Gallery was retired in 2002 and all MSDN pages now redirect to the new code samples experience on Microsoft Learn.[19]

MSDN had historically offered a subscription package whereby developers had access and licenses to use nearly all Microsoft software that had ever been released to the public. Subscriptions were sold on an annual basis, and cost anywhere from US$1,000 to US$6,000 per year per subscription, as it was offered in several tiers.

Microsoft provided editorial content for MSDN Magazine, a monthly publication. The magazine was created as a merger between Microsoft Systems Journal (MSJ) and Microsoft Internet Developer (MIND) magazines in March 2000.[22] [23]

MSJ back issues were available online.[24] MSDN Magazine was available as a print magazine in the United States, and online in 11 languages. The last issue of the magazine was released in November 2019.[25]

MSDN was launched in September 1992[29] as a quarterly, CD-ROM-based compilation of technical articles, sample code, and software development kits. The first two MSDN CD releases (September 1992 and January 1993) were marked as pre-release discs (P1 and P2, respectively).[30] Disc 3, released in April 1993, was the first full release. In addition to CDs, there was a 16-page tabloid newspaper, Microsoft Developer Network News, edited by Andrew Himes, who had previously been the founding editor of MacTech, the premiere Macintosh technology journal.[31] A Level II subscription was added in 1993, that included the MAPI, ODBC, TAPI and VFW SDKs.[32]

MSDN2 was opened in November 2004 as a source for Visual Studio 2005 API information, with noteworthy differences being updated web site code, conforming better to web standards and thus giving a long-awaited improved support for alternative web browsers to Internet Explorer in the API browser. In 2008, the original MSDN cluster was retired and MSDN2 became msdn.microsoft.com.[33]

In 1996, Bob Gunderson began writing a column in Microsoft Developer Network News, edited by Andrew Himes, using the pseudonym "Dr.GUI". The column provided answers to questions submitted by MSDN subscribers. The caricature of Dr. GUI was based on a photo of Gunderson. When he left the MSDN team, Dennis Crain took over the Dr. GUI role and added medical humor to the column. Upon his departure, Dr. GUI became the composite identity of the original group (most notably Paul Johns) of Developer Technology Engineers that provided in-depth technical articles to the Library. The early members included: Bob Gunderson, Dale Rogerson, Rdiger R. Asche, Ken Lassesen, Nigel Thompson (a.k.a. Herman Rodent), Nancy Cluts, Paul Johns, Dennis Crain, and Ken Bergmann. Nigel Thompson was the development manager for Windows Multimedia Extensions that originally added multimedia capabilities to Windows. Renan Jeffreis produced the original system (Panda) to publish MSDN on the Internet and in HTML instead of the earlier multimedia viewer engine. Dale Rogerson, Nigel Thompson and Nancy Cluts all published MS Press books while on the MSDN team. As of August 2010, only Dennis Crain and Dale Rogerson remain employed by Microsoft.

A string, without whitespace, specifying the name of the browsing context the resource is being loaded into. If the name doesn't identify an existing context, a new context is created and given the specified name. The special target keywords, _self, _blank (default), _parent, _top, and _unfencedTop can also be used. _unfencedTop is only relevant to fenced frames.

A string containing a comma-separated list of window features in the form name=value. Boolean values can be set to true using one of: name, name=yes, name=true, or name=n where n is any non-zero integer. These features include options such as the window's default size and position, whether or not to open a minimal popup window, and so forth. The following options are supported:

Indicates that you want the browser to send an Attribution-Reporting-Eligible header along with the open() call. This call must be made with transient activation (i.e. inside a user interaction event handle such as click), within five seconds of user interaction. On the server-side this is used to trigger sending an Attribution-Reporting-Register-Source header in the response to complete registration of an attribution source.

By default, window.open opens the page in a new tab. If popup is set to true, it requests that a minimal popup window be used. The UI features included in the popup window will be automatically decided by the browser, generally including an address bar only. If popup is present and set to false, a new tab is still opened.

There are a few legacy features, which used to control UI features of the opened window. In modern browsers, they only have the effect of requesting a popup. If popup is unspecified, and windowFeatures contains any features (including unrecognized ones) other than noopener, noreferrer, or attributionsrc, the window is also opened as a popup if any of the following conditions apply:

Note: Requested position (top, left), and requested dimension (width, height) values in windowFeatures will be corrected if any of such requested value does not allow the entire browser popup to be rendered within the work area for applications of the user's operating system. In other words, no part of the new popup can be initially positioned offscreen.

If the browser successfully opens the new browsing context, a WindowProxy object is returned. The returned reference can be used to access properties and methods of the new context as long as it complies with the same-origin policy security requirements.

3a8082e126