VijayAnand.FormsTemplates 1.6.0

CLI Project and Item Templates for developing Xamarin.Forms App that runs on iOS, Android, and Windows

Project template for Xamarin.Forms 5 Class Library and is named as formsclasslib

Class library project template take the below optional parameters to override its target framework and to include the officially supported Xamarin.CommunityToolkit, Xamarin.CommunityToolkit.Markup, Xamarin.Essentials, CommunityToolkit.Mvvm (aka Microsoft MVVM Toolkit), VijayAnand.Toolkit.Markup (the Shared Toolkit) or all NuGet packages:

• -f | --framework - Default value is netstandard2.0
• -asp | --all-supported-packages - Default value is false
• -it | --include-toolkit - Default value is false
• -im | --include-markup - Default value is false
• -ie | --include-essentials - Default value is false
• -imt | --include-mvvm-toolkit - Default value is false
• -ist | --include-shared-toolkit - Default value is false

Explicit option:

• -iei | --include-essentials-interfaces - Default value is false

Note: The NuGet package version being added out-of-the-box are v2.0.x for the Xamarin Toolkit packages, v1.8.x for the Xamarin.Essentials package, and v8.2.x for the MVVM Toolkit package.

To install the template NuGet package, use the below .NET CLI command:

dotnet new install VijayAnand.FormsTemplates

If you've already installed this package, then it can be updated to the latest version with the below command:

dotnet new update --check-only

dotnet new update

Use the below .NET CLI command to create the project, pages, and views out these templates:

dotnet new formsclasslib -o MyApp.Core

Library target framework override:

dotnet new formsclasslib -o MyApp.Core -f netstandard2.1

Option to include NuGet packages:

dotnet new formsclasslib -o MyApp.UI -it -im -ie -iei -imt -ist

In a single parameter (Essentials Interfaces is an exception, to be explicitly mentioned):

dotnet new formsclasslib -o MyApp.UI -asp -iei

NuGet Central Package Management (CPM) feature:

For now, this is supported only on CLI. Can be used in combination with other parameters too.

dotnet new formsclasslib -o MyApp.UI -cpm

Item Template options:

Here, -n denotes the name of the Page/View that is to be created (for Pages/Shell/Views, don't need to suffix the type like HomePage, OrderView, AppShell and file extension .xaml / .cs, it will be added automatically) (Can also be specified as --name in the expanded form).

Just mention only the name of the item that is to be created. Item Type and File Extension would be automatically added.

Note: If name parameter is not provided, the .NET CLI template engine will take the current folder name in the context as its name.

And -na denotes the namespace under which the file is to be created (Can also be specified as --namespace in the expanded form).

While working with .NET 7 or higher SDK, the namespace parameter in short notation needs to be passed as -p:na (i.e., it needs to be prefixed with -p:).

Page:

dotnet new forms-page -n Login -na MyApp.Views

dotnet new forms-page-cs -n Home -na MyApp.Views

View:

dotnet new forms-view -n Card -na MyApp.Views

dotnet new forms-view-cs -n Order -na MyApp.Views

Shell:

dotnet new forms-shell -n App -na MyApp

dotnet new forms-shell-cs -n Mobile -na MyApp

Resource Dictionary:

With C# code-behind file:

dotnet new forms-resdict -n DefaultTheme -na MyApp.Themes

Without C# code-behind file - Xaml only (The option to be specified is -xo or --xaml-only):

dotnet new forms-resdict -n DarkTheme -na MyApp.Themes -xo