867184-Integrate .NET MAUI Scheduler with android native embedding application

NativeEmbedding_Scheduler/NativeEmbedding_Scheduler.sln

@@ -0,0 +1,27 @@
+
+Microsoft Visual Studio Solution File, Format Version 12.00
+# Visual Studio Version 17
+VisualStudioVersion = 17.8.34408.163
+MinimumVisualStudioVersion = 10.0.40219.1
+Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "NativeEmbedding_Scheduler", "NativeEmbedding_Scheduler\NativeEmbedding_Scheduler.csproj", "{1D6B6F8C-0ACB-4BDF-9E96-A8B68684FA8F}"
+EndProject
+Global
+	GlobalSection(SolutionConfigurationPlatforms) = preSolution
+		Debug|Any CPU = Debug|Any CPU
+		Release|Any CPU = Release|Any CPU
+	EndGlobalSection
+	GlobalSection(ProjectConfigurationPlatforms) = postSolution
+		{1D6B6F8C-0ACB-4BDF-9E96-A8B68684FA8F}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
+		{1D6B6F8C-0ACB-4BDF-9E96-A8B68684FA8F}.Debug|Any CPU.Build.0 = Debug|Any CPU
+		{1D6B6F8C-0ACB-4BDF-9E96-A8B68684FA8F}.Debug|Any CPU.Deploy.0 = Debug|Any CPU
+		{1D6B6F8C-0ACB-4BDF-9E96-A8B68684FA8F}.Release|Any CPU.ActiveCfg = Release|Any CPU
+		{1D6B6F8C-0ACB-4BDF-9E96-A8B68684FA8F}.Release|Any CPU.Build.0 = Release|Any CPU
+		{1D6B6F8C-0ACB-4BDF-9E96-A8B68684FA8F}.Release|Any CPU.Deploy.0 = Release|Any CPU
+	EndGlobalSection
+	GlobalSection(SolutionProperties) = preSolution
+		HideSolutionNode = FALSE
+	EndGlobalSection
+	GlobalSection(ExtensibilityGlobals) = postSolution
+		SolutionGuid = {D5B82CF7-B31C-4158-8A87-D90B0BBCBDDB}
+	EndGlobalSection
+EndGlobal

NativeEmbedding_Scheduler/NativeEmbedding_Scheduler/AndroidManifest.xml

@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="utf-8"?>
+<manifest xmlns:android="http://schemas.android.com/apk/res/android">
+  <application android:allowBackup="true" android:icon="@mipmap/appicon" android:label="@string/app_name" android:roundIcon="@mipmap/appicon_round" android:supportsRtl="true">
+  </application>
+  <uses-permission android:name="android.permission.INTERNET" />
+</manifest>

NativeEmbedding_Scheduler/NativeEmbedding_Scheduler/MainActivity.cs

@@ -0,0 +1,45 @@
+using Microsoft.Maui.Embedding;
+using Android.App;
+using Android.OS;
+using Microsoft.Maui.Platform;
+using Syncfusion.Maui.Core.Hosting;
+using Syncfusion.Maui.Scheduler;
+using System.Collections.ObjectModel;
+
+namespace NativeEmbedding_Scheduler
+{
+    [Activity(Label = "@string/app_name", MainLauncher = true)]
+    public class MainActivity : Activity
+    {
+        MauiContext? _mauiContext;
+        protected override void OnCreate(Bundle? savedInstanceState)
+        {
+            base.OnCreate(savedInstanceState);
+
+            MauiAppBuilder builder = MauiApp.CreateBuilder();
+            builder.UseMauiEmbedding<Microsoft.Maui.Controls.Application>();
+            builder.ConfigureSyncfusionCore();
+            MauiApp mauiApp = builder.Build();
+            _mauiContext = new MauiContext(mauiApp.Services, this);
+
+            SfScheduler scheduler = new SfScheduler();
+            scheduler.View = SchedulerView.Week;
+            var appointment = new ObservableCollection<SchedulerAppointment>();
+
+            //Adding scheduler appointment in the schedule appointment collection. 
+            appointment.Add(new SchedulerAppointment()
+            {
+                StartTime = DateTime.Today.AddHours(13),
+                EndTime = DateTime.Today.AddHours(15),
+                Subject = "Client Meeting",
+            });
+
+            //Adding the scheduler appointment collection to the AppointmentsSource of .NET MAUI Scheduler.
+            scheduler.AppointmentsSource = appointment;
+            Android.Views.View view = scheduler.ToPlatform(_mauiContext);
+
+            // Set our view from the "main" layout resource
+            SetContentView(view);
+        }
+    }
+}

