News

Uno Platform 4.7 Sports New Project Template

A New Project Template highlights the list of new features in Uno Platform 4.7, for creating single-source, multi-platform applications that let developers reuse 99 percent of the business logic and UI layer across native mobile, web and desktop projects.

The open source Uno Platform is a partner of Microsoft in the dev tooling space, claiming the only offering that enables development of single-codebase applications for Windows, WebAssembly, iOS, macOS, Android and Linux, targeting all OSes and browsers. It has also teamed up with Redmond on various projects and has sometimes implemented new tech before Microsoft itself. For example, it was the first to provide Ahead of Time (AOT) compilation for WebAssembly, the tech behind client-side Blazor.

Uno Platform
[Click on image for larger view.] Uno Platform(source: Uno Platform).

In the new v4.7 release -- the company's first of 2023 -- the New Project Template is the company's response to community feedback.

"Uno Platform 4.7 brings an updated solution template without using a Shared project," the company announced last week. "In our 2023 Community Survey, we've heard the community feedback about this aspect of our templates being commonly confusing. Thank you for bringing this forward so vocally!"

The non-confusing template looks like this:

New Project Template
[Click on image for larger view.] New Project Template (source: Uno Platform).

"In this updated solution template, the 'Shared Project' is replaced by a regular cross-platform library containing all user code files," Uno Platform said. "This also implies that package references can be included in a single location without the previous need to include those in all project heads." The company said developers aren't required to use the new template and don't need to update to using a class library if they're using a Shared project based structure.

The dev team also unified font loading functionality in projects and noted that it built upon previous library assets work to ensure the Uno Fluent Symbols font is now automatically included when building projects, so there's no longer a need to manage individual font files in project heads. "This change has been made possible by the unification of font loading in projects," the company said. "The presence of a font file in a solution project with the 'Content' build action automatically makes the font available for use in an app. Fonts can also be included in NuGet packages and be transitively used in the project using them."

Performance improvements were also made across a selection of platform areas, including updates to XAML Trimming, .NET 7 WebAssembly, .NET Native AOT, Android and more.

About the Author

David Ramel is an editor and writer at Converge 360.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube