Tags: dotMorten/maui
Tags
[release/6.0.1xx-rc1] Update dependencies from xamarin/xamarin-android ( dotnet#2369) * Update dependencies from https://github.com/xamarin/xamarin-android build 6.0.1xx-rc1-3793f6e34c40e3aa1a00d0dbe6dd0d706283e197-1 Microsoft.Android.Sdk.Windows From Version 31.0.100-rc.1.12 -> To Version 31.0.100-rc.1.16 Dependency coherency updates Microsoft.NETCore.App.Ref,Microsoft.Dotnet.Sdk.Internal,Microsoft.Extensions.Primitives,Microsoft.AspNetCore.App.Runtime.win-x64,Microsoft.Extensions.Hosting,Microsoft.Extensions.Hosting.Abstractions,Microsoft.Extensions.DependencyInjection.Abstractions,Microsoft.Extensions.DependencyInjection,Microsoft.Extensions.Configuration.Abstractions,Microsoft.Extensions.Configuration,Microsoft.Extensions.Logging.Abstractions,Microsoft.Extensions.Logging,Microsoft.Extensions.Logging.Console,Microsoft.Extensions.Logging.Debug,Microsoft.Extensions.FileProviders.Abstractions,Microsoft.AspNetCore.Authorization,Microsoft.AspNetCore.Components.WebView,Microsoft.AspNetCore.Components.Web,Microsoft.JSInterop,Microsoft.WindowsDesktop.App.Runtime.win-x64,System.CodeDom From Version 6.0.0-rc.1.21426.8 -> To Version 6.0.0-rc.1.21451.13 (parent: Microsoft.Dotnet.Sdk.Internal * Remove incorrect LangVersion 9.0 and use default Razor Source Generator needs at least 10.0 * Explicitly set LangVersion=10.0 * Use $(LangVersion) preview, because dotnet/maui builds with VS Context: dotnet/sdk@10efeed...454eae3 This was removed from the dotnet/sdk: <!-- Required to support incremental source generator --> <LangVersion Condition="'$(UseRazorSourceGenerator)' != '' ">preview</LangVersion> So I think we need to opt into `preview` to build with the older Roslyn in VS. * Keep Controls.Core.UnitTests on C# 9 This apparently breaks NUnit `Assert.That()` calls. I could build the project locally after this change. * Try start vs4mac with local dotnet * Revert "Try start vs4mac with local dotnet" This reverts commit 85ce42d. * Update LifecycleEventsTests.cs I think we might also be hitting some method overloading issues in these test failures: * `CanAddMultipleEventsViaMultipleConfigureLifecycleEvents` * `CanAddMultipleEventsViaBuilder` * `EventsFireExactlyOnce` * Revert "Update LifecycleEventsTests.cs" This reverts commit 90c233d. * Keep Core.UnitTests on C# 9 This solves 3 test failures: > .\bin\dotnet\dotnet.exe test src\Core\tests\UnitTests\Core.UnitTests-net6.csproj -bl ... [xUnit.net 00:00:00.60] CanAddMultipleEventsViaMultipleConfigureLifecycleEvents [FAIL] Failed CanAddMultipleEventsViaMultipleConfigureLifecycleEvents [10 ms] Error Message: Assert.Equal() Failure Expected: 1 Actual: 0 Stack Trace: at Microsoft.Maui.UnitTests.LifecycleEvents.LifecycleEventsTests.CanAddMultipleEventsViaMultipleConfigureLifecycleEvents() in C:\src\maui\src\Core\tests\UnitTests\LifecycleEvents\LifecycleEventsTests.cs:line 134 [xUnit.net 00:00:00.62] EventsFireExactlyOnce [FAIL] [xUnit.net 00:00:00.62] CanAddMultipleEventsViaBuilder [FAIL] Failed EventsFireExactlyOnce [2 ms] Error Message: Assert.Equal() Failure Expected: 1 Actual: 0 Stack Trace: at Microsoft.Maui.UnitTests.LifecycleEvents.LifecycleEventsTests.EventsFireExactlyOnce() in C:\src\maui\src\Core\tests\UnitTests\LifecycleEvents\LifecycleEventsTests.cs:line 75 Failed CanAddMultipleEventsViaBuilder [2 ms] Error Message: Assert.Equal() Failure Expected: 1 Actual: 0 Stack Trace: at Microsoft.Maui.UnitTests.LifecycleEvents.LifecycleEventsTests.CanAddMultipleEventsViaBuilder() in C:\src\maui\src\Core\tests\UnitTests\LifecycleEvents\LifecycleEventsTests.cs:line 156 Failed! - Failed: 3, Passed: 367, Skipped: 0, Total: 370, Duration: 192 ms - Microsoft.Maui.UnitTests.dll (net6.0) Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com> Co-authored-by: Eilon Lipton <Eilon@users.noreply.github.com> Co-authored-by: Jonathan Peppers <jonathan.peppers@microsoft.com> Co-authored-by: Rui Marinho <me@ruimarinho.net>
Update OutputType to WinExe on -windows (dotnet#2340) * Update OutputType to WinExe on -windows This happens in the sdk targets/props but not quite early enough to influence the `EnableWin32Codegen` property which causes `[STAThreadAttribute]` to be generated in the Windows app. * For non-blazor projects, interpreter is fine Blazor android projects (and possibly iOS?) will require this runtime fix: dotnet/runtime#58467 So, enabling interpreter again on non-blazor templates
AppxPackageRecipe prop no longer needed (dotnet#2332) * AppxPackageRecipe prop no longer needed Updated Single Project MSIX VSIX fixes the problem this workaround initially addressed, and now this work around causes issues itself, so removing. * Disable interpreter by default (Android has debug issues currently) * Disable interpreter by default (Android has debug issues currently) * Remove old comment * Remove old comment
Support Min/Max Height/Width on IView (dotnet#2265) * Min/max height/width for Android/iOS/Windows Fixes dotnet#709 * Set up constants for Core min/max/explicit default values * Fix up device tests and directly set Windows height/width * Add implementation to benchmark stub; make negative dimension exceptions consistent * Check for unset values in min height/width VisualElement properties * Remove now irrelevant comments * Use correct property * Remove the tests that no longer make any sense * Not sure how this test ever worked * shrug * Cleanup * Use correct version of Width/Height for ScrollView * Use measurespec instead of raw values when measuring PageViewGroup * Don't let VET force the page back to 0x0 * Stomp out another -1 * Use correct unset value * stomp stomp stomp * Add extra MauiContext null check for when the old layout system tries to force a layout too early * Enable AbsoluteLayout for iOS Co-authored-by: Matthew Leibowitz <mattleibow@live.com>
Add template icons (dotnet#2278) * Fix the templates * undo that * Microsoft.Maui.Extensions is now a library pack * Add template icons * "New" icons * newer icons * .ico * Restore BundledVersions.in.targets * revert
PreviousNext