NativeEmbedding_Scheduler/NativeEmbedding_Scheduler/NativeEmbedding_Scheduler.csproj

@@ -0,0 +1,16 @@
+<Project Sdk="Microsoft.NET.Sdk">
+	<PropertyGroup>
+		<TargetFramework>net8.0-android</TargetFramework>
+		<SupportedOSPlatformVersion>21</SupportedOSPlatformVersion>
+		<OutputType>Exe</OutputType>
+		<Nullable>enable</Nullable>
+		<UseMaui>true</UseMaui>
+		<ImplicitUsings>enable</ImplicitUsings>
+		<ApplicationId>com.companyname.NativeEmbedding_Scheduler</ApplicationId>
+		<ApplicationVersion>1</ApplicationVersion>
+		<ApplicationDisplayVersion>1.0</ApplicationDisplayVersion>
+	</PropertyGroup>
+	<ItemGroup>
+	  <PackageReference Include="Syncfusion.Maui.Scheduler" Version="*" />
+	</ItemGroup>
+</Project>

NativeEmbedding_Scheduler/NativeEmbedding_Scheduler/Resources/AboutResources.txt

@@ -0,0 +1,44 @@
+Images, layout descriptions, binary blobs and string dictionaries can be included 
+in your application as resource files.  Various Android APIs are designed to 
+operate on the resource IDs instead of dealing with images, strings or binary blobs 
+directly.
+
+For example, a sample Android app that contains a user interface layout (main.xml),
+an internationalization string table (strings.xml) and some icons (drawable-XXX/icon.png) 
+would keep its resources in the "Resources" directory of the application:
+
+Resources/
+    drawable/
+        icon.png
+
+    layout/
+        main.xml
+
+    values/
+        strings.xml
+
+In order to get the build system to recognize Android resources, set the build action to
+"AndroidResource".  The native Android APIs do not operate directly with filenames, but 
+instead operate on resource IDs.  When you compile an Android application that uses resources, 
+the build system will package the resources for distribution and generate a class called "Resource" 
+(this is an Android convention) that contains the tokens for each one of the resources 
+included. For example, for the above Resources layout, this is what the Resource class would expose:
+
+public class Resource {
+    public class Drawable {
+        public const int icon = 0x123;
+    }
+
+    public class Layout {
+        public const int main = 0x456;
+    }
+
+    public class Strings {
+        public const int first_string = 0xabc;
+        public const int second_string = 0xbcd;
+    }
+}
+
+You would then use Resource.Drawable.icon to reference the drawable/icon.png file, or 
+Resource.Layout.main to reference the layout/main.xml file, or Resource.Strings.first_string 
+to reference the first string in the dictionary file values/strings.xml.

NativeEmbedding_Scheduler/NativeEmbedding_Scheduler/Resources/layout/activity_main.xml

@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="utf-8"?>
+<RelativeLayout xmlns:android="http://schemas.android.com/apk/res/android"
+    xmlns:app="http://schemas.android.com/apk/res-auto"
+    xmlns:tools="http://schemas.android.com/tools"
+    android:layout_width="match_parent"
+    android:layout_height="match_parent">
+    <TextView 
+        android:layout_width="wrap_content"
+        android:layout_height="wrap_content"
+        android:layout_centerInParent="true"
+        android:text="@string/app_text"
+    />
+</RelativeLayout>

