Merge pull request #69 from CommunityToolkit/feature/8.0.0-preview2-update

8.0.0-preview2 update

Author: Sergio0694

.git-blame-ignore-revs

@@ -0,0 +1,2 @@
+# Refactor to file-scoped namespaces
+4c8a30e4d6588d0921dca49e8ab3fb1c01e35c08

azure-pipelines.yml

@@ -16,22 +16,26 @@ variables:
 
 steps:
 - task: NuGetToolInstaller@1
+  displayName: Install NuGet tool
 
 - task: NuGetCommand@2
+  displayName: Restore solution(s)
   inputs:
     command: 'restore'
     restoreSolution: '**/*.sln'
     feedsToUse: 'config'
     nugetConfigPath: ./samples/nuget.config
 
 - task: VSBuild@1
+  displayName: Build UWP solution
   inputs:
     platform: 'x86'
     solution: '$(solutionUwp)'
     configuration: '$(buildConfiguration)'
     msbuildArgs: '/p:AppxBundlePlatforms="$(buildPlatform)" /p:AppxPackageDir="$(appxPackageDir)" /p:AppxBundle=Always /p:UapAppxPackageBuildMode=StoreUpload'
 
 - task: VSBuild@1
+  displayName: Build Xamarin.Forms solution
   inputs:
     platform: 'Any CPU'
     solution: '$(solutionXf)'

docs/mvvm/AsyncRelayCommand.md

@@ -9,9 +9,9 @@ dev_langs:
 
 # AsyncRelayCommand and AsyncRelayCommand<T>
 
