.NET 4.8 RTM Updates (#1008)

* .NET 4.8 RTM Updates

.NET 4.8 RTM Updates

Remove additonal files

Remove additonal files

.NET 4.8 RTM Updates

.NET 4.8 RTM Updates

.NET 4.8 RTM Updates

.NET 4.8 RTM Updates

.NET 4.8 RTM Updates

Adding .NET Framework 4.8

.NET 4.8 RTM Updates

* .NET 4.8 RTM Updates

* .NET 4.8 RTM Updates

* .NET 4.8 RTM Updates

* .NET 4.8 RTM Updates

* .NET 4.8 RTM Updates

* .NET 4.8 RTM Updates

Documentation/KnownIssues/README.md

@@ -2,6 +2,7 @@
 
 The following links provide the known issues about the various .NET Framework versions at the time of their release. They describe the underlying issue and how to resolve them. 
 
+- [.NET Framework 4.8](http://go.microsoft.com/fwlink/?LinkId=2086606)
 - [.NET Framework 4.7.2](http://go.microsoft.com/fwlink/?LinkId=863257)
 - [.NET Framework 4.7.1](http://go.microsoft.com/fwlink/?LinkId=852101)
 - [.NET Framework 4.7](http://go.microsoft.com/fwlink/?LinkId=825308)

data/platforms.json

@@ -82,6 +82,35 @@
         }
       ]
     },
+    {
+      "platform": ".NET Framework 4.8",
+      "alias": "net48",
+      "category": "netfx",
+      "supportInfo": {
+        "support": "Supported",
+        "link": ""
+      },
+      "popular": true,
+      "info": "http://go.microsoft.com/fwlink/?LinkId=2054306",
+      "supportedBy": [
+        "VS2019",
+        "VS2017"
+      ],
+      "runtime": [
+        {
+          "name": ".NET Framework 4.8",
+          "link": "http://go.microsoft.com/fwlink/?LinkId=2085155",
+          "directLink": "http://go.microsoft.com/fwlink/?LinkId=2085155&source=getdotnet&desc=dotnet48"
+        }
+      ],
+      "tools": [
+        {
+          "name": ".NET Framework 4.8 Developer Pack",
+          "link": "http://go.microsoft.com/fwlink/?LinkId=2085167",
+          "description": "The .NET 4.8 Developer pack includes 4.8 reference assemblies needed by Visual Studio and msbuild."
+        }
+      ]
+    },
     {
       "platform": ".NET Framework 4.7.2",
       "alias": "net472",
@@ -93,9 +122,10 @@
       "popular": true,
       "info": "http://go.microsoft.com/fwlink/?LinkId=863281",
       "includedIn": [
-        "VS2017"
+        "VS2019"
       ],
       "supportedBy": [
+        "VS2017",
         "VS2015"
       ],
       "runtime": [
@@ -316,6 +346,7 @@
       "info": "http://msdn.microsoft.com/library/w0x726c2(VS.90).aspx",
       "includedIn": [],
       "supportedBy": [
+        "VS2019",
         "VS2017",
         "VS2015",
         "VS2013"

releases/README.md

@@ -8,6 +8,7 @@ To get up-to-date with the latest versions of .NET Framework and Visual Studio,
 
 You can see what was included in each .NET Framework release. Some releases are now unsupported, as called out.
 
+- [.NET Framework 4.8](net48/README.md)
 - [.NET Framework 4.7.2](net472/README.md)
 - [.NET Framework 4.7.1](net471/README.md)
 - [.NET Framework 4.7](net47/README.md)

releases/net48/KnownIssues/776516-InvalidOperationException in System_Web_ni!System.Web.Hosting.RecycleLimitMonitor+RecycleLimitMonitorSingleton.AlertProxyMonitors.md

@@ -0,0 +1,20 @@
+# InvalidOperationException in ASP.Net-RecycleLimitMonitor-AlertProxyMonitors
+
+## Symptoms
+ASP.Net applications may crash intermittently due to an `InvalidOperationException` in
+`System_Web_ni!System.Web.Hosting.RecycleLimitMonitor+RecycleLimitMonitorSingleton.AlertProxyMonitors`.
+
+## Cause
+This issue was introduced when ASP.Net 4.7 separated cache management and memory monitoring. This new `RecycleLimitMonitorSingleton` monitors worker process private bytes usage against the recycling limit for the process, and when
+the limit is near, it alerts a set of "proxy monitors" in each registered AppDomain so they can take action to avoid a process
+recycle. The collection of "proxy monitors" being enumerated was not thread-safe, though, so new AppDomains spinning up or old
+AppDomains shutting down while this monitor enumerated the collection could result in this unhandled `InvalidOperationException`
+in the default AppDomain, causing a crash.
+
+## Workaround 
+There is no reliable workaround. If the environment does not tend to consume private bytes near the recycling limit, or if
+web app domain lifetimes tend to last the entire length of the process lifetime, then chances of hitting this issue are
+extremely minimal. More private bytes consumption and/or more AppDomain recycling increases the odds of hitting this exception condition.
+
+## Resolution
+A hotfix for this issue is planned for .Net 4.8. This page will be updated with a link to the hotfix when it becomes available.

releases/net48/KnownIssues/wpf-pma-window-drag.md

@@ -0,0 +1,7 @@
+# Per-Monitor DPI-aware WPF applications position mouse cursor incorrectly when dragging between monitors
+
+## Symptoms
+A user running a WPF application that enables the Per-Monitor DPI awareness feature introduced in .NET Framework 4.7.2 may notice that the mouse cursor is in a different location relative to the window after dragging the window from one monitor to another.
+
+## Cause
+This issue is caused by a calculation error when resizing and placing the window after switching DPI.

releases/net48/README.md

@@ -2,12 +2,23 @@
 
 You can learn about the changes made in the .NET Framework 4.8.
 
-- [Download .NET 4.8 Developer Pack build 3694](https://go.microsoft.com/fwlink/?linkid=2033281)
-- [.NET Framework 4.8 Early Access build 3694 Announcement blog post](https://blogs.msdn.microsoft.com/dotnet/2018/11/28/announcing-net-framework-4-8-early-access-build-3694/)
-- [Release notes](dotnet472-changes.md)
-- [Application compatibility](https://go.microsoft.com/fwlink/?linkid=863254)
+- [Download](http://go.microsoft.com/fwlink/?LinkId=2085155)
+- [.NET Framework 4.8 RTM Announcement blog post](https://go.microsoft.com/fwlink/?linkid=2054306)
+- [Release notes](dotnet48-changes.md)
+- [Application compatibility](https://go.microsoft.com/fwlink/?linkid=2053971)
 - [API changes](dotnet48-api-changes.md)
 - [Known issues](dotnet48-known-issues.md) 
 
 ## Release Notes by Product Area
 
+- [ASP.NET](dotnet48-changes.md#aspnet)
+- [BCL](dotnet48-changes.md#bcl)
+- [ClickOnce](dotnet48-changes.md#clickonce)
+- [CLR](dotnet48-changes.md#clr)
+- [Networking](dotnet48-changes.md#networking)
+- [SQL](dotnet48-changes.md#sql)
+- [WCF](dotnet48-changes.md#wcf)
+- [Windows Forms](dotnet48-changes.md#windows-forms)
+- [WPF](dotnet48-changes.md#wpf)
+- [Workflow](dotnet48-changes.md#workflow)
+