NativeEmbedding_Scheduler/NativeEmbedding_Scheduler/Resources/mipmap-anydpi-v26/appicon.xml

@@ -0,0 +1,4 @@
+<adaptive-icon xmlns:android="http://schemas.android.com/apk/res/android">
+  <background android:drawable="@mipmap/appicon_background" />
+  <foreground android:drawable="@mipmap/appicon_foreground" />
+</adaptive-icon>

NativeEmbedding_Scheduler/NativeEmbedding_Scheduler/Resources/mipmap-anydpi-v26/appicon_round.xml

@@ -0,0 +1,4 @@
+<adaptive-icon xmlns:android="http://schemas.android.com/apk/res/android">
+  <background android:drawable="@mipmap/appicon_background" />
+  <foreground android:drawable="@mipmap/appicon_foreground" />
+</adaptive-icon>

NativeEmbedding_Scheduler/NativeEmbedding_Scheduler/Resources/values/ic_launcher_background.xml

@@ -0,0 +1,4 @@
+<?xml version="1.0" encoding="utf-8"?>
+<resources>
+    <color name="ic_launcher_background">#2C3E50</color>
+</resources>

NativeEmbedding_Scheduler/NativeEmbedding_Scheduler/Resources/values/strings.xml

@@ -0,0 +1,4 @@
+<resources>
+    <string name="app_name">NativeEmbedding_Scheduler</string>
+    <string name="app_text">Hello, Android!</string>
+</resources>

README.md

@@ -1,2 +1,49 @@
-# How-to-integrate-.NET-MAUI-Scheduler-with-android-native-embedding-application
-This repository contains the sample code to integrate .NET MAUI Scheduler with the android native embedding application.
+# How to integrate .NET MAUI Scheduler with android native embedding application
+
+This repository contains the sample code to integrate [SfScheduler](https://help.syncfusion.com/maui/scheduler/getting-started) with the android native embedding application.
+
+## Syncfusion controls
+
+This project used the following Syncfusion control(s):
+* [.NET MAUI Scheduler (SfScheduler)](https://www.syncfusion.com/maui-controls/maui-scheduler)
+
+## Supported platforms
+
+| Platforms | Supported versions |
+| --------- | ------------------ |
+| Android   | API level 19 and later versions |
+
+## Requirements to run the sample
+
+* [Visual Studio](https://visualstudio.microsoft.com/downloads/)
+* [Visual Studio for Mac](https://visualstudio.microsoft.com/vs/mac)
+
+Refer to the following link for more details: [System Requirements](https://help.syncfusion.com/maui/system-requirements)
+
+## How to run the sample
+
+1. Clone the sample and open it in Visual Studio 2022 preview.
+
+   *Note: If you download the sample using the "Download ZIP" option, right-click it, select Properties, and then select Unblock.*
+
+2. Register your license key in the App.cs file as demonstrated in the following code.
+
+		public App()
+		{
+			//Register Syncfusion license
+			Syncfusion.Licensing.SyncfusionLicenseProvider.RegisterLicense("YOUR LICENSE KEY");
+
+			InitializeComponent();
+
+			MainPage = new MainPage();
+		}
+
+	Refer to this [link](https://help.syncfusion.com/maui/licensing/overview) for more details.
+
+3. Clean and build the application.
+
+4. Run the application.
+
+## License
+
+Syncfusion has no liability for any damage or consequence that may arise from using or viewing the samples. The samples are for demonstrative purposes. If you choose to use or access the samples, you agree to not hold Syncfusion liable, in any form, for any damage related to use, for accessing, or viewing the samples. By accessing, viewing, or seeing the samples, you acknowledge and agree Syncfusion’s samples will not allow you seek injunctive relief in any form for any claim related to the sample. If you do not agree to this, do not view, access, utilize, or otherwise do anything with Syncfusion’s samples.