Releases: VincentH-Net/CSharpForMarkup
csharpmarkup2-winui-2-4-18
New in this release:
- Updated to Uno 5.2 including Uno's .NET Single Project and
uno.sdk
! - Added support for latest
dotnet new unoapp
template - Updated to Uno.Extensions.* 4.1
- Updated to Microsoft.WindowsAppSDK 1.5
- Allow
!
in binding expressions - Add
SecondaryCommands
property setter for Uno ToolkitNavigationBar
- Minimize diff in generated source between different versions of dependencies by refining sorting of generated methods, allowing a clear overview on what is new in each release
- Removed workarounds for fixed issues in dependencies:
Breaking changes:
- Renamed
.Stretch()
shorthand method forFrameworkElement
to.HVStretch()
to avoid ambiguity with the.Stretch()
extension method forImage
- The
Uno.Extensions.*
4 NuGets no longer support .NET 7, they are now .NET 8+ so the correspondingCSharpMarkup.WinUI.Uno.Extensions.*
NuGets are now .NET8+ as well
csharpmarkup2-winui-2-3-66
New templates
This release supports the new mcs-uno-markup2
and mcs-uno-view
templates in Modern.CSharp.Templates 1.5.0:
- The
mcs-uno-view
template is used by theNew-View.ps1
script, which is included inmcs-uno-markup2
- Improved frictionless startup for both existing and new Uno solutions - whether created with Uno's
dotnet new unoapp
template or with the Uno solution wizard for Visual Studio. - Add support for .NET 8 / .NET 7, as well as model types MVUX / MVVM / none
- Now pre-structured with best practices for maintainability and code reuse of C# Markup 2 UI.
New methods
This release adds / changes the following methods:
- Add content alignment convenience extension methods for Control: LeftContent, HCenterContent, RightContent, TopContent, VCenterContent, BottomContent, CenterContent, StretchContent
- Add Stretch convenience extension method for FrameworkElement
- Add overload for Page Content extension method with different parameter order for better markup readability
Full Changelog: csharpmarkup2-winui-2-3-64...csharpmarkup2-winui-2-3-66
csharpmarkup2-winui-2-3-64
This release is fully updated to the awesome Uno 5 release and .NET 8 GA. You can use the Uno Solution Wizard for Visual Studio and add a C# Markup 2 project to it at any time with one command. All Uno wizard customizations are supported: combine C# Markup 2 with MVUX or MVVM, XAML or Uno C# Markup, use Uno Navigation extensions, and target .NET 8 or .NET 7. All Uno target platforms are supported.
A brand new dotnet new C# Markup 2 project template gets you going in no time - carefully optimized for an optimal developer experience: uncluttered solution explorer view, automatic file grouping of markup and logic files, uncluttered markup source, focused Intellisense, clear starting points for markup extensions in your code, plus fast hot reload - both automatic and with a hot reload button overlay in debug mode, for the platforms that your IDE can hot reload but cannot (yet) update the UI automatically.
Enjoy general C# Markup 2 improvements, plus C# Markup 2 API's for 5 additional Uno libraries:
- Support for Uno's UI Toolkit, Reactive / MVUX extension and Navigation extensions
- Support for the awesome LiveCharts2
- All
ThemeResource
s searchable in C# Intellisense, strongly typed
The getting started is fully up to date. Examples in this repo and the readme will be updated soon to show off the new features.
NJoy concise C# Markup!
csharpmarkup2-winui-2-3-63-dev-13
csharpmarkup2-winui-2-3-62-dev-2
csharpmarkup2-winui-2-3-61-dev-9
csharpmarkup2-winui-2-3-60-dev-3
csharpmarkup2-winui-2-3-60-dev-1
csharpmarkup2-winui-wpf-2-2-21
Windows App SDK
- Fix to add missing layout type helpers for many types of content properties - both collection and single item type content:
VisualStateGroup
,CommandBar
,Hub
,MenuBarItemFlyout
,MenuFlyout
,MenuFlyoutSubItem
,CommandBarFlyoutCommandBar
,RadioButtons
,TabView
and more - Fix helpers for
ItemsRepeater
ItemTemplate
property plus add manual lambdaDataTemplate
helper - Fix for multiple
ContentAttribute
implementations used in Windows App SDK - Fix for multiple
GradientStop
collection types used in Windows App SDK - Fix for inconsistent parameter order for
GradientStop
between WinUI and Uno - add manual overload to allow specifying offset and color by value without ambiguity - Shorten generated code: omit namespaces that are in using statements from type names
Uno Platform
- Fix to add missing layout type helpers for many types of content properties - both collection and single item type content:
VisualStateGroup
,CommandBar
,Hub
,MenuBarItemFlyout
,MenuFlyout
,MenuFlyoutSubItem
,CommandBarFlyoutCommandBar
,RadioButtons
,TabView
,Border
,Flyout
,MediaPlayerPresenter
,SplitView
,Viewbox
and more - Fix helpers for
ItemsRepeater
ItemTemplate
property plus add manual lambdaDataTemplate
helper - Shorten generated code: omit namespaces that are in using statements from type names
WPF
- Shorten generated code: omit namespaces that are in using statements from type names
Full Changelog: csharpmarkup2-winui-wpf-2-1-14...csharpmarkup2-winui-wpf-2-2-21
csharpmarkup2-winui-wpf-2-1-14
Windows App SDK
- Updated to latest stable Microsoft.WindowsAppSDK 1.3.230602002
Uno Platform
- Updated to latest stable Uno.WinUI 4.9.20
- Map Uno NotImplemented attribute to .NET UnsupportedOSPlatform attribute
Now you will get compile warnings when a WinUI API is not implemented by Uno Platform for a specific target platform;
This is the equivalent of the Uno0001 warning
WPF
- Version of CSharpMarkup.WPF NuGet aligned to version of CSharpMarkup.WinUI NuGet
- Enable Source Link
Full Changelog: csharpmarkup2-winui-2-0-0...csharpmarkup2-winui-wpf-2-1-14