-The [`AsyncRelayCommand`](https://docs.microsoft.com/dotnet/api/microsoft.toolkit.mvvm.input.AsyncRelayCommand) and [`AsyncRelayCommand<T>`](https://docs.microsoft.com/dotnet/api/microsoft.toolkit.mvvm.input.AsyncRelayCommand-1) are `ICommand` implementations that extend the functionalities offered by [`RelayCommand`](https://docs.microsoft.com/dotnet/api/microsoft.toolkit.mvvm.input.RelayCommand), with support for asynchronous operations.
+The [`AsyncRelayCommand`](/dotnet/api/microsoft.toolkit.mvvm.input.AsyncRelayCommand) and [`AsyncRelayCommand<T>`](/dotnet/api/microsoft.toolkit.mvvm.input.AsyncRelayCommand-1) are `ICommand` implementations that extend the functionalities offered by [`RelayCommand`](/dotnet/api/microsoft.toolkit.mvvm.input.RelayCommand), with support for asynchronous operations.
 
-> **Platform APIs:** [`AsyncRelayCommand`](https://docs.microsoft.com/dotnet/api/microsoft.toolkit.mvvm.input.AsyncRelayCommand), [`AsyncRelayCommand<T>`](https://docs.microsoft.com/dotnet/api/microsoft.toolkit.mvvm.input.AsyncRelayCommand-1), [`RelayCommand`](https://docs.microsoft.com/dotnet/api/microsoft.toolkit.mvvm.input.RelayCommand), [`IAsyncRelayCommand`](https://docs.microsoft.com/dotnet/api/microsoft.toolkit.mvvm.input.IAsyncRelayCommand), [`IAsyncRelayCommand<T>`](https://docs.microsoft.com/dotnet/api/microsoft.toolkit.mvvm.input.IAsyncRelayCommand-1)
+> **Platform APIs:** [`AsyncRelayCommand`](/dotnet/api/microsoft.toolkit.mvvm.input.AsyncRelayCommand), [`AsyncRelayCommand<T>`](/dotnet/api/microsoft.toolkit.mvvm.input.AsyncRelayCommand-1), [`RelayCommand`](/dotnet/api/microsoft.toolkit.mvvm.input.RelayCommand), [`IAsyncRelayCommand`](/dotnet/api/microsoft.toolkit.mvvm.input.IAsyncRelayCommand), [`IAsyncRelayCommand<T>`](/dotnet/api/microsoft.toolkit.mvvm.input.IAsyncRelayCommand-1)
 
 ## How they work
 
@@ -20,7 +20,7 @@ The [`AsyncRelayCommand`](https://docs.microsoft.com/dotnet/api/microsoft.toolki
 - They extend the functionalities of the synchronous commands included in the library, with support for `Task`-returning delegates.
 - They can wrap asynchronous functions with an additional `CancellationToken` parameter to support cancelation, and they expose a `CanBeCanceled` and `IsCancellationRequested` properties, as well as a `Cancel` method.
 - They expose an `ExecutionTask` property that can be used to monitor the progress of a pending operation, and an `IsRunning` that can be used to check when an operation completes. This is particularly useful to bind a command to UI elements such as loading indicators.
-- They implement the [`IAsyncRelayCommand`](https://docs.microsoft.com/dotnet/api/microsoft.toolkit.mvvm.input.IAsyncRelayCommand) and [`IAsyncRelayCommand<T>`](https://docs.microsoft.com/dotnet/api/microsoft.toolkit.mvvm.input.IAsyncRelayCommand-1) interfaces, which means that viewmodel can easily expose commands using these to reduce the tight coupling between types. For instance, this makes it easier to replace a command with a custom implementation exposing the same public API surface, if needed.
+- They implement the [`IAsyncRelayCommand`](/dotnet/api/microsoft.toolkit.mvvm.input.IAsyncRelayCommand) and [`IAsyncRelayCommand<T>`](/dotnet/api/microsoft.toolkit.mvvm.input.IAsyncRelayCommand-1) interfaces, which means that viewmodel can easily expose commands using these to reduce the tight coupling between types. For instance, this makes it easier to replace a command with a custom implementation exposing the same public API surface, if needed.
 
 ## Working with asynchronous commands
 
@@ -79,4 +79,5 @@ Upon clicking the `Button`, the command is invoked, and the `ExecutionTask` upda
 
 ## Examples
 
-You can find more examples in the [unit tests](https://github.com/Microsoft/WindowsCommunityToolkit//blob/master/UnitTests/UnitTests.Shared/Mvvm).
+- Check out the [sample app](https://github.com/windows-toolkit/MVVM-Samples) (for multiple UI frameworks) to see the MVVM Toolkit in action.
+- You can also find more examples in the [unit tests](https://github.com/windows-toolkit/WindowsCommunityToolkit/blob/rel/7.1.0/UnitTests/UnitTests.Shared/Mvvm).

docs/mvvm/Introduction.md

@@ -1,23 +1,25 @@
 ---
-title: Introduction to the MVVM package
+title: Introduction to the MVVM Toolkit
 author: Sergio0694
-description: An overview of how to get started with MVVM package and to the APIs it contains
+description: An overview of how to get started with the MVVM Toolkit and to the APIs it contains
 keywords: windows 10, uwp, windows community toolkit, uwp community toolkit, uwp toolkit, get started, visual studio, MVVM, net core, net standard
 dev_langs:
   - csharp
   - vb 
 ---
 
-# Introduction to the MVVM package
+# Introduction to the MVVM Toolkit
 
-The `Microsoft.Toolkit.Mvvm` package is a modern, fast, and modular MVVM library. It is part of the Windows Community Toolkit and is built around the following principles:
+The `Microsoft.Toolkit.Mvvm` package (aka MVVM Toolkit) is a modern, fast, and modular MVVM library. It is part of the Windows Community Toolkit and is built around the following principles:
 
-- **Platform and Runtime Independent** - **.NET Standard 2.0** 🚀 (UI Framework Agnostic)
+- **Platform and Runtime Independent** - **.NET Standard 2.0** and **.NET 5** 🚀 (UI Framework Agnostic)
 - **Simple to pick-up and use** - No strict requirements on Application structure or coding-paradigms (outside of 'MVVM'ness), i.e., flexible usage.
 - **À la carte** - Freedom to choose which components to use.
 - **Reference Implementation** - Lean and performant, providing implementations for interfaces that are included in the Base Class Library, but lack concrete types to use them directly.
 
-This package targets .NET Standard so it can be used on any app platform: UWP, WinForms, WPF, Xamarin, Uno, and more; and on any runtime: .NET Native, .NET Core, .NET Framework, or Mono. It runs on all of them. The API surface is identical in all cases, making it perfect for building shared libraries.
+This package targets **.NET Standard** so it can be used on any app platform: UWP, WinForms, WPF, Xamarin, Uno, and more; and on any runtime: .NET Native, .NET Core, .NET Framework, or Mono. It runs on all of them. The API surface is identical in all cases, making it perfect for building shared libraries.
+
+Additionally, the MVVM Toolkit also has a **.NET 5** target, which is used to enable more internal optimizations when running in on the .NET 5 runtime. The public API surface is identical in both cases, so NuGet will always resolve the best possible version of the package without consumers having to worry about which APIs will be available on their platform.
 
 To install the package from within Visual Studio:
 
@@ -30,11 +32,12 @@ To install the package from within Visual Studio:
     ```c#
     using Microsoft.Toolkit.Mvvm;
     ```
+
     ```vb
     Imports Microsoft.Toolkit.Mvvm
     ```
 
-3. Code samples are available in the other docs pages for the MVVM package, and in the [unit tests](https://github.com/windows-toolkit/WindowsCommunityToolkit/tree/master/UnitTests/UnitTests.Shared/Mvvm) for the project.
+3. Code samples are available in the other docs pages for the MVVM Toolkit, and in the [unit tests](https://github.com/windows-toolkit/WindowsCommunityToolkit/tree/rel/7.1.0/UnitTests/UnitTests.Shared/Mvvm) for the project.
 
 ## When should I use this package?
 
@@ -43,28 +46,37 @@ Use this package for access to a collection of standard, self-contained, lightwe
 The included types are:
 
 - **Microsoft.Toolkit.Mvvm.ComponentModel**
-  - `ObservableObject`
-  - `ObservableRecipient`
+  - [`ObservableObject`](ObservableObject.md)
+  - [`ObservableRecipient`](ObservableRecipient.md)
+  - [`ObservableValidator`](ObservableValidator.md)
 - **Microsoft.Toolkit.Mvvm.DependencyInjection**
-  - `Ioc`
+  - [`Ioc`](Ioc.md)
 - **Microsoft.Toolkit.Mvvm.Input**
-  - `RelayCommand`
-  - `RelayCommand<T>`
-  - `AsyncRelayCommand`
-  - `AsyncRelayCommand<T>`
-  - `IRelayCommand`
-  - `IRelayCommand<in T>`
-  - `IAsyncRelayCommand`
-  - `IAsyncRelayCommand<in T>`
+  - [`RelayCommand`](RelayCommand.md)
+  - [`RelayCommand<T>`](RelayCommand.md)
+  - [`AsyncRelayCommand`](AsyncRelayCommand.md)
+  - [`AsyncRelayCommand<T>`](AsyncRelayCommand.md)
+  - [`IRelayCommand`](RelayCommand.md)
+  - [`IRelayCommand<in T>`](RelayCommand.md)
+  - [`IAsyncRelayCommand`](AsyncRelayCommand.md)
+  - [`IAsyncRelayCommand<in T>`](AsyncRelayCommand.md)
 - **Microsoft.Toolkit.Mvvm.Messaging**
-  - `Messenger`
-  - `IMessenger`
+  - [`IMessenger`](Messenger.md)
+  - [`WeakReferenceMessenger`](Messenger.md)
+  - [`StrongReferenceMessenger`](Messenger.md)
+  - [`IRecipient<TMessage>`](Messenger.md)
+  - [`MessageHandler<TRecipient, TMessage>`](Messenger.md)
 - **Microsoft.Toolkit.Mvvm.Messaging.Messages**
-  - `PropertyChangedMessage<T>`
-  - `RequestMessage<T>`
-  - `AsyncRequestMessage<T>`
-  - `CollectionRequestMessage<T>`
-  - `AsyncCollectionRequestMessage<T>`
-  - `ValueChangedMessage<T>`
+  - [`PropertyChangedMessage<T>`](/dotnet/api/microsoft.toolkit.mvvm.Messaging.Messages.PropertyChangedMessage-1)
+  - [`RequestMessage<T>`](/dotnet/api/microsoft.toolkit.mvvm.Messaging.Messages.RequestMessage-1)
+  - [`AsyncRequestMessage<T>`](/dotnet/api/microsoft.toolkit.mvvm.Messaging.Messages.AsyncRequestMessage-1)
+  - [`CollectionRequestMessage<T>`](/dotnet/api/microsoft.toolkit.mvvm.Messaging.Messages.CollectionRequestMessage-1)
+  - [`AsyncCollectionRequestMessage<T>`](/dotnet/api/microsoft.toolkit.mvvm.Messaging.Messages.AsyncCollectionRequestMessage-1)
+  - [`ValueChangedMessage<T>`](/dotnet/api/microsoft.toolkit.mvvm.Messaging.Messages.ValueChangedMessage-1)
 
 This package aims to offer as much flexibility as possible, so developers are free to choose which components to use.  All types are loosely-coupled, so that it's only necessary to include what you use. There is no requirement to go "all-in" with a specific series of all-encompassing APIs, nor is there a set of mandatory patterns that need to be followed when building apps using these helpers. Combine these building blocks in a way that best fits your needs.
+
+## Additional resources
+
+- Check out the [sample app](https://github.com/windows-toolkit/MVVM-Samples) (for multiple UI frameworks) to see the MVVM Toolkit in action.
+- You can also find more examples in the [unit tests](https://github.com/windows-toolkit/WindowsCommunityToolkit/blob/rel/7.1.0/UnitTests/UnitTests.Shared/Mvvm).

docs/mvvm/Ioc.md

@@ -13,7 +13,7 @@ A common pattern that can be used to increase modularity in the codebase of an a
 
 The MVVM Toolkit doesn't provide built-in APIs to facilitate the usage of this pattern, as there already exist dedicated libraries specifically for this such as the `Microsoft.Extensions.DependencyInjection` package, which provides a fully featured and powerful DI set of APIs, and acts as an easy to setup and use `IServiceProvider`. The following guide will refer to this library and provide a series of examples of how to integrate it into applications using the MVVM pattern.
 
-> **Platform APIs:** [`Ioc`](Microsoft.Toolkit.Mvvm.DependencyInjection.Ioc)
+> **Platform APIs:** [`Ioc`](/dotnet/api/Microsoft.Toolkit.Mvvm.DependencyInjection.Ioc)
 
 ## Configure and resolve services
 
@@ -147,8 +147,9 @@ public ContactsView()
 
 ## More docs
 
-For more info about `Microsoft.Extensions.DependencyInjection`, see [here](https://docs.microsoft.com/aspnet/core/fundamentals/dependency-injection).
+For more info about `Microsoft.Extensions.DependencyInjection`, see [here](/aspnet/core/fundamentals/dependency-injection).
 
 ## Examples
 
-You can find more examples in the [unit tests](https://github.com/Microsoft/WindowsCommunityToolkit//blob/master/UnitTests/UnitTests.Shared/Mvvm).
+- Check out the [sample app](https://github.com/windows-toolkit/MVVM-Samples) (for multiple UI frameworks) to see the MVVM Toolkit in action.
+- You can also find more examples in the [unit tests](https://github.com/windows-toolkit/WindowsCommunityToolkit/blob/rel/7.1.0/UnitTests/UnitTests.Shared/Mvvm).