Replacing OS version TBD placeholder with 'in the latest release...'

Author: drewbatgit

hub/apps/develop/widgets/implement-widget-provider-cs.md

@@ -80,10 +80,10 @@ public static Dictionary<string, CompactWidgetInfo> RunningWidgets = new Diction
 
 This example will declare some static strings to define the JSON templates for each widget. For convenience, these templates are stored in the member variables of the **WidgetProvider** class. If you need a general storage for the templates - they can be included as part of the application package: [Accessing Package Files](/windows/uwp/app-resources/uri-schemes#ms-appx-and-ms-appx-web). For information on creating the widget template JSON document, see [Create a widget template with the Adaptive Card Designer](../../design/widgets/widgets-create-a-template.md).
 
-Starting with Windows build [TBD - Build number], apps that implement Windows widgets can customize the header that is displayed for their widget in the Widgets Board, overriding the default presentation. For more information, see [Customize the widget header area](widget-header-customization.md).
+In the latest release, apps that implement Windows widgets can customize the header that is displayed for their widget in the Widgets Board, overriding the default presentation. For more information, see [Customize the widget header area](widget-header-customization.md).
 
 > [!NOTE]
-> Starting with Windows Build [TBD - Build number], apps that implement Windows widgets can choose to populate the widget content with HTML served from a specified URL instead of supplying content in the Adaptive Card schema format in the JSON payload passed from the provider to the Widgets Board. Widget providers must still provide an Adaptive Card JSON payload, so the implementation steps in this walkthrough are applicable to web widgets. For more information, see [Web widget providers](web-widget-providers.md).
+> In the latest release, apps that implement Windows widgets can choose to populate the widget content with HTML served from a specified URL instead of supplying content in the Adaptive Card schema format in the JSON payload passed from the provider to the Widgets Board. Widget providers must still provide an Adaptive Card JSON payload, so the implementation steps in this walkthrough are applicable to web widgets. For more information, see [Web widget providers](web-widget-providers.md).
 
 ```csharp
 // WidgetProvider.cs

hub/apps/develop/widgets/implement-widget-provider-win32.md

@@ -160,7 +160,7 @@ struct WidgetProvider : winrt::implements<WidgetProvider, winrt::Microsoft::Wind
 
 This example will declare some static strings to define the JSON templates for each widget. For convenience, these templates are stored in the local variables declared outside of the **WidgetProvider** class definition. If you need a general storage for the templates - they can be included as part of the application package: [Accessing Package Files](/windows/uwp/app-resources/uri-schemes#ms-appx-and-ms-appx-web). For information on creating the widget template JSON document, see [Create a widget template with the Adaptive Card Designer](../../design/widgets/widgets-create-a-template.md).
 
-Starting with Windows build [TBD - Build number], apps that implement Windows widgets can customize the header that is displayed for their widget in the Widgets Board, overriding the default presentation. For more information, see [Customize the widget header area](widget-header-customization.md).
+In the latest release, apps that implement Windows widgets can customize the header that is displayed for their widget in the Widgets Board, overriding the default presentation. For more information, see [Customize the widget header area](widget-header-customization.md).
 
 > [!NOTE]
 > Starting with Windows Build [TBD - Build number], apps that implement Windows widgets can choose to populate the widget content with HTML served from a specified URL instead of supplying content in the Adaptive Card schema format in the JSON payload passed from the provider to the Widgets Board. Widget providers must still provide an Adaptive Card JSON payload, so the implementation steps in this walkthrough are applicable to web widgets. For more information, see [Web widget providers](web-widget-providers.md).

hub/apps/develop/widgets/web-widget-providers.md

@@ -8,7 +8,7 @@ ms.localizationpriority: medium
 
 # Web widget providers
 
-Starting with Windows Build [TBD - Build number], apps that implement Windows widgets can choose to populate the widget content with HTML served from a remote URL. Previously, the widget content could only be supplied in the Adaptive Card schema format in the JSON payload passed from the provider to the Widgets Board. Because web widget providers must still provide an Adaptive Card JSON payload, you should follow the steps for implementing a widget provider in [Implement a widget provider in a C# Windows App](implement-widget-provider-cs.md) or [Implement a widget provider in a win32 app (C++/WinRT)](implement-widget-provider-win32.md).
+In the latest release, apps that implement Windows widgets can choose to populate the widget content with HTML served from a remote URL. Previously, the widget content could only be supplied in the Adaptive Card schema format in the JSON payload passed from the provider to the Widgets Board. Because web widget providers must still provide an Adaptive Card JSON payload, you should follow the steps for implementing a widget provider in [Implement a widget provider in a C# Windows App](implement-widget-provider-cs.md) or [Implement a widget provider in a win32 app (C++/WinRT)](implement-widget-provider-win32.md).
 
 ## Specify the content URL
 
@@ -44,21 +44,21 @@ In the implementation of the **OnResourceRequested** method, widget providers ca
 ```csharp
 async void IWidgetResourceProvider.OnResourceRequested(WidgetResourceRequestedArgs args)
 {
-    if (args.Request.Uri == "Https://contoso.com/logo-image")
-    {
-        var deferral = args.GetDeferral();
+    var deferral = args.GetDeferral();
 
-        Func<Task> asyncLambda = async () =>
+    if (args.Request.Uri.Length > 0)
+    {
+        if (args.Request.Uri == "https://contoso.com/logo-image")
         {
             string fullPath = Windows.ApplicationModel.Package.Current.InstalledPath + "/Assets/image.png";
             var file = await StorageFile.GetFileFromPathAsync(fullPath);
-            var response = new WidgetResourceResponse(RandomAccessStreamReference.CreateFromFile(file), "", 200);
+            var response = new WidgetResourceResponse(RandomAccessStreamReference.CreateFromFile(file), "OK", 200);
+            response.Headers.Add("Content-Type", "image/png");
             args.Response = response;
-        };
-        await asyncLambda();
-
-        deferral.Complete();
+        }
     }
+
+    deferral.Complete();
 }
 ```
 
@@ -84,6 +84,9 @@ var message = $"{{ \"current_location\": \"{ location }\" }}";
 WidgetManager.GetDefault().SendMessageToContent("Weather_Widget", message);
 ```
 
+## Limitations and requirements
+
+* This feature is available only to users in the European Economic Area (EEA). In the EEA, installed apps that implement a feed provider can provide content feed in the Widgets Board.
 
 
 

hub/apps/develop/widgets/widget-header-customization.md

@@ -8,7 +8,7 @@ ms.localizationpriority: medium
 
 # Customize the widget header area
 
-Starting with Windows build [TBD - Build number], apps that implement Windows widgets can customize the header that is displayed for their widget in the Widgets Board, overriding the default presentation. Header customization is implemented in the Adaptive Card payload you pass to the OS from your widget provider, so the steps are the same regardless of the language your widget provider is implemented in. For a walkthrough of creating a widget provider, see [Implement a widget provider in a C# Windows App](implement-widget-provider-cs.md) or [Implement a widget provider in a win32 app (C++/WinRT)](implement-widget-provider-win32.md).
+In the latest release, apps that implement Windows widgets can customize the header that is displayed for their widget in the Widgets Board, overriding the default presentation. Header customization is implemented in the Adaptive Card payload you pass to the OS from your widget provider, so the steps are the same regardless of the language your widget provider is implemented in. For a walkthrough of creating a widget provider, see [Implement a widget provider in a C# Windows App](implement-widget-provider-cs.md) or [Implement a widget provider in a win32 app (C++/WinRT)](implement-widget-provider-win32.md).
 
 ## The default header
 
@@ -84,37 +84,3 @@ The following example demonstrates setting an empty header.
 } 
 ```
 
-## Override the header with Adaptive Card content
-
-You can overwrite the header with UI components defined using the Adaptive Card schema. The specified content will be rendered within the 48px high header area.
-
-The following example uses Adaptive Card components to render a combo box selector in the widget header.
-
-```json
-{ 
-    "type": "AdaptiveCard", 
-    "$schema": "http://adaptivecards.io/schemas/adaptive-card.json", 
-    "version": "1.6", 
-    "body": [
-        ...
-    ] ,
-    "header": [
-        { 
-            "type": "Input.ChoiceSet", 
-            "id": "WeatherSwitcher", 
-            "choices": [ 
-              { 
-                "title": "Redmond", 
-                "value": "Redmond" 
-              }, 
-              { 
-                "title": "Bellevue", 
-                "value": "Bellevue" 
-              } 
-            ], 
-            "placeholder": "Pick location", 
-            "value": "Bellevue" 
-        } 
-    ]
-} 
-```