Remove Xamarin references (#44398)

Author: gewarren

.openpublishing.redirection.standard.json

@@ -318,6 +318,11 @@
             "redirect_url": "/previous-versions/dotnet/framework/data/xml/xslt/outputs-from-an-xsltransform",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/docs/standard/data/sqlite/xamarin.md",
+            "redirect_url": "/dotnet/standard/data/sqlite/",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/docs/standard/data/xml/resolving-external-xslt-style-sheets-and-documents.md",
             "redirect_url": "/previous-versions/dotnet/framework/data/xml/xslt/resolving-external-xslt-style-sheets-and-documents",

docs/ai/quickstarts/quickstart-local-ai.md

@@ -101,21 +101,21 @@ The Semantic Kernel SDK provides many services and features to connect to AI mod
     Tell me three facts about .NET.
 
     AI response:
-    1. **Cross-Platform Development:** One of the significant strengths of .NET, 
+    1. **Cross-Platform Development:** One of the significant strengths of .NET,
     particularly its newer iterations (.NET Core and .NET 5+), is cross-platform support.
     It allows developers to build applications that run on Windows, Linux, macOS,
     and various other operating systems seamlessly, enhancing flexibility and
     reducing barriers for a wider range of users.
 
-    2. **Rich Ecosystem and Library Support:** .NET has an incredibly rich ecosystem,
-    comprising an extensive collection of libraries (such as those provided by the 
-    official NuGet Package Manager), tools, and services. This allows developers 
-    to work on web applications (.NET Framework for desktop apps and ASP.NET Core 
-    for modern web applications), mobile applications (.NET MAUI or Xamarin.Forms),
-    IoT solutions, AI/ML projects, and much more with a vast array of pre-built
+    2. **Rich Ecosystem and Library Support:** .NET has a rich ecosystem,
+    comprising an extensive collection of libraries (such as those provided by the
+    official NuGet Package Manager), tools, and services. This allows developers
+    to work on web applications (.NET for desktop apps and ASP.NET Core
+    for modern web applications), mobile applications (.NET MAUI),
+    IoT solutions, AI/ML projects, and much more with a vast array of prebuilt
     components available at their disposal.
-    
-    3. **Type Safety:** .NET operates under the Common Language Infrastructure (CLI) 
+
+    3. **Type Safety:** .NET operates under the Common Language Infrastructure (CLI)
     model and employs managed code for executing applications. This approach inherently
     offers strong type safety checks which help in preventing many runtime errors that
     are common in languages like C/C++. It also enables features such as garbage collection,
@@ -133,11 +133,11 @@ The Semantic Kernel SDK provides many services and features to connect to AI mod
     AI Response:
      **Cross-platform Capabilities:** .NET allows building for various operating systems
     through platforms like .NET Core, promoting accessibility (Windows, Linux, macOS).
-    
+
     **Extensive Ecosystem:** Offers a vast library selection via NuGet and tools for web
-    (.NET Framework), mobile development (Maui/Xamarin.Forms), IoT, AI, providing rich
+    (.NET Framework), mobile development (.NET MAUI), IoT, AI, providing rich
     capabilities to developers.
-    
+
     **Type Safety & Reliability:** .NET's CLI model enforces strong typing and automatic
     garbage collection, mitigating runtime errors, thus enhancing application stability.
     ```

docs/architecture/blazor-for-web-forms-developers/introduction.md

@@ -27,7 +27,7 @@ When .NET and ASP.NET Web Forms first shipped, the platform ecosystem looked muc
 
 Most modern web frameworks are now also open-source, which has a number of benefits. Users aren't beheld to a single project owner to fix bugs and add features. Open-source projects provide improved transparency on development progress and upcoming changes. Open-source projects enjoy contributions from an entire community, and they foster a supportive open-source ecosystem. Despite the risks of open-source, many consumers and contributors have found suitable mitigations that enable them to enjoy the benefits of an open-source ecosystem in a safe and reasonable way. Examples of such mitigations include contributor license agreements, friendly licenses, pedigree scans, and supporting foundations.
 
-The .NET community has embraced both cross-platform support and open-source. .NET Core is an open-source and cross-platform implementation of .NET that runs on a plethora of platforms, including Windows, macOS, and various Linux distributions. Xamarin provides Mono, an open-source version of .NET. Mono runs on Android, iOS, and a variety of other form factors, including watches and smart TVs. In 2020, Microsoft released [.NET 5](https://devblogs.microsoft.com/dotnet/announcing-net-5-0/) that reconciled .NET Core and Mono into "a single .NET runtime and framework that can be used everywhere and that has uniform runtime behaviors and developer experiences."
+The .NET community has embraced both cross-platform support and open-source. .NET Core is an open-source and cross-platform implementation of .NET that runs on a plethora of platforms, including Windows, macOS, and various Linux distributions. Mono is an open-source version of .NET that runs on Android, iOS, and a variety of other form factors, including watches and smart TVs. In 2020, Microsoft released [.NET 5](https://devblogs.microsoft.com/dotnet/announcing-net-5-0/) that reconciled .NET Core and Mono into "a single .NET runtime and framework that can be used everywhere and that has uniform runtime behaviors and developer experiences."
 
 Will ASP.NET Web Forms benefit from the move to open-source and cross-platform support? The answer, unfortunately, is no, or at least not to the same extent as the rest of the platform. The .NET team [made it clear](https://devblogs.microsoft.com/dotnet/net-core-is-the-future-of-net/) that ASP.NET Web Forms won't be ported to .NET Core or .NET 8. Why is that?
 

docs/architecture/cloud-native/map-eshoponcontainers-azure-services.md

@@ -8,7 +8,7 @@ ms.date: 04/06/2022
 
 [!INCLUDE [download-alert](includes/download-alert.md)]
 
-Although not required, Azure is well-suited to supporting the eShopOnContainers because the project was built to be a cloud-native application. The application is built with .NET, so it can run on Linux or Windows containers depending on the Docker host. The application is made up of multiple autonomous microservices, each with its own data. The different microservices showcase different approaches, ranging from simple CRUD operations to more complex DDD and CQRS patterns. Microservices communicate with clients over HTTP and with one another via message-based communication. The application supports multiple platforms for clients as well, since it adopts HTTP as a standard communication protocol and includes ASP.NET Core and Xamarin mobile apps that run on Android, iOS, and Windows platforms.
+Although not required, Azure is well-suited to supporting the eShopOnContainers because the project was built to be a cloud-native application. The application is built with .NET, so it can run on Linux or Windows containers depending on the Docker host. The application is made up of multiple autonomous microservices, each with its own data. The different microservices showcase different approaches, ranging from simple CRUD operations to more complex DDD and CQRS patterns. Microservices communicate with clients over HTTP and with one another via message-based communication. The application supports multiple platforms for clients as well, since it adopts HTTP as a standard communication protocol and includes ASP.NET Core and Xamarin mobile apps that run on Android, iOS, and Windows platforms. (Xamarin is unsupported as of May 2024.)
 
 The application's architecture is shown in Figure 2-5. On the left are the client apps, broken up into mobile, traditional Web, and Web Single Page Application (SPA) flavors. On the right are the server-side components that make up the system, each of which can be hosted in Docker containers and Kubernetes clusters. The traditional web app is powered by the ASP.NET Core MVC application shown in yellow. This app and the mobile and web SPA applications communicate with the individual microservices through one or more API gateways. The API gateways follow the "backends for front ends" (BFF) pattern, meaning that each gateway is designed to support a given front-end client. The individual microservices are listed to the right of the API gateways and include both business logic and some kind of persistence store. The different services make use of SQL Server databases, Redis cache instances, and MongoDB/CosmosDB stores. On the far right is the system's Event Bus, which is used for communication between the microservices.
 

docs/architecture/maui/introduction.md

@@ -101,7 +101,7 @@ In addition, unit tests are provided for some of the classes in the eShop multi-
 
 ## Multi-Platform app solution
 
-The eShop multi-platform app solution organizes the source code and other resources into a multiple projects. All of the core mobile components are contained in a singular project named eShopContainers. This is a feature introduced with .NET 6 that allows a project to target multiple outputs which helps eliminate the need for multiple platform projects that we would have used in Xamarin.Forms and earlier .NET versions. An additional project is included for unit testing.
+The eShop multi-platform app solution organizes the source code and other resources into a multiple projects. All of the core mobile components are contained in a singular project named eShopContainers. This is a feature introduced with .NET 6 that allows a project to target multiple outputs which helps eliminate the need for multiple platform projects that we would have used in earlier .NET versions. An additional project is included for unit testing.
 
 While this project has all of its components stored in a singular project, it is worth considering separating it into multiple projects based on your needs. For example, if you have multiple implementations of service providers based off of a service with their own dependencies, it may make sense to break those service provider implementations out into their own separate project. Good candidates for project separation include shared models, service implementations, api client components, database or caching layers. Any place where you feel that the business could re-use a component in another project is a potential candidate for separation. These projects can then be packaged via [NuGet](/nuget/) for easy distribution and versioning.
 

docs/architecture/microservices/architect-microservice-container-applications/microservice-based-composite-ui-shape-layout.md

@@ -27,33 +27,33 @@ Figure 4-21 shows a version of this composite UI approach. This approach is simp
 
 Each of those UI composition microservices would be similar to a small API Gateway. But in this case, each one is responsible for a small UI area.
 
-A composite UI approach that's driven by microservices can be more challenging or less so, depending on what UI technologies you're using. For instance, you won't use the same techniques for building a traditional web application that you use for building an SPA or for native mobile app (as when developing Xamarin apps, which can be more challenging for this approach).
+A composite UI approach that's driven by microservices can be more challenging or less so, depending on what UI technologies you're using. For instance, you won't use the same techniques for building a traditional web application that you use for building an SPA or for native mobile app (which can be more challenging for this approach).
 
-The [eShopOnContainers](https://aka.ms/MicroservicesArchitecture) sample application uses the monolithic UI approach for multiple reasons. First, it's an introduction to microservices and containers. A composite UI is more advanced but also requires further complexity when designing and developing the UI. Second, eShopOnContainers also provides a native mobile app based on Xamarin, which would make it more complex on the client C\# side.
+The [eShopOnContainers](https://aka.ms/MicroservicesArchitecture) sample application uses the monolithic UI approach for multiple reasons. First, it's an introduction to microservices and containers. A composite UI is more advanced but also requires further complexity when designing and developing the UI. Second, eShopOnContainers also provides a native mobile app based on Xamarin (unsupported as of May 2024), which would make it more complex on the client C\# side.
 
 However, we encourage you to use the following references to learn more about composite UI based on microservices.
 
 ## Additional resources
 
-- **Micro Frontends (Martin Fowler's blog)**  
+- **Micro Frontends (Martin Fowler's blog)**
   <https://martinfowler.com/articles/micro-frontends.html>
-  
-- **Micro Frontends (Michael Geers site)**  
+
+- **Micro Frontends (Michael Geers site)**
   <https://micro-frontends.org/>
-  
-- **Composite UI using ASP.NET (Particular's Workshop)**  
+
+- **Composite UI using ASP.NET (Particular's Workshop)**
   <https://github.com/Particular/Workshop/tree/master/demos/asp-net-core>
 
-- **Ruben Oostinga. The Monolithic Frontend in the Microservices Architecture**  
+- **Ruben Oostinga. The Monolithic Frontend in the Microservices Architecture**
   <https://xebia.com/blog/the-monolithic-frontend-in-the-microservices-architecture/>
 
-- **Mauro Servienti. The secret of better UI composition**  
+- **Mauro Servienti. The secret of better UI composition**
   <https://particular.net/blog/secret-of-better-ui-composition>
 
-- **Viktor Farcic. Including Front-End Web Components Into Microservices**  
+- **Viktor Farcic. Including Front-End Web Components Into Microservices**
   <https://technologyconversations.com/2015/08/09/including-front-end-web-components-into-microservices/>
 
-- **Managing Frontend in the Microservices Architecture**  
+- **Managing Frontend in the Microservices Architecture**
   <https://allegro.tech/2016/03/Managing-Frontend-in-the-microservices-architecture.html>
 
 >[!div class="step-by-step"]

docs/architecture/microservices/microservice-ddd-cqrs-patterns/client-side-validation.md

@@ -17,7 +17,7 @@ Even when using client-side validation, you should always validate your commands
 
 Therefore, in client-side code you typically validate the ViewModels. You could also validate the client output DTOs or commands before you send them to the services.
 
-The implementation of client-side validation depends on what kind of client application you are building. It will be different if you are validating data in a web MVC web application with most of the code in .NET, a SPA web application with that validation being coded in JavaScript or TypeScript, or a mobile app coded with Xamarin and C#.
+The implementation of client-side validation depends on what kind of client application you are building. It will be different if you're validating data in an MVC web application with most of the code in .NET versus a SPA web application with the validation code in JavaScript or TypeScript.
 
 ## Additional resources
 

docs/azure/index.yml

@@ -122,20 +122,11 @@ conceptualContent:
     - title: Create mobile apps
       links:
         - itemType: learn
-          text: Consume REST services from Azure in Xamarin apps
-          url: /training/modules/consume-rest-services/
-        - itemType: quickstart
-          text: Create a Xamarin.Forms app with .NET SDK and Azure Cosmos DB's API for MongoDB
-          url: /azure/cosmos-db/create-mongodb-xamarin
-        - itemType: quickstart
-          text: Azure Blob storage client library with Xamarin.Forms
-          url: /azure/storage/blobs/storage-quickstart-blobs-xamarin
-        - itemType: tutorial
-          text: Send push notifications to Xamarin.Forms apps using ASP.NET Core and Azure Notification Hubs
-          url: /azure/notification-hubs/notification-hubs-backend-service-xamarin-forms
-        - itemType: concept
-          text: Add authentication and manage user identities in your mobile apps
-          url: /azure/developer/mobile-apps/authentication
+          text: Consume REST web services in .NET MAUI apps
+          url: /training/modules/consume-rest-services-maui/
+        - itemType: overview
+          text: Mobile architecture design
+          url: /azure/architecture/guide/mobile/mobile-start-here
     - title: Work with storage & data
       links:
         - itemType: concept

docs/core/diagnostics/dotnet-dsrouter.md

@@ -263,6 +263,5 @@ If there's no need to collect a trace during application startup, it's possible
 
 ## See also
 
-- [Android .NET Tracing](https://github.com/xamarin/xamarin-android/blob/d17-0/Documentation/guides/tracing.md)
 - [.NET MAUI Tracing](https://github.com/dotnet/maui/wiki/Profiling-.NET-MAUI-Apps)
 - [.NET Diagnostics Tracing on mobile](https://github.com/dotnet/runtime/blob/main/docs/design/mono/diagnostics-tracing.md)

docs/core/testing/index.md

@@ -39,7 +39,7 @@ Keep in mind there are [best practices](unit-testing-best-practices.md) for writ
 
 ### xUnit
 
-[xUnit](https://xunit.net) is a free, open-source, community-focused unit testing tool for .NET. The original inventor of NUnit v2 wrote xUnit.net. xUnit.net is the latest technology for unit testing .NET apps. It also works with ReSharper, CodeRush, TestDriven.NET, and [Xamarin](https://dotnet.microsoft.com/apps/xamarin). xUnit.net is a project of the [.NET Foundation](https://dotnetfoundation.org) and operates under its code of conduct.
+[xUnit](https://xunit.net) is a free, open-source, community-focused unit testing tool for .NET. The original inventor of NUnit v2 wrote xUnit.net. xUnit.net is the latest technology for unit testing .NET apps. It also works with ReSharper, CodeRush, and TestDriven.NET. xUnit.net is a project of the [.NET Foundation](https://dotnetfoundation.org) and operates under its code of conduct.
 
 For more information, see the following resources: