You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Extension/WPF-Extension/Template-Studio.md
+27-29Lines changed: 27 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,9 +53,9 @@ Create the Syncfusion WPF project using the Visual Studio Project Template by fo
53
53
54
54
55
55
**Predefined template:** Choose this option to select from 5 predefined templates, including Calendar, Contact, Outlook, Docking Manager, Spreadsheet, Tile view, and Word. By choosing one of these templates, you can create your application without needing to follow any further steps.
**Project type:** Choose this option to select from 4 project types, including Navigation Pane, Blank, Menu Bar, and Ribbon .
60
60
61
61
6. Click **Next** or navigate to the **Pages** tab to access a list of available Syncfusion WPF components you can add to the application.
@@ -88,48 +88,46 @@ In the **Project Details** section, you can modify configurations and project ty
88
88
89
89
To find out which NuGet packages are needed for other WPF controls, please refer to this [documentation link](https://help.syncfusion.com/wpf/control-dependencies) for detailed information on the required NuGet packages for each control.
90
90
91
-
10. When you create a WPF project, the following Dependency Injection (DI) setup is added to the `App.xaml.cs` file. This setup registers services, view models, and views with the DI container, ensuring proper functionality for the selected components and service management within your application. Below, the `ConfigureServices` method in `App.xaml.cs` sets up Dependency Injection (DI) in a WPF project to manage the application's services, view models, and views. Here's a simple breakdown:
10. When you create a WPF project, the following Dependency Injection (DI) setup is added to the **App.xaml.cs** file. This setup registers services, view models, and views with the DI container, ensuring proper functionality for the selected components and service management within your application. Below, the **ConfigureServices** method in **App.xaml.cs**`** sets up Dependency Injection (DI) in a WPF project to manage the application's services, view models, and views. Here's a simple breakdown:
92
+
94
93
94
+
*I. Application Host:*
95
+
- Registers **ApplicationHostService** to manage the app's lifecycle.
95
96
96
-
I. Application Host:
97
-
- Registers `ApplicationHostService` to manage the app's lifecycle.
97
+
*II. Specific Services:*
98
+
- Registers **PageService** and **NavigationService** for handling page navigation.
98
99
99
-
II. Specific Services:
100
-
- Registers `PageService` and `NavigationService` for handling page navigation.
101
-
102
-
III. Views and ViewModels:
100
+
*III. Views and ViewModels:*
103
101
- Registers ShellWindow and ShellViewModel for the main application window.
104
-
- Registers `DataGridViewModel` and `DataGridPage` for the added component DataGrid UI.
102
+
- Registers **DataGridViewModel** and **DataGridPage** for the added component DataGrid UI.
105
103
- Registers MainViewModel and MainPage for the main page of the app.
106
104
107
-
IV. Configuration:
108
-
- Binds the app's configuration settings to the `AppConfig` class using the settings from the configuration file.
105
+
*IV. Configuration:*
106
+
- Binds the app's configuration settings to the **AppConfig** class using the settings from the configuration file.
11. In a WPF MVVM application, the `PageService.cs` class helps manage navigation and page creation. For instance, it facilitates registering and navigating to pages associated with specific view models. Here's a simple explanation:
110
+
11. In a WPF MVVM application, the **PageService.cs** class helps manage navigation and page creation. For instance, it facilitates registering and navigating to pages associated with specific view models. Here's a simple explanation:
111
111
112
-
I. Initialization:
112
+
*I. Initialization:*
113
113
- The constructor of PageService takes a serviceProvider to access registered services.
114
114
115
-
II. Registering Pages:
116
-
-Configure `<DataGridViewModel, DataGridPage>();` links the DataGridViewModel to the DataGridPage.
117
-
- Configure `<MainViewModel, MainPage>();` links the MainViewModel to the MainPage.
115
+
*II. Registering Pages:*
116
+
-**Configure `<DataGridPage>()`:** Registers DataGridPage with the service provider.
117
+
-**Configure `<MainPage>()`:** Registers MainPage with the service provider.
12. Some components require additional resource files, such as images and other necessary files, to function correctly. For example, if you add the `PDFViewer` and `Carousel` component to your WPF project, the respective images and PDF files will be added to the Images and Assets folder in your project.
121
+
12. Some components require additional resource files, such as images and other necessary files, to function correctly. For example, if you add the **PDFViewer** and **Carousel** component to your WPF project, the respective images and PDF files will be added to the Images and Assets folder in your project.
N> The .Net 6.0, .Net 7.0, and .Net 8.0 option will be listed in Select a framework version when only the .Net 6.0, .Net 7.0, and .Net 8.0 SDK setup has been installed.
126
-
127
-
> | .NET Version | Available From Version | Supported from Visual Studio |
13. Then, Syncfusion licensing registration required message box will be shown if you installed the trial setup or NuGet packages since Syncfusion introduced the licensing system from 2018 Volume 2 (v16.2.0.41) Essential Studio release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion license key to your project. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio.
Copy file name to clipboardExpand all lines: Extension/WindowsForms-Extension/Template-Studio.md
+17-19Lines changed: 17 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,47 +91,45 @@ Create the Syncfusion WinForms project using the Visual Studio Project Template
91
91
To find out which NuGet packages are needed for other WinForms controls, please refer to this [documentation link](https://help.syncfusion.com/windowsforms/control-dependencies) for detailed information on the required packages for each control.
92
92
93
93
10. When you create a WinForms project, the following Dependency Injection (DI) setup is added to the **Program.cs** file. This setup registers services, view models, and views with the DI container, ensuring proper functionality and service management within your application. Below **ConfigureServices** method in program.cs file establishes the DI setup in a WinForms project. It manages the application's services, view models, and views. Here's a detailed breakdown:
94
-
95
-
96
-
97
-
I. Application Host:
94
+
95
+
*I. Application Host:*
98
96
- Registers **ApplicationHostService** to manage the app's lifecycle.
99
97
100
-
II. Specific Services:
98
+
*II. Specific Services:*
101
99
- Registers **PageService** and **NavigationService** for handling page navigation.
102
100
103
-
III. Views and ViewModels:
101
+
*III. Views and ViewModels:*
104
102
-**ShellWindow:** Registers the main application window.
105
103
-**DataGridPage:** Registers the added component DataGrid on UI.
106
104
-**MainPage:** Registers the main page of the application.
107
105
108
-
IV. Configuration:
106
+
*IV. Configuration:*
109
107
- Binds the app's configuration settings to the **AppConfig** class using the settings from the configuration file.
110
108
109
+
110
+
111
111
11. In a WinForms MVVM application, the **PageService.cs** class is responsible for managing navigation and page creation. It registers view models with their corresponding pages, allowing for seamless navigation within the application.
- The constructor of PageService takes an IServiceProvider to access the registered services. This allows the service to resolve and instantiate the required view models and views.
118
116
119
-
II. Registering Pages:
117
+
*II. Registering Pages:*
120
118
- **Configure `<DataGridPage>()`:** Registers DataGridPage with the service provider.
121
119
- **Configure `<MainPage>()`:** Registers MainPage with the service provider.
12. Some components require additional resource files, such as pdf and other necessary files, to function correctly. For example, if you add the **PDFViewer** and **Diagram** components to your WinForms project, the respective PDF and ico files will be added to the Resources folder in your project.
N> The .NET 6.0, .NET 7.0, and .NET 8.0 option will be listed in Select a framework version when only the .NET 6.0, .NET 7.0, and .NET 8.0 SDK setup has been installed.
129
-
130
-
> | .NET Version | Available From Version | Supported from Visual Studio |
13. If you install the trial setup or NuGet packages from nuget.org, you must register the Syncfusion license key to your application since Syncfusion introduced the licensing system from the 2018 Volume 2 (v16.2.0.41) Essential Studio release. Navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/overview#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion license key to your application. Refer to this [blog](https://www.syncfusion.com/blogs/post/whats-new-in-2018-volume-2.aspx) post for understanding the licensing changes introduced in Essential Studio.
0 commit comments