From bdac7738d739141c7c1ff04e9e64eeadf24d46bf Mon Sep 17 00:00:00 2001 From: Dominik Titl <78549750+morning4coffe-dev@users.noreply.github.com> Date: Thu, 25 Jul 2024 13:07:59 +0200 Subject: [PATCH 01/18] chore: Adjust contributing docs --- doc/articles/uno-development/contributing-intro.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/doc/articles/uno-development/contributing-intro.md b/doc/articles/uno-development/contributing-intro.md index 261f4dae3712..f5964b53786d 100644 --- a/doc/articles/uno-development/contributing-intro.md +++ b/doc/articles/uno-development/contributing-intro.md @@ -22,7 +22,7 @@ For the prerequisites you'll need, as well as useful tips like using [solution f If you're doing development for Uno's macOS support, you'll need to build and run Uno using Visual Studio for Mac. [There's a separate guide for that here](building-uno-macos.md). -You can contribute to Uno directly from your browser using GitPod. [Find out how.](../features/working-with-gitpod.md) +You can contribute to Uno directly from your browser using GitPod, [find out how](../features/working-with-gitpod.md). Whether you're fixing a bug or working on a new feature, [inspecting the visual tree of a running app](debugging-inspect-visual-tree.md) is often a key step. @@ -32,7 +32,7 @@ See [Uno's code conventions and common patterns here](../contributing/guidelines ## Implementing a new feature -See how to implement a new [feature here](../contributing/guidelines/implementing-a-new%20winui-winrt-feature.md). +See how to implement a new [feature here](xref:Uno.Contributing.ImplementWinUIWinRTAPI). ## Experimenting with Samples App @@ -52,7 +52,10 @@ See the [Guidelines for creating tests](../contributing/guidelines/creating-test ## Creating a Pull Request -Uno uses [Git](https://git-scm.com/) for version control, and GitHub to host the [main repository](https://github.com/unoplatform/uno). You'll need to know the basics of Git to submit changes to Uno, but never fear, there are plenty of [great](https://git-scm.com/book/en/v2) [guides](https://guides.github.com/introduction/git-handbook/) [available](https://www.atlassian.com/git/tutorials). +Uno uses [Git](https://git-scm.com/) for version control, and GitHub to host the [main repository](https://github.com/unoplatform/uno). You'll need to know the basics of Git to submit changes to Uno, but never fear, there are plenty of great guides available: +[Pro Git book | git-scm](https://git-scm.com/book/en/v2) +[About Git | GitHub](https://guides.github.com/introduction/git-handbook/) +[Tutorials | Atlassian](https://www.atlassian.com/git/tutorials) > [!IMPORTANT] > Before you commit your code, take a minute to familiarize yourself with the [Conventional Commits format](git-conventional-commits.md) Uno uses. From 5ce430cd5e78706d007d6301465098f5b163db5f Mon Sep 17 00:00:00 2001 From: Dominik Titl <78549750+morning4coffe-dev@users.noreply.github.com> Date: Thu, 25 Jul 2024 13:12:44 +0200 Subject: [PATCH 02/18] chore: Fix UserInputs manipulation link --- .../features/pointers-keyboard-and-other-user-inputs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/articles/features/pointers-keyboard-and-other-user-inputs.md b/doc/articles/features/pointers-keyboard-and-other-user-inputs.md index d9105b45f36b..91f60f2c6ed3 100644 --- a/doc/articles/features/pointers-keyboard-and-other-user-inputs.md +++ b/doc/articles/features/pointers-keyboard-and-other-user-inputs.md @@ -28,7 +28,7 @@ User inputs are usually propagated using `RoutedEvents`. See Uno's [routed event | **_manipulation events_** | `ManipulationStarting` | Yes | Yes | Yes | Yes | [Documentation](https://learn.microsoft.com/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.uielement.manipulationstarting) | | `ManipulationStarted` | Yes | Yes | Yes | Yes | [Documentation](https://learn.microsoft.com/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.uielement.manipulationstarted) | -| `ManipulationDelta` | Yes | Yes | Yes | Yes | [Documentation](https://learn.microsoft.com/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.uielement.manipulationedelta) | +| `ManipulationDelta` | Yes | Yes | Yes | Yes | [Documentation](https://learn.microsoft.com/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.uielement.manipulationdelta) | | `ManipulationInertiaStarting` | Yes | Yes | Yes | Yes | [Documentation](https://learn.microsoft.com/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.uielement.manipulationinertiastarting) | | `ManipulationCompleted` | Yes | Yes | Yes | Yes | [Documentation](https://learn.microsoft.com/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.uielement.manipulationcompleted) | | **_gesture events_** From 8a062bb4696612715d6a3d0dfc88b46a9d13e847 Mon Sep 17 00:00:00 2001 From: Dominik Titl <78549750+morning4coffe-dev@users.noreply.github.com> Date: Thu, 25 Jul 2024 13:14:13 +0200 Subject: [PATCH 03/18] chore: Fix aria-label link --- doc/articles/features/working-with-accessibility.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/articles/features/working-with-accessibility.md b/doc/articles/features/working-with-accessibility.md index 165421919b51..ef02beba7344 100644 --- a/doc/articles/features/working-with-accessibility.md +++ b/doc/articles/features/working-with-accessibility.md @@ -65,7 +65,7 @@ Setting this property does the following: - On **Android**, it sets the [`View.ContentDescription`](https://developer.android.com/reference/android/view/View.html#setContentDescription(java.lang.CharSequence)) property - On **iOS**, it sets the [`UIView.AccessibilityIdentifier`](https://developer.apple.com/documentation/uikit/uiaccessibilityidentification/1623132-accessibilityidentifier) property - On **macOS**, it sets the [`NSView.AccessibilityIdentifier`](https://developer.apple.com/documentation/appkit/nsaccessibility/1535023-accessibilityidentifier) property -- On **WebAssembly**, it sets [`aria-label`](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-label_attribute) and the `xamlautomationid` property on the HTML element. The [`role`](https://www.w3.org/WAI/PF/HTML/wiki/RoleAttribute) HTML Attribute is also set based on the XAML view type whose `AutomationProperties.AutomationId` was set. +- On **WebAssembly**, it sets [`aria-label`](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-label) and the `xamlautomationid` property on the HTML element. The [`role`](https://www.w3.org/WAI/PF/HTML/wiki/RoleAttribute) HTML Attribute is also set based on the XAML view type whose `AutomationProperties.AutomationId` was set. This property is generally used alongside [Uno.UITest](https://github.com/unoplatform/Uno.UITest) to create UI Tests, and is particularly useful to select items using data-bound identifiers. From 5adcaa1336f752b0248c0acb70658106630fb7f4 Mon Sep 17 00:00:00 2001 From: Dominik Titl <78549750+morning4coffe-dev@users.noreply.github.com> Date: Thu, 25 Jul 2024 13:28:43 +0200 Subject: [PATCH 04/18] chore: Fix migrating to WinUI link --- doc/articles/migrating-from-xamarin-to-net6.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/articles/migrating-from-xamarin-to-net6.md b/doc/articles/migrating-from-xamarin-to-net6.md index dae1f99e5982..9428b59fb2cd 100644 --- a/doc/articles/migrating-from-xamarin-to-net6.md +++ b/doc/articles/migrating-from-xamarin-to-net6.md @@ -16,7 +16,7 @@ There are two ways to migrate an application to .NET 7. 1. In a separate folder, create a new application from the templates using [`dotnet new unoapp -o MyApp`](get-started-dotnet-new.md) (MyApp being of the same name as your existing app), or by using the Visual Studio `Uno Platform App` template 2. Move the `MyApp.Mobile` project folder and include it in your existing solution - 3. Make the adjustments to move from the [UWP APIs to the WinUI APIs](updating-to-winui3.ms) + 3. Make the adjustments to move from the [UWP APIs to the WinUI APIs](updating-to-winui3.md) 4. Optionally [convert your legacy Xamarin heads](updating-to-winui3.md) to use Uno.WinUI instead of Uno.UI ## Additional considerations From 38460764ee9b3de16b72b222e802765a25cc99b0 Mon Sep 17 00:00:00 2001 From: Dominik Titl <78549750+morning4coffe-dev@users.noreply.github.com> Date: Thu, 25 Jul 2024 13:29:08 +0200 Subject: [PATCH 05/18] chore: Fix Using Wizard docs --- doc/articles/getting-started/wizard/includes/extensions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/articles/getting-started/wizard/includes/extensions.md b/doc/articles/getting-started/wizard/includes/extensions.md index 61698dca5601..2c4bd1f8c3d9 100644 --- a/doc/articles/getting-started/wizard/includes/extensions.md +++ b/doc/articles/getting-started/wizard/includes/extensions.md @@ -47,9 +47,9 @@ dotnet new unoapp -http The Localization extension is responsible for managing globalization in your app. This enables keeping all translations of your app in a single place and enables the user to easily switch the UI language. -The generated app contains *resw* files which can be used to define the application strings. The defined languages are configured in *appsettings.json*. Follow [this link](Learn.Tutorials.Localization.HowToUseLocalization#3-update-the-ui-culture-with-localizationsettings) to learn how to switch the UI culture. +The generated app contains *resw* files which can be used to define the application strings. The defined languages are configured in *appsettings.json*. Follow [this link](xref:Learn.Tutorials.Localization.HowToUseLocalization#3-update-the-ui-culture-with-localizationsettings) to learn how to switch the UI culture. -![Visual Studio Solution Explorer showing localization files](assets/localization.jpg) +![Visual Studio Solution Explorer showing localization files](doc/articles/getting-started/wizard/assets/localization.jpg) The default settings come with the following pre-set languages: English (*en*), Spanish (*es*), French (*fr*), and Portuguese - Brazil (*pt-BR*). From cf4aa68ba70a8aa9aa2ca0bed959205474e1345c Mon Sep 17 00:00:00 2001 From: Dominik Titl <78549750+morning4coffe-dev@users.noreply.github.com> Date: Thu, 25 Jul 2024 14:12:49 +0200 Subject: [PATCH 06/18] chore: Misc link fixes --- doc/articles/concepts/overview/why-uno-platform.md | 2 +- doc/articles/uno-development/building-uno-ui.md | 2 +- doc/blog/201809-uno-wasm-intro-part-01.md | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/articles/concepts/overview/why-uno-platform.md b/doc/articles/concepts/overview/why-uno-platform.md index 0985ec6b884c..32c0a4923957 100644 --- a/doc/articles/concepts/overview/why-uno-platform.md +++ b/doc/articles/concepts/overview/why-uno-platform.md @@ -162,7 +162,7 @@ The Uno Platform provides access to SkiaSharp as a render canvas for your app, e ## Animations: Beyond storyboards, access to Lottie and Rive -Based on SkiaSharp support, Uno Platform provides AnimatedVisualPlayer to give the ability to render rich Lottie files directly in your app, for all target platforms. +Based on SkiaSharp support, Uno Platform provides AnimatedVisualPlayer to give the ability to render rich [Lottie files](https://airbnb.io/lottie/#/) directly in your app, for all target platforms. ## Performance and app size with AOT/Jiterpreter diff --git a/doc/articles/uno-development/building-uno-ui.md b/doc/articles/uno-development/building-uno-ui.md index 5e482eeb5f90..15a86a7da2f2 100644 --- a/doc/articles/uno-development/building-uno-ui.md +++ b/doc/articles/uno-development/building-uno-ui.md @@ -15,7 +15,7 @@ This article explains how to build Uno.UI locally, for instance, if you wish to - To build the UWP flavor of Uno, you'll need **UWP Development**, install all recent UWP SDKs, starting from 10.0.19041 (or above or equal to `TargetPlatformVersion` line [in this file](https://github.com/unoplatform/uno/blob/master/src/Uno.CrossTargetting.targets)) - Install (**Tools** / **Android** / **Android SDK manager**) all Android SDKs starting from 7.1 (or the Android versions `TargetFrameworks` [list used here](https://github.com/unoplatform/uno/blob/master/src/Uno.UI.BindingHelper.Android/Uno.UI.BindingHelper.Android.csproj)) - Run [Uno.Check](https://github.com/unoplatform/uno.check) on your dev machine to setup .NET Android/iOS workloads -- Install the version of the .NET SDK specified in [global.json](../../../global.json). +- Install the version of the .NET SDK specified in [global.json](https://github.com/unoplatform/uno/blob/master/global.json). ## Recommended Windows hardware diff --git a/doc/blog/201809-uno-wasm-intro-part-01.md b/doc/blog/201809-uno-wasm-intro-part-01.md index 68ac4460fbb4..30dabcc4a92b 100644 --- a/doc/blog/201809-uno-wasm-intro-part-01.md +++ b/doc/blog/201809-uno-wasm-intro-part-01.md @@ -38,9 +38,9 @@ Consuming a WebAssembly module is generally composed of a `.wasm` file and a JS WebAssembly is mainly trying to solve the issues that makes it difficult to optimize performance for large applications, provide access to binary-producing languages and improve the security of running the resulting code. -WebAssembly modules are defined as self-contained units of byte code. It's possible to use [streaming compilation](https://webassembly.github.io/spec/web-api/index.html#streaming-modules) to concurrently process the byte code as it is being downloaded, unlike Javascript where the source file needs to be fully parsed to make sense. +WebAssembly modules are defined as self-contained units of byte code. It's possible to use [streaming compilation](https://webassembly.github.io/spec/web-api/index.html#streaming-modules) to concurrently process the byte code as it is being downloaded, unlike JavaScript where the source file needs to be fully parsed to make sense. -It also provides a way for any language to have a compilation back-end (such as LLVM and [Emscripten](http://emscripten.org/)) to target the Web. That opens a path for C, C++, Rust, [.NET based languages via Mono](https://github.com/mono/mono/tree/master/sdks/wasm), Java, Go, and many other languages to finally reach the web. It provides choices for developers targeting the Web, whether they need full type safety or not, to reuse that complex C++ library that is proving very difficult to port to Javascript. Such portability also enables runtimes and frameworks to follow, such as [QT-Wasm](https://wiki.qt.io/Qt_for_WebAssembly), and Mono and a very large part of the .NET ecosystem. +It also provides a way for any language to have a compilation back-end (such as LLVM and [Emscripten](http://emscripten.org/)) to target the Web. That opens a path for C, C++, Rust, [.NET based languages via Mono](https://github.com/dotnet/runtime/tree/main/src/mono/wasm), Java, Go, and many other languages to finally reach the web. It provides choices for developers targeting the Web, whether they need full type safety or not, to reuse that complex C++ library that is proving very difficult to port to Javascript. Such portability also enables runtimes and frameworks to follow, such as [QT-Wasm](https://wiki.qt.io/Qt_for_WebAssembly), and Mono and a very large part of the .NET ecosystem. Security-wise, WebAssembly is very different from previous attempts to run arbitrary binary code in the browser, such as Flash, Java applets, VBA, Silverlight, ActiveX, ... which all had (and continue to have) security and portability issues. For instance, security features include the inability to execute arbitrary memory locations. While this makes optionally JIT'ed languages (such as .NET based languages) a difficult target, it promises a [higher security](https://i.blackhat.com/us-18/Thu-August-9/us-18-Lukasiewicz-WebAssembly-A-New-World-of-Native_Exploits-On-The-Web-wp.pdf) execution environment than its similar add-in based predecessors. From 556de3c1853f7a421abf99a058b8149f1c5a9f91 Mon Sep 17 00:00:00 2001 From: Dominik Titl <78549750+morning4coffe-dev@users.noreply.github.com> Date: Thu, 8 Aug 2024 08:54:48 +0200 Subject: [PATCH 07/18] chore: Update extensions.md from Youssefs review Co-authored-by: Youssef Victor --- doc/articles/getting-started/wizard/includes/extensions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/articles/getting-started/wizard/includes/extensions.md b/doc/articles/getting-started/wizard/includes/extensions.md index 2c4bd1f8c3d9..9ad1ebc62f35 100644 --- a/doc/articles/getting-started/wizard/includes/extensions.md +++ b/doc/articles/getting-started/wizard/includes/extensions.md @@ -49,7 +49,7 @@ This enables keeping all translations of your app in a single place and enables The generated app contains *resw* files which can be used to define the application strings. The defined languages are configured in *appsettings.json*. Follow [this link](xref:Learn.Tutorials.Localization.HowToUseLocalization#3-update-the-ui-culture-with-localizationsettings) to learn how to switch the UI culture. -![Visual Studio Solution Explorer showing localization files](doc/articles/getting-started/wizard/assets/localization.jpg) +![Visual Studio Solution Explorer showing localization files](../assets/localization.jpg) The default settings come with the following pre-set languages: English (*en*), Spanish (*es*), French (*fr*), and Portuguese - Brazil (*pt-BR*). From 725c943d511ede3559920a18b02b12b1282cf520 Mon Sep 17 00:00:00 2001 From: Dominik Titl <78549750+morning4coffe-dev@users.noreply.github.com> Date: Thu, 8 Aug 2024 09:48:02 +0200 Subject: [PATCH 08/18] docs: Update TargetFrameworks link --- doc/articles/uno-development/building-uno-ui.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/articles/uno-development/building-uno-ui.md b/doc/articles/uno-development/building-uno-ui.md index 15a86a7da2f2..5fc95dee1920 100644 --- a/doc/articles/uno-development/building-uno-ui.md +++ b/doc/articles/uno-development/building-uno-ui.md @@ -13,7 +13,7 @@ This article explains how to build Uno.UI locally, for instance, if you wish to - Select the **.NET Multi-Platform App UI development`** workload - Select the **.NET desktop development** workload - To build the UWP flavor of Uno, you'll need **UWP Development**, install all recent UWP SDKs, starting from 10.0.19041 (or above or equal to `TargetPlatformVersion` line [in this file](https://github.com/unoplatform/uno/blob/master/src/Uno.CrossTargetting.targets)) -- Install (**Tools** / **Android** / **Android SDK manager**) all Android SDKs starting from 7.1 (or the Android versions `TargetFrameworks` [list used here](https://github.com/unoplatform/uno/blob/master/src/Uno.UI.BindingHelper.Android/Uno.UI.BindingHelper.Android.csproj)) +- Install (**Tools** / **Android** / **Android SDK manager**) all Android SDKs starting from 7.1 (or the Android versions `TargetFrameworks` [list used here](https://github.com/unoplatform/uno/blob/master/src/Uno.UI.BindingHelper.Android/Uno.UI.BindingHelper.Android.netcoremobile.csproj)) - Run [Uno.Check](https://github.com/unoplatform/uno.check) on your dev machine to setup .NET Android/iOS workloads - Install the version of the .NET SDK specified in [global.json](https://github.com/unoplatform/uno/blob/master/global.json). From c44d7d1da685b388aa9df45f4b873b591b3dbb64 Mon Sep 17 00:00:00 2001 From: Dominik Titl <78549750+morning4coffe-dev@users.noreply.github.com> Date: Thu, 8 Aug 2024 09:48:21 +0200 Subject: [PATCH 09/18] docs: Update IL Linker link --- doc/articles/common-issues-all-ides.md | 2 +- doc/articles/contributing/guidelines/issue-triage.md | 4 ++-- doc/articles/contributing/guidelines/updating-dependencies.md | 2 +- .../guides/silverlight-migration/09-client-auth-service.md | 2 +- .../guides/silverlight-migration/98-timeentry-samples.md | 2 +- doc/articles/uno-community-toolkit-v7.md | 2 +- 6 files changed, 7 insertions(+), 7 deletions(-) diff --git a/doc/articles/common-issues-all-ides.md b/doc/articles/common-issues-all-ides.md index 57b23f35e9f5..331244040fa3 100644 --- a/doc/articles/common-issues-all-ides.md +++ b/doc/articles/common-issues-all-ides.md @@ -21,7 +21,7 @@ Try building your project again. ## Runtime error `No parameterless constructor defined for XXXX` -This error is generally caused by some missing [IL Linker](https://github.com/mono/linker/tree/master/docs) configuration on WebAssembly. You may need to add some of your application assemblies in the LinkerConfig.xml file of your project. You can find [additional information in the documentation](features/using-il-linker-webassembly.md). +This error is generally caused by some missing [IL Linker](https://github.com/dotnet/runtime/tree/main/src/tools/illink) configuration on WebAssembly. You may need to add some of your application assemblies in the LinkerConfig.xml file of your project. You can find [additional information in the documentation](features/using-il-linker-webassembly.md). Similar error messages using various libraries: diff --git a/doc/articles/contributing/guidelines/issue-triage.md b/doc/articles/contributing/guidelines/issue-triage.md index bed249c754f8..540ad33f37e4 100644 --- a/doc/articles/contributing/guidelines/issue-triage.md +++ b/doc/articles/contributing/guidelines/issue-triage.md @@ -35,10 +35,10 @@ Is something unclear? Do we need to improve our documentation or samples? Community support requests should be directed to: -* Our [documentation](https://platform.uno/docs/) and [troubleshooting guide](https://platform.uno/docs/troubleshooting-guide). +* Our [documentation](https://platform.uno/docs/) and [troubleshooting guide](xref:Uno.UI.CommonIssues). * [GitHub Discussions](https://github.com/unoplatform/uno/discussions) * The [Discord Server](https://platform.uno/discord) -* On [Twitter using the #unoplatform](https://twitter.com/search?q=%23unoplatform) hashtag. +* On [X/Twitter using the #unoplatform](https://twitter.com/search?q=%23unoplatform) hashtag. Organizations that want a deeper level of support beyond community support should be directed to [contact Uno Platform](https://platform.uno/contact/) to discuss obtaining professional support. diff --git a/doc/articles/contributing/guidelines/updating-dependencies.md b/doc/articles/contributing/guidelines/updating-dependencies.md index 7dd5a239cd36..1290851add38 100644 --- a/doc/articles/contributing/guidelines/updating-dependencies.md +++ b/doc/articles/contributing/guidelines/updating-dependencies.md @@ -8,7 +8,7 @@ We use Dependabot to notify the team of any updates to dependencies. Once a week ## Internal dependencies -The following dependencies don't change the public API surface and are typically safe to merge and we could potentially [configure mergify to automatically merge them if CI passes](https://medium.com/mergify/merging-bots-pull-requests-automatically-548ed0b4a424): +The following dependencies don't change the public API surface and are typically safe to merge and we could potentially [configure mergify to automatically merge them if CI passes](https://docs.mergify.com/workflow/automerge/): - BenchmarkDotNet - [FluentAssertions](https://github.com/unoplatform/uno/pull/1196) diff --git a/doc/articles/guides/silverlight-migration/09-client-auth-service.md b/doc/articles/guides/silverlight-migration/09-client-auth-service.md index b4c1e524665f..81a31d3d2e88 100644 --- a/doc/articles/guides/silverlight-migration/09-client-auth-service.md +++ b/doc/articles/guides/silverlight-migration/09-client-auth-service.md @@ -25,7 +25,7 @@ As discussed earlier, the UWP implementation of the **TimeEntryUno** application > [!TIP] > The IdentityServer4 server-side implementation used in the sample mirrors the QuickStart tutorial shown below. : > -> * [Protecting an API using Client Credentials](http://docs.identityserver.io/en/latest/quickstarts/1_client_credentials.html) +> * [Protecting an API using Client Credentials](https://docs.duendesoftware.com/identityserver/v7/quickstarts/1_client_credentials/) The code to retrieve the access token is encapsulated within the a class **IdentityServerClient** and uses the **HttpClient** class as well as the **IdentityModel** NuGet package. diff --git a/doc/articles/guides/silverlight-migration/98-timeentry-samples.md b/doc/articles/guides/silverlight-migration/98-timeentry-samples.md index 1043014f1ac7..031ee019c237 100644 --- a/doc/articles/guides/silverlight-migration/98-timeentry-samples.md +++ b/doc/articles/guides/silverlight-migration/98-timeentry-samples.md @@ -10,7 +10,7 @@ The sample application is made up of 3 solutions containing multiple projects an * Uno.Samples * reference - * [TimeEntryRia](https://github.com/unoplatform/Uno.Samples/tree/master/reference/TimeEntryRia) + * [TimeEntryRia](https://github.com/unoplatform/Uno.Samples/tree/master/ArchivedProjects/UI/TimeEntryRia/TimeEntryRia) * UI * TimeEntry * [TimeEntryServices](https://github.com/unoplatform/Uno.Samples/tree/master/UI/TimeEntry/TimeEntryServices) diff --git a/doc/articles/uno-community-toolkit-v7.md b/doc/articles/uno-community-toolkit-v7.md index 268053e5874b..1b1f7cee10a0 100644 --- a/doc/articles/uno-community-toolkit-v7.md +++ b/doc/articles/uno-community-toolkit-v7.md @@ -53,7 +53,7 @@ These package ids are for Uno Platform (non-Windows) projects. For WinUI 3 proje - [Uno.Microsoft.Toolkit.UWP](https://www.nuget.org/packages/Uno.Microsoft.Toolkit.UWP) - [Uno.Microsoft.Toolkit.Uwp.Notifications](https://www.nuget.org/packages/Uno.Microsoft.Toolkit.Uwp.Notifications) - [Uno.Microsoft.Toolkit.Uwp.Services](https://www.nuget.org/packages/Uno.Microsoft.Toolkit.Uwp.Services) -- [Uno.Microsoft.Toolkit.Uwp.UI.Controls.DataGrid](https://www.nuget.org/packages/Uno.Microsoft.Toolkit.UWP.UI.DataGrid) +- [Uno.Microsoft.Toolkit.Uwp.UI.Controls.DataGrid](https://www.nuget.org/packages/Uno.Microsoft.Toolkit.Uwp.UI.Controls.DataGrid) - [Uno.Microsoft.Toolkit.Uwp.UI](https://www.nuget.org/packages/Uno.Microsoft.Toolkit.UWP.UI) - [Uno.Microsoft.Toolkit.Uwp.UI.Animations](https://www.nuget.org/packages/Uno.Microsoft.Toolkit.Uwp.UI.Animations) - [Uno.Microsoft.Toolkit.Uwp.UI.Controls](https://www.nuget.org/packages/Uno.Microsoft.Toolkit.Uwp.UI.Controls) From eeeb505b06ec8fa3f44d27b78a3024201ceba2b1 Mon Sep 17 00:00:00 2001 From: Dominik Titl <78549750+morning4coffe-dev@users.noreply.github.com> Date: Thu, 8 Aug 2024 09:48:21 +0200 Subject: [PATCH 10/18] docs: Misc link fixes --- doc/articles/common-issues-all-ides.md | 2 +- doc/articles/contributing/guidelines/issue-triage.md | 4 ++-- doc/articles/contributing/guidelines/updating-dependencies.md | 2 +- .../guides/silverlight-migration/09-client-auth-service.md | 2 +- .../guides/silverlight-migration/98-timeentry-samples.md | 2 +- doc/articles/uno-community-toolkit-v7.md | 2 +- 6 files changed, 7 insertions(+), 7 deletions(-) diff --git a/doc/articles/common-issues-all-ides.md b/doc/articles/common-issues-all-ides.md index 57b23f35e9f5..331244040fa3 100644 --- a/doc/articles/common-issues-all-ides.md +++ b/doc/articles/common-issues-all-ides.md @@ -21,7 +21,7 @@ Try building your project again. ## Runtime error `No parameterless constructor defined for XXXX` -This error is generally caused by some missing [IL Linker](https://github.com/mono/linker/tree/master/docs) configuration on WebAssembly. You may need to add some of your application assemblies in the LinkerConfig.xml file of your project. You can find [additional information in the documentation](features/using-il-linker-webassembly.md). +This error is generally caused by some missing [IL Linker](https://github.com/dotnet/runtime/tree/main/src/tools/illink) configuration on WebAssembly. You may need to add some of your application assemblies in the LinkerConfig.xml file of your project. You can find [additional information in the documentation](features/using-il-linker-webassembly.md). Similar error messages using various libraries: diff --git a/doc/articles/contributing/guidelines/issue-triage.md b/doc/articles/contributing/guidelines/issue-triage.md index bed249c754f8..540ad33f37e4 100644 --- a/doc/articles/contributing/guidelines/issue-triage.md +++ b/doc/articles/contributing/guidelines/issue-triage.md @@ -35,10 +35,10 @@ Is something unclear? Do we need to improve our documentation or samples? Community support requests should be directed to: -* Our [documentation](https://platform.uno/docs/) and [troubleshooting guide](https://platform.uno/docs/troubleshooting-guide). +* Our [documentation](https://platform.uno/docs/) and [troubleshooting guide](xref:Uno.UI.CommonIssues). * [GitHub Discussions](https://github.com/unoplatform/uno/discussions) * The [Discord Server](https://platform.uno/discord) -* On [Twitter using the #unoplatform](https://twitter.com/search?q=%23unoplatform) hashtag. +* On [X/Twitter using the #unoplatform](https://twitter.com/search?q=%23unoplatform) hashtag. Organizations that want a deeper level of support beyond community support should be directed to [contact Uno Platform](https://platform.uno/contact/) to discuss obtaining professional support. diff --git a/doc/articles/contributing/guidelines/updating-dependencies.md b/doc/articles/contributing/guidelines/updating-dependencies.md index 7dd5a239cd36..1290851add38 100644 --- a/doc/articles/contributing/guidelines/updating-dependencies.md +++ b/doc/articles/contributing/guidelines/updating-dependencies.md @@ -8,7 +8,7 @@ We use Dependabot to notify the team of any updates to dependencies. Once a week ## Internal dependencies -The following dependencies don't change the public API surface and are typically safe to merge and we could potentially [configure mergify to automatically merge them if CI passes](https://medium.com/mergify/merging-bots-pull-requests-automatically-548ed0b4a424): +The following dependencies don't change the public API surface and are typically safe to merge and we could potentially [configure mergify to automatically merge them if CI passes](https://docs.mergify.com/workflow/automerge/): - BenchmarkDotNet - [FluentAssertions](https://github.com/unoplatform/uno/pull/1196) diff --git a/doc/articles/guides/silverlight-migration/09-client-auth-service.md b/doc/articles/guides/silverlight-migration/09-client-auth-service.md index b4c1e524665f..81a31d3d2e88 100644 --- a/doc/articles/guides/silverlight-migration/09-client-auth-service.md +++ b/doc/articles/guides/silverlight-migration/09-client-auth-service.md @@ -25,7 +25,7 @@ As discussed earlier, the UWP implementation of the **TimeEntryUno** application > [!TIP] > The IdentityServer4 server-side implementation used in the sample mirrors the QuickStart tutorial shown below. : > -> * [Protecting an API using Client Credentials](http://docs.identityserver.io/en/latest/quickstarts/1_client_credentials.html) +> * [Protecting an API using Client Credentials](https://docs.duendesoftware.com/identityserver/v7/quickstarts/1_client_credentials/) The code to retrieve the access token is encapsulated within the a class **IdentityServerClient** and uses the **HttpClient** class as well as the **IdentityModel** NuGet package. diff --git a/doc/articles/guides/silverlight-migration/98-timeentry-samples.md b/doc/articles/guides/silverlight-migration/98-timeentry-samples.md index 1043014f1ac7..031ee019c237 100644 --- a/doc/articles/guides/silverlight-migration/98-timeentry-samples.md +++ b/doc/articles/guides/silverlight-migration/98-timeentry-samples.md @@ -10,7 +10,7 @@ The sample application is made up of 3 solutions containing multiple projects an * Uno.Samples * reference - * [TimeEntryRia](https://github.com/unoplatform/Uno.Samples/tree/master/reference/TimeEntryRia) + * [TimeEntryRia](https://github.com/unoplatform/Uno.Samples/tree/master/ArchivedProjects/UI/TimeEntryRia/TimeEntryRia) * UI * TimeEntry * [TimeEntryServices](https://github.com/unoplatform/Uno.Samples/tree/master/UI/TimeEntry/TimeEntryServices) diff --git a/doc/articles/uno-community-toolkit-v7.md b/doc/articles/uno-community-toolkit-v7.md index 268053e5874b..1b1f7cee10a0 100644 --- a/doc/articles/uno-community-toolkit-v7.md +++ b/doc/articles/uno-community-toolkit-v7.md @@ -53,7 +53,7 @@ These package ids are for Uno Platform (non-Windows) projects. For WinUI 3 proje - [Uno.Microsoft.Toolkit.UWP](https://www.nuget.org/packages/Uno.Microsoft.Toolkit.UWP) - [Uno.Microsoft.Toolkit.Uwp.Notifications](https://www.nuget.org/packages/Uno.Microsoft.Toolkit.Uwp.Notifications) - [Uno.Microsoft.Toolkit.Uwp.Services](https://www.nuget.org/packages/Uno.Microsoft.Toolkit.Uwp.Services) -- [Uno.Microsoft.Toolkit.Uwp.UI.Controls.DataGrid](https://www.nuget.org/packages/Uno.Microsoft.Toolkit.UWP.UI.DataGrid) +- [Uno.Microsoft.Toolkit.Uwp.UI.Controls.DataGrid](https://www.nuget.org/packages/Uno.Microsoft.Toolkit.Uwp.UI.Controls.DataGrid) - [Uno.Microsoft.Toolkit.Uwp.UI](https://www.nuget.org/packages/Uno.Microsoft.Toolkit.UWP.UI) - [Uno.Microsoft.Toolkit.Uwp.UI.Animations](https://www.nuget.org/packages/Uno.Microsoft.Toolkit.Uwp.UI.Animations) - [Uno.Microsoft.Toolkit.Uwp.UI.Controls](https://www.nuget.org/packages/Uno.Microsoft.Toolkit.Uwp.UI.Controls) From bf208feca5f6f74031c83f846534fb1a51e4635a Mon Sep 17 00:00:00 2001 From: Dominik Titl <78549750+morning4coffe-dev@users.noreply.github.com> Date: Thu, 8 Aug 2024 10:16:55 +0200 Subject: [PATCH 11/18] chore: Update updating-to-winui3 link with xref --- doc/articles/migrating-from-xamarin-to-net6.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/articles/migrating-from-xamarin-to-net6.md b/doc/articles/migrating-from-xamarin-to-net6.md index 9428b59fb2cd..abb266541db4 100644 --- a/doc/articles/migrating-from-xamarin-to-net6.md +++ b/doc/articles/migrating-from-xamarin-to-net6.md @@ -16,8 +16,8 @@ There are two ways to migrate an application to .NET 7. 1. In a separate folder, create a new application from the templates using [`dotnet new unoapp -o MyApp`](get-started-dotnet-new.md) (MyApp being of the same name as your existing app), or by using the Visual Studio `Uno Platform App` template 2. Move the `MyApp.Mobile` project folder and include it in your existing solution - 3. Make the adjustments to move from the [UWP APIs to the WinUI APIs](updating-to-winui3.md) - 4. Optionally [convert your legacy Xamarin heads](updating-to-winui3.md) to use Uno.WinUI instead of Uno.UI + 3. Make the adjustments to move from the [UWP APIs to the WinUI APIs](xref:updating-to-winui3.md) + 4. Optionally [convert your legacy Xamarin heads](xref:updating-to-winui3.md) to use Uno.WinUI instead of Uno.UI ## Additional considerations From 0f82865332346f3f824ea67c113b0fc131aef16a Mon Sep 17 00:00:00 2001 From: Dominik Titl <78549750+morning4coffe-dev@users.noreply.github.com> Date: Thu, 8 Aug 2024 12:08:23 +0200 Subject: [PATCH 12/18] chore: Update X links --- doc/articles/contributing/guidelines/issue-triage.md | 2 +- doc/articles/uno-development/ways-to-contribute.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/articles/contributing/guidelines/issue-triage.md b/doc/articles/contributing/guidelines/issue-triage.md index 540ad33f37e4..0412cc95c8ce 100644 --- a/doc/articles/contributing/guidelines/issue-triage.md +++ b/doc/articles/contributing/guidelines/issue-triage.md @@ -38,7 +38,7 @@ Community support requests should be directed to: * Our [documentation](https://platform.uno/docs/) and [troubleshooting guide](xref:Uno.UI.CommonIssues). * [GitHub Discussions](https://github.com/unoplatform/uno/discussions) * The [Discord Server](https://platform.uno/discord) -* On [X/Twitter using the #unoplatform](https://twitter.com/search?q=%23unoplatform) hashtag. +* On [X/Twitter using the #unoplatform](https://x.com/search?q=%23unoplatform) hashtag. Organizations that want a deeper level of support beyond community support should be directed to [contact Uno Platform](https://platform.uno/contact/) to discuss obtaining professional support. diff --git a/doc/articles/uno-development/ways-to-contribute.md b/doc/articles/uno-development/ways-to-contribute.md index 228c03602646..f434f35a6974 100644 --- a/doc/articles/uno-development/ways-to-contribute.md +++ b/doc/articles/uno-development/ways-to-contribute.md @@ -64,7 +64,7 @@ You can: - present Uno at a local user group - share your open-source Uno projects -Whatever you do, let us know [through Twitter](https://twitter.com/unoplatform) or via info@platform.uno. +Whatever you do, let us know [through X/Twitter](https://x.com/unoplatform) or via mailto:info@platform.uno. ## Contributing code From 0930c9e81733d071ce95814d00bcffbc3e66c759 Mon Sep 17 00:00:00 2001 From: Dominik Titl <78549750+morning4coffe-dev@users.noreply.github.com> Date: Thu, 8 Aug 2024 12:10:23 +0200 Subject: [PATCH 13/18] chore: Adjust xref link --- doc/articles/migrating-from-xamarin-to-net6.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/articles/migrating-from-xamarin-to-net6.md b/doc/articles/migrating-from-xamarin-to-net6.md index abb266541db4..5efa669378a2 100644 --- a/doc/articles/migrating-from-xamarin-to-net6.md +++ b/doc/articles/migrating-from-xamarin-to-net6.md @@ -16,8 +16,8 @@ There are two ways to migrate an application to .NET 7. 1. In a separate folder, create a new application from the templates using [`dotnet new unoapp -o MyApp`](get-started-dotnet-new.md) (MyApp being of the same name as your existing app), or by using the Visual Studio `Uno Platform App` template 2. Move the `MyApp.Mobile` project folder and include it in your existing solution - 3. Make the adjustments to move from the [UWP APIs to the WinUI APIs](xref:updating-to-winui3.md) - 4. Optionally [convert your legacy Xamarin heads](xref:updating-to-winui3.md) to use Uno.WinUI instead of Uno.UI + 3. Make the adjustments to move from the [UWP APIs to the WinUI APIs](xref:Uno.Development.UpdatingToWinUI3) + 4. Optionally [convert your legacy Xamarin heads](xref:Uno.Development.UpdatingToWinUI3) to use Uno.WinUI instead of Uno.UI ## Additional considerations From 4541ba71ddf25cff39afed391d3f0c2f7d056a5c Mon Sep 17 00:00:00 2001 From: Dominik Titl <78549750+morning4coffe-dev@users.noreply.github.com> Date: Fri, 9 Aug 2024 08:28:23 +0200 Subject: [PATCH 14/18] chore: Update libinput link --- doc/articles/features/using-linux-framebuffer.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/articles/features/using-linux-framebuffer.md b/doc/articles/features/using-linux-framebuffer.md index 64ab92aada5b..7e4a71c87394 100644 --- a/doc/articles/features/using-linux-framebuffer.md +++ b/doc/articles/features/using-linux-framebuffer.md @@ -4,7 +4,7 @@ uid: Uno.Skia.Linux.Framebuffer # Using the Linux FrameBuffer and `libinput` -Uno Platform supports the [Linux FrameBuffer](https://www.kernel.org/doc/html/latest/fb/framebuffer.html) and [libinput](https://github.com/wayland-project/libinput) as a target, in the case where your target device does not provide a Window Manager. +Uno Platform supports the [Linux FrameBuffer](https://www.kernel.org/doc/html/latest/fb/framebuffer.html) and [libinput](https://wayland.freedesktop.org/libinput/doc/latest/what-is-libinput.html) as a target, in the case where your target device does not provide a Window Manager. There are some restrictions for the support for the FrameBuffer: From ff617179ed83a0991ae58ac91ce4c87ed015d955 Mon Sep 17 00:00:00 2001 From: Dominik Titl <78549750+morning4coffe-dev@users.noreply.github.com> Date: Fri, 9 Aug 2024 08:52:36 +0200 Subject: [PATCH 15/18] chore: Misc link fixes --- doc/articles/Uno-UI-Performance.md | 2 +- doc/articles/features/using-the-uno-sdk.md | 2 +- .../getting-started/wizard/includes/authentication.md | 4 ++-- .../getting-started/wizard/includes/extensions.md | 8 ++++---- doc/articles/uno-development/contributing-intro.md | 2 +- doc/articles/uno-development/debugging-uno-ui.md | 2 +- 6 files changed, 10 insertions(+), 10 deletions(-) diff --git a/doc/articles/Uno-UI-Performance.md b/doc/articles/Uno-UI-Performance.md index c4c855387690..34c838b5507b 100644 --- a/doc/articles/Uno-UI-Performance.md +++ b/doc/articles/Uno-UI-Performance.md @@ -152,7 +152,7 @@ Here's what to look for: ### Profiling applications -A profiling guide for Uno Platform apps is [available here](ref:Uno.Tutorials.ProfilingApplications). +A profiling guide for Uno Platform apps is [available here](xref:Uno.Tutorials.ProfilingApplications). ### FrameworkTemplatePool diff --git a/doc/articles/features/using-the-uno-sdk.md b/doc/articles/features/using-the-uno-sdk.md index 3fa70969df17..89b78497b585 100644 --- a/doc/articles/features/using-the-uno-sdk.md +++ b/doc/articles/features/using-the-uno-sdk.md @@ -67,7 +67,7 @@ Here are the supported features: | `Navigation` | Adds support for [Navigation](xref:Uno.Extensions.Navigation.Overview) using [Uno.Extensions](xref:Uno.Extensions.Overview). | | `LoggingSerilog` | Adds support for [Serilog](https://github.com/serilog/serilog) using [Uno.Extensions](xref:Uno.Extensions.Overview). | | `Storage` | Adds support for [Storage](xref:Uno.Extensions.Storage.Overview) using [Uno.Extensions](xref:Uno.Extensions.Overview). | -| `Serialization` | Adds support for [Serialization](Uno.Extensions.Serialization.Overview) using [Uno.Extensions](xref:Uno.Extensions.Overview). | +| `Serialization` | Adds support for [Serialization](xref:Uno.Extensions.Serialization.Overview) using [Uno.Extensions](xref:Uno.Extensions.Overview). | | `Toolkit` | Adds support for the [Uno.Toolkit](xref:Toolkit.GettingStarted). | | `Material` | Adds support for the [Material Design Theme](xref:Uno.Themes.Material.GetStarted) library. If the `Toolkit` feature is also used, it will add support for the [Material Design Toolkit](xref:Toolkit.GettingStarted.Material) library. | | `Cupertino` | Adds support for the [Cupertino Design Theme](xref:Uno.Themes.Cupertino.GetStarted) library. If the `Toolkit` feature is also used, it will add support for the [Cupertino Design Toolkit](xref:Toolkit.GettingStarted.Cupertino) library. | diff --git a/doc/articles/getting-started/wizard/includes/authentication.md b/doc/articles/getting-started/wizard/includes/authentication.md index 27a55bc797b3..951e40ec693f 100644 --- a/doc/articles/getting-started/wizard/includes/authentication.md +++ b/doc/articles/getting-started/wizard/includes/authentication.md @@ -1,4 +1,4 @@ -Adds Uno Platform's [Custom Authentication](xref:Learn.Tutorials.Authentication.HowToAuthentication) support to the generated project. +Adds Uno Platform's [Custom Authentication](xref:Uno.Extensions.Authentication.HowToAuthentication) support to the generated project. Using Uno's authentication tools you can easily integrate in your app a login screen and authenticate users. It also helps you manage and track the state of the app's authentication, by allowing you to log out or switch users as well as other authentication-related actions. @@ -44,7 +44,7 @@ Uno.Extensions.Authentication currently supports these types of authentication: dotnet new unoapp -auth web ``` -Read the [Authentication documentation](xref:Overview.Authentication) to get more knowledge about Uno Platform's authentication support and the tools it provides. +Read the [Authentication documentation](xref:Uno.Extensions.Authentication.Overview) to get more knowledge about Uno Platform's authentication support and the tools it provides. > [!NOTE] > The Authentication option is selected by default in the Default template, and not in the Blank one. diff --git a/doc/articles/getting-started/wizard/includes/extensions.md b/doc/articles/getting-started/wizard/includes/extensions.md index 9ad1ebc62f35..27082372c175 100644 --- a/doc/articles/getting-started/wizard/includes/extensions.md +++ b/doc/articles/getting-started/wizard/includes/extensions.md @@ -9,7 +9,7 @@ The available extensions are: Dependency Injection (DI) is an Inversion of Control (IoC) technique that enables consuming classes not to worry about the management or creation of their dependencies and instead rely on a central service to provide it when needed, based on how the provider was configured. -Uno Platform brings the power of [Microsoft Extensions Dependency Injection](https://learn.microsoft.com/dotnet/core/extensions/dependency-injection) to all OSs Uno Platform targets and adds its additional functionality via its Uno.Extensions.DependencyInjection library, which you can learn more about [here](xref:Overview.DependencyInjection). +Uno Platform brings the power of [Microsoft Extensions Dependency Injection](https://learn.microsoft.com/dotnet/core/extensions/dependency-injection) to all operating systems it targets and enhances it with additional functionality through its Uno.Extensions.DependencyInjection library. You can learn more about it in the [Uno.Extensions.DependencyInjection overview](xref:Uno.Extensions.DependencyInjection.Overview). This is included by default in the recommended preset, but not in the blank preset. @@ -24,7 +24,7 @@ dotnet new unoapp -di This extension provides a way to load application configuration data from and to various sources using the [Options Pattern](https://learn.microsoft.com/dotnet/core/extensions/options). This is included by default in the recommended preset, but not in the blank preset. -Refer to the [Uno Configuration](xref:Overview.Configuration) documentation for more information. +Refer to the [Uno Configuration](xref:Uno.Extensions.Configuration.Overview) documentation for more information. ```dotnetcli dotnet new unoapp -config @@ -34,9 +34,9 @@ dotnet new unoapp -config Uno.Extensions.Http allows for the registration of API endpoints as multiple typed HttpClient instances. In this centralized location for accessing web resources, the lifecycle of the corresponding HttpMessageHandler objects is managed. Added clients can optionally be configured to use the platform-native handler. Additional functionality is provided to clear cookies or log diagnostic messages in responses. This library uses Microsoft.Extensions.Http for any HTTP-related work. This is included by default in the recommended preset, but not in the blank preset. -For more documentation on HTTP requests, [read the documentation](xref:Overview.Http). +For more documentation on HTTP requests, [read the documentation](xref:Uno.Extensions.Http.Overview). -Refer to the [documentation](xref:Overview.Http#refit) to learn how to use it in an Uno Platform app. +Refer to the [documentation](xref:Uno.Extensions.Http.Overview#Refit) to learn how to use it in an Uno Platform app. ```dotnetcli dotnet new unoapp -http diff --git a/doc/articles/uno-development/contributing-intro.md b/doc/articles/uno-development/contributing-intro.md index f5964b53786d..b1c7760f638d 100644 --- a/doc/articles/uno-development/contributing-intro.md +++ b/doc/articles/uno-development/contributing-intro.md @@ -36,7 +36,7 @@ See how to implement a new [feature here](xref:Uno.Contributing.ImplementWinUIWi ## Experimenting with Samples App -The [Samples App](../../../src/SamplesApp) is the development app contained in the Uno.UI solution. It serves as a UI and Runtime Tests host, as well as a playground for validating other API scenarios. +The [Samples App](xref:Uno.Contributing.SamplesApp) is the development app contained in the Uno.UI solution. It serves as a UI and Runtime Tests host, as well as a playground for validating other API scenarios. This app is available live at these locations, built from the default branch: diff --git a/doc/articles/uno-development/debugging-uno-ui.md b/doc/articles/uno-development/debugging-uno-ui.md index ffa8ab2df785..0342ace30cd9 100644 --- a/doc/articles/uno-development/debugging-uno-ui.md +++ b/doc/articles/uno-development/debugging-uno-ui.md @@ -75,7 +75,7 @@ If this is the case: - Make sure to build the app once to populate the nuget cache - Rebuild the Uno.UI project (or **Uno.UI.WebAssembly**/**Uno.UI.Skia**) to replace the binaries with your debug ones - Rebuild your app and debug your again -- Make sure that you're debugging the right flavor of Uno (Uno.UI vs. Uno.WinUI). You can debug the UWP flavor [using this conversion tool](xref:no.Contributing.UWPConversion). +- Make sure that you're debugging the right flavor of Uno (Uno.UI vs. Uno.WinUI). You can debug the UWP flavor [using this conversion tool](xref:Uno.Contributing.UWPConversion). ## Microsoft Source Link support From 89b407bde346b76d151c15aff2ac9f4a2ced1a27 Mon Sep 17 00:00:00 2001 From: Dominik Titl <78549750+morning4coffe-dev@users.noreply.github.com> Date: Fri, 9 Aug 2024 08:58:42 +0200 Subject: [PATCH 16/18] chore: Update localization link --- doc/articles/getting-started/wizard/includes/extensions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/articles/getting-started/wizard/includes/extensions.md b/doc/articles/getting-started/wizard/includes/extensions.md index 27082372c175..e3bd6fbd987d 100644 --- a/doc/articles/getting-started/wizard/includes/extensions.md +++ b/doc/articles/getting-started/wizard/includes/extensions.md @@ -47,7 +47,7 @@ dotnet new unoapp -http The Localization extension is responsible for managing globalization in your app. This enables keeping all translations of your app in a single place and enables the user to easily switch the UI language. -The generated app contains *resw* files which can be used to define the application strings. The defined languages are configured in *appsettings.json*. Follow [this link](xref:Learn.Tutorials.Localization.HowToUseLocalization#3-update-the-ui-culture-with-localizationsettings) to learn how to switch the UI culture. +The generated app contains *resw* files, which are used to define the application strings. The supported languages are configured in *appsettings.json*. To learn how to switch the UI culture, refer to the [localization tutorial](xref:Uno.Extensions.Localization.HowToUseLocalization#4-update-the-ui-culture-with-localizationsettings). ![Visual Studio Solution Explorer showing localization files](../assets/localization.jpg) From 94005b0d9605700365c7004eff0e2dc119065f4a Mon Sep 17 00:00:00 2001 From: Dominik Titl <78549750+morning4coffe-dev@users.noreply.github.com> Date: Thu, 15 Aug 2024 10:30:26 +0200 Subject: [PATCH 17/18] chore: Adjust from PR review --- doc/articles/common-issues-all-ides.md | 2 +- doc/articles/migrating-from-xamarin-to-net6.md | 4 ++-- doc/articles/uno-development/building-uno-ui.md | 2 +- doc/articles/uno-development/contributing-intro.md | 6 +++--- doc/articles/uno-development/ways-to-contribute.md | 2 +- doc/blog/201809-uno-wasm-intro-part-01.md | 2 +- 6 files changed, 9 insertions(+), 9 deletions(-) diff --git a/doc/articles/common-issues-all-ides.md b/doc/articles/common-issues-all-ides.md index 331244040fa3..41479a3f0359 100644 --- a/doc/articles/common-issues-all-ides.md +++ b/doc/articles/common-issues-all-ides.md @@ -21,7 +21,7 @@ Try building your project again. ## Runtime error `No parameterless constructor defined for XXXX` -This error is generally caused by some missing [IL Linker](https://github.com/dotnet/runtime/tree/main/src/tools/illink) configuration on WebAssembly. You may need to add some of your application assemblies in the LinkerConfig.xml file of your project. You can find [additional information in the documentation](features/using-il-linker-webassembly.md). +This error is generally caused by some missing [IL Linker](https://github.com/dotnet/runtime/tree/main/src/tools/illink) configuration on WebAssembly. You may need to add some of your application assemblies in the LinkerConfig.xml file of your project. You can find [additional information in the documentation](xref:uno.articles.features.illinker). Similar error messages using various libraries: diff --git a/doc/articles/migrating-from-xamarin-to-net6.md b/doc/articles/migrating-from-xamarin-to-net6.md index 5efa669378a2..3e7b0b9d9133 100644 --- a/doc/articles/migrating-from-xamarin-to-net6.md +++ b/doc/articles/migrating-from-xamarin-to-net6.md @@ -7,14 +7,14 @@ There are two ways to migrate an application to .NET 7. ## The fastest path to keep using the UWP APIs - 1. In a separate folder, create a new application from the templates using [`dotnet new unoapp-uwp-net6 -o MyApp`](get-started-dotnet-new.md) (MyApp being of the same name as your existing app), + 1. In a separate folder, create a new application from the templates using [`dotnet new unoapp-uwp-net6 -o MyApp`](xref:Uno.GetStarted.dotnet-new) (MyApp being of the same name as your existing app), 2. Move the `MyApp.Mobile` project folder and include it in your existing solution 3. Make the adjustments for your new application head to build 4. Optionally remove the legacy Xamarin heads, once you're done with the migration ## The forward looking path using the WinUI/WinApp SDK APIs - 1. In a separate folder, create a new application from the templates using [`dotnet new unoapp -o MyApp`](get-started-dotnet-new.md) (MyApp being of the same name as your existing app), or by using the Visual Studio `Uno Platform App` template + 1. In a separate folder, create a new application from the templates using [`dotnet new unoapp -o MyApp`](xref:Uno.GetStarted.dotnet-new) (MyApp being of the same name as your existing app), or by using the Visual Studio `Uno Platform App` template 2. Move the `MyApp.Mobile` project folder and include it in your existing solution 3. Make the adjustments to move from the [UWP APIs to the WinUI APIs](xref:Uno.Development.UpdatingToWinUI3) 4. Optionally [convert your legacy Xamarin heads](xref:Uno.Development.UpdatingToWinUI3) to use Uno.WinUI instead of Uno.UI diff --git a/doc/articles/uno-development/building-uno-ui.md b/doc/articles/uno-development/building-uno-ui.md index 5fc95dee1920..212e0688a932 100644 --- a/doc/articles/uno-development/building-uno-ui.md +++ b/doc/articles/uno-development/building-uno-ui.md @@ -15,7 +15,7 @@ This article explains how to build Uno.UI locally, for instance, if you wish to - To build the UWP flavor of Uno, you'll need **UWP Development**, install all recent UWP SDKs, starting from 10.0.19041 (or above or equal to `TargetPlatformVersion` line [in this file](https://github.com/unoplatform/uno/blob/master/src/Uno.CrossTargetting.targets)) - Install (**Tools** / **Android** / **Android SDK manager**) all Android SDKs starting from 7.1 (or the Android versions `TargetFrameworks` [list used here](https://github.com/unoplatform/uno/blob/master/src/Uno.UI.BindingHelper.Android/Uno.UI.BindingHelper.Android.netcoremobile.csproj)) - Run [Uno.Check](https://github.com/unoplatform/uno.check) on your dev machine to setup .NET Android/iOS workloads -- Install the version of the .NET SDK specified in [global.json](https://github.com/unoplatform/uno/blob/master/global.json). +- Install the latest [.NET SDK](https://aka.ms/dotnet/download) from Microsoft. ## Recommended Windows hardware diff --git a/doc/articles/uno-development/contributing-intro.md b/doc/articles/uno-development/contributing-intro.md index b1c7760f638d..fb8c3d540d68 100644 --- a/doc/articles/uno-development/contributing-intro.md +++ b/doc/articles/uno-development/contributing-intro.md @@ -20,11 +20,11 @@ Get an [in-depth introduction to how Uno works](uno-internals-overview.md), or j For the prerequisites you'll need, as well as useful tips like using [solution filters](https://learn.microsoft.com/visualstudio/ide/filtered-solutions) and cross-targeting overrides to quickly load and build Uno for a single platform, start with the guide to [Building Uno.UI](building-uno-ui.md). The guide to [Debugging Uno.UI](debugging-uno-ui.md) will show you how to debug Uno.UI code either in the included UI samples or in an application outside the Uno.UI solution. -If you're doing development for Uno's macOS support, you'll need to build and run Uno using Visual Studio for Mac. [There's a separate guide for that here](building-uno-macos.md). +If you're doing development for Uno's macOS support, you'll need to build and run Uno using Visual Studio for Mac. [There's a separate guide for that here](xref:Uno.Contributing.BuildingUnomacOS). -You can contribute to Uno directly from your browser using GitPod, [find out how](../features/working-with-gitpod.md). +You can contribute to Uno directly from your browser using GitPod, [find out how](xref:Uno.Features.Gitpod). -Whether you're fixing a bug or working on a new feature, [inspecting the visual tree of a running app](debugging-inspect-visual-tree.md) is often a key step. +Whether you're fixing a bug or working on a new feature, [inspecting the visual tree of a running app](xref:Uno.Contributing.InspectVisualTree) is often a key step. ## Writing code in Uno diff --git a/doc/articles/uno-development/ways-to-contribute.md b/doc/articles/uno-development/ways-to-contribute.md index f434f35a6974..7c0e33171d77 100644 --- a/doc/articles/uno-development/ways-to-contribute.md +++ b/doc/articles/uno-development/ways-to-contribute.md @@ -64,7 +64,7 @@ You can: - present Uno at a local user group - share your open-source Uno projects -Whatever you do, let us know [through X/Twitter](https://x.com/unoplatform) or via mailto:info@platform.uno. +Whatever you do, let us know [through X/Twitter](https://x.com/unoplatform), our [Discord Server](https://platform.uno/discord) in #contributing, or by emailing us at [info@platform.uno](mailto:info@platform.uno). ## Contributing code diff --git a/doc/blog/201809-uno-wasm-intro-part-01.md b/doc/blog/201809-uno-wasm-intro-part-01.md index 30dabcc4a92b..533970d98ca6 100644 --- a/doc/blog/201809-uno-wasm-intro-part-01.md +++ b/doc/blog/201809-uno-wasm-intro-part-01.md @@ -36,7 +36,7 @@ Consuming a WebAssembly module is generally composed of a `.wasm` file and a JS ## Why WebAssembly ? -WebAssembly is mainly trying to solve the issues that makes it difficult to optimize performance for large applications, provide access to binary-producing languages and improve the security of running the resulting code. +WebAssembly is mainly trying to solve the issues that make it difficult to optimize performance for large applications, provide access to binary-producing languages, and improve the security of running the resulting code. WebAssembly modules are defined as self-contained units of byte code. It's possible to use [streaming compilation](https://webassembly.github.io/spec/web-api/index.html#streaming-modules) to concurrently process the byte code as it is being downloaded, unlike JavaScript where the source file needs to be fully parsed to make sense. From a963c2c5fffee2278c0b424bd835f3b55a2ace90 Mon Sep 17 00:00:00 2001 From: Dominik Titl <78549750+morning4coffe-dev@users.noreply.github.com> Date: Thu, 15 Aug 2024 17:10:16 +0200 Subject: [PATCH 18/18] chore: Move more links to xref --- doc/articles/get-started-next-steps.md | 2 +- .../guides/silverlight-migration/01-create-uno-solution.md | 2 +- .../guides/silverlight-migration/08-data-access-overview.md | 2 +- .../guides/silverlight-migration/09-client-auth-service.md | 4 ++-- .../11-implementing-identity-service-client.md | 2 +- .../guides/silverlight-migration/99-useful-resources.md | 2 +- doc/articles/howto-consume-webservices.md | 2 +- doc/articles/interop/wasm-javascript-2.md | 2 +- doc/articles/interop/wasm-javascript-3.md | 2 +- doc/articles/uno-development/docfx.md | 2 +- doc/articles/uno-howto-create-a-repro.md | 4 ++-- doc/articles/wpf-migration.md | 6 +++--- 12 files changed, 16 insertions(+), 16 deletions(-) diff --git a/doc/articles/get-started-next-steps.md b/doc/articles/get-started-next-steps.md index 82ab66c69b83..e87babc352f0 100644 --- a/doc/articles/get-started-next-steps.md +++ b/doc/articles/get-started-next-steps.md @@ -65,7 +65,7 @@ Microsoft MVP Skye Hoefling put together [Uno Platform: Getting Started Series]( ### Raspberry Pi Applications with Uno Platform (Free) -If you are looking to bring your cross-platform apps to Raspberry Pi with Uno Platform, Peter Gallagher wrote an [article to help you get started]( https://www.petecodes.co.uk/developing-uwp-apps-for-the-raspberry-pi-with-uno-platform/) or try our [getting started with Raspberry Pi documentation]( https://platform.uno/docs/articles/guides/raspberry-pi/raspberry-pi-intro.html). +If you are looking to bring your cross-platform apps to Raspberry Pi with Uno Platform, Peter Gallagher wrote an [article to help you get started](https://www.petecodes.co.uk/developing-uwp-apps-for-the-raspberry-pi-with-uno-platform/) or try our [getting started with Raspberry Pi documentation](xref:Uno.RaspberryPi.Intro). ### XAML Fundamentals for Web and Mobile (Free) diff --git a/doc/articles/guides/silverlight-migration/01-create-uno-solution.md b/doc/articles/guides/silverlight-migration/01-create-uno-solution.md index 09ea230e9dcf..5642d3454924 100644 --- a/doc/articles/guides/silverlight-migration/01-create-uno-solution.md +++ b/doc/articles/guides/silverlight-migration/01-create-uno-solution.md @@ -65,7 +65,7 @@ As part of the continuing evolution of desktop development on Windows, Microsoft > [!NOTE] > The Uno Platform has great support for WinUI 2.x and preview support for WinUI 3: > -> * For WinUI 2.5, see [Fluent-styled controls](https://platform.uno/docs/articles/features/fluent-styles.html) +> * For WinUI 2.5, see [Fluent-styled controls](xref:Uno.Features.FluentStyles) > * For WinUI 3, see [Uno Platform 3.3 – Day 0 support for WinUI 3 Preview 3, Android 11](https://platform.uno/blog/uno-platform-3-3-day-0-support-for-winui-3-preview-3-android-11/). > > [!TIP] diff --git a/doc/articles/guides/silverlight-migration/08-data-access-overview.md b/doc/articles/guides/silverlight-migration/08-data-access-overview.md index 4ffd1630a0eb..ac34a53b70ab 100644 --- a/doc/articles/guides/silverlight-migration/08-data-access-overview.md +++ b/doc/articles/guides/silverlight-migration/08-data-access-overview.md @@ -26,7 +26,7 @@ Unfortunately, WCF itself has been discontinued, although there are, of course, > [!TIP] > In the sample migration of TimeEntryRIA to Uno, ASP.NET Core Web APIs were used. You can find a full article discussing how to consume a web service with Uno below: > -> * [How to consume a web service](https://platform.uno/docs/articles/howto-consume-webservices.html) +> * [How to consume a web service](xref:Uno.Development.ConsumeWebApi) > > [!NOTE] > You can learn more about alternate service technologies here: diff --git a/doc/articles/guides/silverlight-migration/09-client-auth-service.md b/doc/articles/guides/silverlight-migration/09-client-auth-service.md index 81a31d3d2e88..7b5433a9e1ff 100644 --- a/doc/articles/guides/silverlight-migration/09-client-auth-service.md +++ b/doc/articles/guides/silverlight-migration/09-client-auth-service.md @@ -80,8 +80,8 @@ The code to retrieve the access token is encapsulated within the a class **Ident > [!TIP] > You can learn more about platform-specific C# and XAML here: > - > * [Platform-specific C# code in Uno](https://platform.uno/docs/articles/platform-specific-csharp.html) - > * [Platform-specific XAML markup in Uno](https://platform.uno/docs/articles/platform-specific-xaml.html) + > * [Platform-specific C# code in Uno](xref:Uno.Development.PlatformSpecificCSharp) + > * [Platform-specific XAML markup in Uno](xref:Uno.Development.PlatformSpecificXaml) 1. To supply the required parameters to the **IdentityServerClient** class, add the following constructor: diff --git a/doc/articles/guides/silverlight-migration/11-implementing-identity-service-client.md b/doc/articles/guides/silverlight-migration/11-implementing-identity-service-client.md index 126c3784f33c..5c705f44f2b9 100644 --- a/doc/articles/guides/silverlight-migration/11-implementing-identity-service-client.md +++ b/doc/articles/guides/silverlight-migration/11-implementing-identity-service-client.md @@ -72,7 +72,7 @@ As mentioned earlier, the server-side of this service is out-of-scope for the ar > [!NOTE] > The implementation of the identity client API will be based heavily on the code discussed in the article below: > -> * [How to consume a web service](https://platform.uno/docs/articles/howto-consume-webservices.html) +> * [How to consume a web service](xref:Uno.Development.ConsumeWebApi) ## Adding a WebApiBase class diff --git a/doc/articles/guides/silverlight-migration/99-useful-resources.md b/doc/articles/guides/silverlight-migration/99-useful-resources.md index 25aa02cd8ab6..4546d2856e0e 100644 --- a/doc/articles/guides/silverlight-migration/99-useful-resources.md +++ b/doc/articles/guides/silverlight-migration/99-useful-resources.md @@ -5,7 +5,7 @@ uid: Uno.SilverlightMigration.UsefulResources # Useful resources * Uno Platform: - * [Using Uno - getting started on Visual Studio](https://platform.uno/docs/articles/get-started-vs.html) + * [Using Uno - getting started on Visual Studio](xref:Uno.GetStarted.vs2022) * Uno Platform Samples: * [unoplatform/Uno.Samples GitHub Repo](https://github.com/unoplatform/Uno.Samples) * [Uno.UI.Toolkit.SL GitHub Repo](https://github.com/unoplatform/Uno.UI.Toolkit.SL) diff --git a/doc/articles/howto-consume-webservices.md b/doc/articles/howto-consume-webservices.md index 2e67fe11da92..ad9306b161ef 100644 --- a/doc/articles/howto-consume-webservices.md +++ b/doc/articles/howto-consume-webservices.md @@ -20,7 +20,7 @@ Throughout the how-to, there will be notes on recommended practices and tips tha > The complete source code that goes along with this tutorial is available in the [unoplatform/Uno.Samples](https://github.com/unoplatform/Uno.Samples) GitHub repository - [TheCatApiClient](https://github.com/unoplatform/Uno.Samples/tree/master/UI/TheCatApiClient) > > [!TIP] -> For a step-by-step guide to installing the prerequisites, see [Getting started on Visual Studio](https://platform.uno/docs/articles/get-started-vs-2022.html) +> For a step-by-step guide to installing the prerequisites, see [Getting started on Visual Studio](xref:Uno.GetStarted.vs2022) ## Task 1 - Create a simple Uno application diff --git a/doc/articles/interop/wasm-javascript-2.md b/doc/articles/interop/wasm-javascript-2.md index 5a3ec3722a1f..c906de4c4aec 100644 --- a/doc/articles/interop/wasm-javascript-2.md +++ b/doc/articles/interop/wasm-javascript-2.md @@ -10,7 +10,7 @@ Let's create an app to integrate a Syntax Highlighter named [`PrismJS`](https:// ### 0. Before starting -📝 To reproduce the code in this article, you must [prepare development environment using Uno's _Getting Started_ article](../get-started.md). +📝 To reproduce the code in this article, you must [prepare a development environment using Uno's _Getting Started_ article](xref:Uno.GetStarted). ### 1. Create the projects diff --git a/doc/articles/interop/wasm-javascript-3.md b/doc/articles/interop/wasm-javascript-3.md index a979348a7ba6..995281958d11 100644 --- a/doc/articles/interop/wasm-javascript-3.md +++ b/doc/articles/interop/wasm-javascript-3.md @@ -14,7 +14,7 @@ Let's create an application illustrating how to use this feature. ### 0. Before starting -📝 To reproduce the code in this article, you must [prepare development environment using Uno's _Getting Started_ article](https://platform.uno/docs/articles/get-started.html). +📝 To reproduce the code in this article, you must [prepare a development environment using Uno's _Getting Started_ article](xref:Uno.GetStarted). ### 1. Create the solution in Visual Studio diff --git a/doc/articles/uno-development/docfx.md b/doc/articles/uno-development/docfx.md index bb3e2cb37ada..e82a778d88c4 100644 --- a/doc/articles/uno-development/docfx.md +++ b/doc/articles/uno-development/docfx.md @@ -6,7 +6,7 @@ uid: Uno.Contributing.DocFx # The Uno docs website and DocFX -Uno Platform's docs website uses [DocFX](https://dotnet.github.io/docfx/) to convert Markdown files in the [articles folder](https://github.com/unoplatform/uno/tree/master/doc/articles) into [html files](https://platform.uno/docs/articles/intro.html). +Uno Platform's docs website uses [DocFX](https://dotnet.github.io/docfx/) to convert Markdown files in the [articles folder](https://github.com/unoplatform/uno/tree/master/doc/articles) into [html files](xref:Uno.Documentation.Intro). ## Adding to the table of contents diff --git a/doc/articles/uno-howto-create-a-repro.md b/doc/articles/uno-howto-create-a-repro.md index fe4d2fd3771d..927db2f37239 100644 --- a/doc/articles/uno-howto-create-a-repro.md +++ b/doc/articles/uno-howto-create-a-repro.md @@ -33,10 +33,10 @@ Some steps and questions to answer: - Add an event handler to `DataContextChanged` in the code behind to see if and when the `DataContext` changed. - Analyze device and app logs for clues about the control's behavior. - You may enable [the controls debug logs](https://github.com/unoplatform/uno/blob/master/doc/articles/logging.md), if any. - - To validate that logs are enabled and in Debug, those starting with `Windows`, `Microsoft` or `Uno` should be visible in the apps output. If not, make sure to [setup the logging properly](https://platform.uno/docs/articles/migrating-from-previous-releases.html). + - To validate that logs are enabled and in Debug, those starting with `Windows`, `Microsoft`, or `Uno` should be visible in the apps output. If not, make sure to [setup the logging properly](xref:Uno.Development.MigratingFromPreviousReleases). - Logs on iOS may need to have the [OSLog logger](https://github.com/unoplatform/uno.extensions.logging) enabled when running on production devices. - Try on different versions of Visual Studio, iOS, Android, Linux, or browsers -- If available, try the API on Windows (UWP or WinUI) and see if it behaves differently that what Uno Platform is doing +- If available, try the API on Windows (UWP or WinUI) and see if it behaves differently than what Uno Platform is doing - When issues occur, try breaking on all exceptions to check if an exception may be hidden and not reported. - Update Uno.WinUI or other dependencies to previous or later versions, using a [bisection technique](https://git-scm.com/docs/git-bisect). Knowing which version of a package introduced an issue can help orienting the investigations. diff --git a/doc/articles/wpf-migration.md b/doc/articles/wpf-migration.md index 201d8161a5a4..c41e5f86cd98 100644 --- a/doc/articles/wpf-migration.md +++ b/doc/articles/wpf-migration.md @@ -35,9 +35,9 @@ The vast majority of your codebase will simply "move across". Existing XAML stru Along the journey to bring your WPF app to the Web, you should become familiar with the Uno Platform documentation. Your team should thoroughly understand what is supported (and where) before you build a feature around it. Learn about: -* [Get started](https://platform.uno/docs/articles/get-started.html) -* [How-tos and tutorials](https://platform.uno/docs/articles/tutorials-intro.html) -* [Development deep-dives](https://platform.uno/docs/articles/using-uno-ui.html) +* [Get started](xref:Uno.GetStarted) +* [How-tos and tutorials](xref:Uno.Tutorials.Intro) +* [Development deep-dives](xref:Uno.Development.Overview) * [Reference](https://platform.uno/docs/articles/implemented-views.html) ## Architecture Considerations