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/ASPNET-Extension/Project-Conversion.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,18 +24,18 @@ The following steps will assist you to use the Syncfusion® Project conversion i
24
24
**Option 1**
25
25
Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Web Forms (EJ1) > Convert to Syncfusion® ASP.NET Application…** in **Visual Studio**.
26
26
27
-
27
+
28
28
29
29
N> In Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu.
30
30
31
31
**Option 2**
32
32
Right-click the Project from Solution Explorer, select **Syncfusion® Web (Essential® JS 1)**, and choose the **Convert to Syncfusion® ASP.NET (Essential® JS 1) Application...** Refer to the following screenshot for more information.
33
33
34
-
34
+
35
35
36
36
3. The Project Conversion Wizard appears, allowing you to configure the project.
37
37
38
-
38
+
39
39
40
40
The following configurations are used in the Project Conversion wizard:
41
41
@@ -49,7 +49,7 @@ The following steps will assist you to use the Syncfusion® Project conversion i
49
49
50
50
**Choose CDN Support:** The project's master page will be updated based on the required Syncfusion® CDN links.
51
51
52
-
52
+
53
53
54
54
**Copy Global Resources:** If you select the Copy Global Resources option, the Syncfusion® localization culture files will be shipped to the project from the Installed Location.
55
55
@@ -63,14 +63,14 @@ The following steps will assist you to use the Syncfusion® Project conversion i
63
63
64
64
4. When you click the **Convert** button, the **Project Backup** dialog will appear. If you click **Yes** in the dialog, it will backup the current project before converting it to a Syncfusion® project. If you choose **No**, the project will be converted to a Syncfusion® project without a backup.
65
65
66
-
66
+
67
67
68
68
5. The necessary Syncfusion® Assembly references, Scripts, and CSS, as well as the necessary Web.config entries, have been added to the project.
69
69
70
-
70
+
71
71
72
-
72
+
73
73
74
-
74
+
75
75
76
76
6. If you installed the trial setup or NuGet packages from nuget.org you must register the Syncfusion® license key to your project 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/license-key#how-to-generate-syncfusion-license-key) to generate and register the Syncfusion® license key to your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx?_ga=2.11237684.1233358434.1587355730-230058891.1567654773) post for understanding the licensing changes introduced in Essential Studio®.
Copy file name to clipboardExpand all lines: Extension/ASPNET-Extension/Project-Migration.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,18 +22,18 @@ To migrate you’re existing Syncfusion® ASP.NET application, follow the steps
22
22
**Option 1**
23
23
Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Web Forms (EJ1) > Migrate Project…** in **Visual Studio**.
24
24
25
-
25
+
26
26
27
27
N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu.
28
28
29
29
**Option 2**
30
30
Right-click the **Syncfusion® ASP.NET Application** from Solution Explorer and select **Syncfusion® Web (Essential® JS 1)**. Choose **Migrate the Essential® JS 1 Project to Another version…**
31
31
32
-
32
+
33
33
34
34
2. The **Project Migration** window appears. You can choose the required Essential Studio® version that is installed in the machine.
35
35
36
-
36
+
37
37
38
38
3. The **Project Migration** window allows you to configure the following options:
39
39
@@ -45,7 +45,7 @@ To migrate you’re existing Syncfusion® ASP.NET application, follow the steps
45
45
46
46
4. Click the **Migrate** Button. The **Project Backup** dialogue box appears. If you select **Yes** in the dialog, it will backup the current project before migrating the Syncfusion® project. If you select **No**, the project will be migrated to the required Syncfusion® version without a backup.
47
47
48
-
48
+
49
49
50
50
51
51
5. The Syncfusion® Reference Assemblies, Scripts, and CSS, Web. Config entries in the project are updated to the corresponding version.
Copy file name to clipboardExpand all lines: Extension/ASPNET-Extension/Sample-Creator.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,26 +18,26 @@ To create the Syncfusion® ASP.NET (Essential® JS 1) Application using the Samp
18
18
**Option 1:**
19
19
Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Web Forms (EJ1) > Launch Sample Creator…** in **Visual Studio**.
20
20
21
-
21
+
22
22
23
23
N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu.
24
24
25
25
**Option 2:**
26
26
Launch the Syncfusion® ASP.NET (Essential® JS 1) Control Panel. To run the ASP.NET (Essential® JS 1) Sample Creator, click the Sample Creator button. More information can be found in the screenshot below.
27
27
28
-
28
+
29
29
30
-
2. The Syncfusion® components and their features are listed in the ASP.NET (Essential® JS 1) Sample Creator.
30
+
2. The Syncfusion® components and their features are listed in the ASP.NET (Essential JS 1) Sample Creator.
31
31
32
-
32
+
33
33
34
34
**Components Selection:** Choose the required components. The components are grouped with Syncfusion® products, and the components are grouped by product.
35
35
36
-
36
+
37
37
38
38
**Feature Selection:** Based on the components, the feature is enabled to choose the features of the corresponding components.
39
39
40
-
40
+
41
41
42
42
**Project Configuration**
43
43
@@ -55,29 +55,29 @@ To create the Syncfusion® ASP.NET (Essential® JS 1) Application using the Samp
55
55
56
56
***Theme Selection:** Choose the required theme. This section shows the controls preview before creating the Syncfusion® project.
57
57
58
-
58
+
59
59
60
60
2. Click the **Create** button. After you've finished creating the project, open it by clicking **Yes**. If you click **No**, the project's corresponding location will be opened. For more information, see the screenshot below.
61
61
62
-
62
+
63
63
64
64
3. The new Syncfusion® ASP.NET (Essential® JS 1) project is created with the resources.
65
65
66
66
* Added the required Controllers and View files in the project.
67
67
68
-
68
+
69
69
70
70
* Under Project Reference, the necessary Syncfusion® assemblies are added for selected components.
71
71
72
-
72
+
73
73
74
74
* Syncfusion® ASP.NET (Essential® JS 1) scripts and theme files were included.
75
75
76
-
76
+
77
77
78
78
* Configure the Web.Config file by adding the Syncfusion® reference assemblies, namespaces and controls.
79
79
80
-
80
+
Copy file name to clipboardExpand all lines: Extension/ASPNET-Extension/Syncfusion-Project-Templates.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,22 +22,22 @@ To create the **Syncfusion® ASP.NET (Essential® JS 1) Application** using the
22
22
**Option 1**
23
23
Click **Syncfusion® Menu** and choose **Essential Studio® for ASP.NET Web Forms (EJ1) > Create New Syncfusion® ASPNET Web Forms Project…** in **Visual Studio**.
24
24
25
-
25
+
26
26
27
27
N> From Visual Studio 2019, Syncfusion® menu is available under Extensions in Visual Studio menu.
28
28
29
29
**Option 2**
30
30
Choose **File > New > Project** and navigate to **Syncfusion > Web > Syncfusion® ASP.NET Web Forms Application** in **Visual Studio**.
31
31
32
-
32
+
33
33
34
34
2. Name the **project**, select the destination location, and configure the project's .NET Framework, then click **OK**. The Project Configuration Wizard is displayed.
35
35
36
36
N> The minimum target framework for Syncfusion® ASP.NET Project Templates is 3.5.
37
37
38
38
3. Using the following Project Configuration window, select the options to configure the Syncfusion® ASP.NET Web Forms Application.
39
39
40
-
40
+
41
41
42
42
**Project Configurations**
43
43
@@ -59,30 +59,30 @@ To create the **Syncfusion® ASP.NET (Essential® JS 1) Application** using the
59
59
60
60
**Assets From:** Choose the Syncfusion® Essential® JS assets to be added to the ASP.NET Web Forms Project from the NuGet, CDN, or Installed Location.
61
61
62
-
62
+
63
63
64
64
**Installed Version** Choose the version of the project that needs to be created.
65
65
66
66
67
67
68
68
4. Select the components, Assemblies, and Scripts that should be added to the project, and then click the Create button. The Syncfusion® ASP.NET Web Forms project will be created.
69
69
70
-
70
+
71
71
72
-
72
+
73
73
74
74
5. The necessary Syncfusion® Assembly references, Scripts, and CSS, as well as the necessary Web.config entries, have been added to the project.
75
75
76
-
76
+
77
77
78
-
78
+
79
79
80
-
80
+
81
81
82
82
83
83
6.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/license-key#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://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio®.
84
84
85
-
85
+
0 commit comments