Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 10 additions & 10 deletions aspnet-core/DropDownList/Functionalities.md
Original file line number Diff line number Diff line change
@@ -1,14 +1,14 @@
---
layout: post
title: Functionalities in the DropDownList control for Syncfusion ASP.NET Core
description: Functionalities in the DropDownList control for Syncfusion ASP.NET Core
title: Functionalities in ASP.NET Core DropDownList Control | Syncfusion
description: Learn here all about Functionalities support in Syncfusion Essential ASP.NET Core DropDownList control, its elements, and more.
platform: aspnet-core
control: DropDownList
documentation: ug
keywords: DropDownList, dropdown, Selection, Grouping, Sorting

---
# Functionalities
# Functionalities in ASP.NET Core DropDownList

## Selection

Expand Down Expand Up @@ -197,7 +197,7 @@ To select an item initially you can pass the item’s value via Value property o

{% endtabs %}

![](Functionalities_images/Functionalities_img1.png)
![ASP.NET Core DropDownList using value or text](Functionalities_images/Functionalities_img1.png)

### Using indices

Expand Down Expand Up @@ -234,7 +234,7 @@ You can select a single or more than one item by passing index values to the pro

{% endtabs %}

![](Functionalities_images/Functionalities_img2.png)
![ASP.NET Core DropDownList using indices](Functionalities_images/Functionalities_img2.png)

I> To use "SelectedIndices" property, you should enable either ShowCheckbox or MultiSelectMode property First.

Expand Down Expand Up @@ -376,7 +376,7 @@ The below given example explains the behavior of grouping with List data binding

{% endtabs %}

![](Functionalities_images/Functionalities_img3.png)
![ASP.NET Core DropDownList grouping](Functionalities_images/Functionalities_img3.png)

N> Grouping has restrictions in the following scenarios, <BR>

Expand Down Expand Up @@ -412,7 +412,7 @@ N> Grouping has restrictions in the following scenarios, <BR>

{% endhighlight %}

![](Functionalities_images/Functionalities_img4.png)
![ASP.NET Core DropDownList virtual scrolling](Functionalities_images/Functionalities_img4.png)

I> Virtual scrolling is not supported with Grouping.

Expand Down Expand Up @@ -519,9 +519,9 @@ Configuring the data items for cascading to the series of DropDownList is demons

{% endtabs %}

![](Functionalities_images/Functionalities_img5.png)
![ASP.NET Core DropDownList sorting](Functionalities_images/Functionalities_img5.png)

![](Functionalities_images/Functionalities_img6.jpeg)
![ASP.NET Core DropDownList cascading](Functionalities_images/Functionalities_img6.jpeg)

### Binding the data source to the cascading DropDownList using cascade event

Expand Down Expand Up @@ -596,7 +596,7 @@ Bind the data source to the cascading DropDownList dynamically using ClientSideE

{% endtabs %}

![](Functionalities_images/Functionalities_img7.jpeg)
![ASP.NET Core DropDownList multi level cascading](Functionalities_images/Functionalities_img7.jpeg)

### Multi-Level Cascading

Expand Down
56 changes: 28 additions & 28 deletions aspnet-core/GettingStarted/Getting-Started-1-1-0.md
Original file line number Diff line number Diff line change
@@ -1,14 +1,14 @@
---
layout: post
title: Getting Started | ASP.NET Core | Syncfusion
description: Getting Started.
description: Learn here all about Getting started with Syncfusion Essential ASP.NET Core Application, its elements, and more.
platform: aspnet-core
control: Common
documentation: ug
---


# Getting Started
# Getting Started with ASP.NET Core Application

> Starting with v16.2.0.x, if you reference Syncfusion assemblies from trial setup or from the NuGet feed, you also have to include a license key in your projects. Please refer to this [link](https://help.syncfusion.com/common/essential-studio/licensing/license-key#aspnet-core) to know about registering Syncfusion license key in your ASP.NET Core application to use our components.

Expand All @@ -28,11 +28,11 @@ The following steps helps to create a ASP.NET Core web application to configure

* Open Visual Studio 2015 to create **ASP.NET Core web application**.

![](getting-started_images/getting-started_img1.png)
![Getting Started in ASP.NET Core Application](getting-started_images/getting-started_img1.png)

* After project creation, open your **project.json** file to add our Syncfusion assembly packages.

![](getting-started_images/getting-started_img5.png)
![After Project in ASP.NET Core Application](getting-started_images/getting-started_img5.png)

> The ASP.NET Core NuGet packages versioning has been streamlined as 16.1.0.32 in shorter than older versioning (16.1600.0.32) from Volume 1, 2018 service pack 1 release (16.1.0.32). Since all the framework version wise assemblies are grouped into a single package.

Expand All @@ -41,15 +41,15 @@ The following steps helps to create a ASP.NET Core web application to configure

* In the Solution Explorer window, click the **"Show All Files"** button.

![](getting-started_images/getting-started_img6.jpeg)
![Solution Explorer Window in ASP.NET Core Application](getting-started_images/getting-started_img6.jpeg)

* Open **bower.json** file to include the following necessary packages.

![](getting-started_images/getting-started_img2.png)
![Open Bower json in ASP.NET Core Application](getting-started_images/getting-started_img2.png)

* After Bower packages installation the scripts and CSS files are loaded into the **wwwroot -> lib** folder as shown below

![](getting-started_images/getting-started_img3.png)
![Scripts and CSS in ASP.NET Core Application](getting-started_images/getting-started_img3.png)

* Now open **_viewImports.cshtml** file from the views folder and add the following namespace for components references and Tag Helper support.

Expand Down Expand Up @@ -114,19 +114,19 @@ N> jQuery.easing external dependency has been removed from version 14.3.0.49 onw

* Finally compile your project, after successful compilation then press F5 key to deploy your project.

![](getting-started_images/getting-started_img4.png)
![Compile Project in ASP.NET Core Application](getting-started_images/getting-started_img4.png)

### Configure Syncfusion File Format Components in ASP.NET Core Application:

The following steps helps to create a ASP.NET Core web application to configure our File Format components.

* Open Visual Studio 2015 to create **ASP.NET Core web application**.

![](getting-started_images/getting-started_fileformat_img1.png)
![Open Visual Studion in ASP.NET Core Application](getting-started_images/getting-started_fileformat_img1.png)

* After project creation, open your **project.json** file to add our Syncfusion assembly packages.

![](getting-started_images/getting-started_fileformat_img2.png)
![AFter Project Creation in ASP.NET Core Application](getting-started_images/getting-started_fileformat_img2.png)

N> 1. You can refer [Installation](https://help.syncfusion.com/aspnet-core/configuration-and-installation) procedure to configure Syncfusion NuGet packages.
N> 2. The File format component packages has been modified from Volume 3, 2017 (15.3.0.26) release. You can refer [migration document](https://help.syncfusion.com/aspnet-core/release-notes/migratingtov15.3.0.26) for more details.
Expand Down Expand Up @@ -164,36 +164,36 @@ dotnet new -t web

{% endhighlight %}

![](getting-started_images/getting-started_img10.JPG)
![ASP.NET Core Application web](getting-started_images/getting-started_img10.JPG)


### Configure Syncfusion Components in ASP.NET Core Application

* Open Visual Studio Code and open your ASP.NET folder using **Open -> Folder** menu. Now your project folder is loaded in Visual Studio Code application.

![](getting-started_images/getting-started_img11.JPG)
![Configure Syncfusion Components in ASP.NET Core Application](getting-started_images/getting-started_img11.JPG)


* Open your **bower.json** json file and specify our Syncfusion package will loads our scripts and CSS. Refer this [link](https://help.syncfusion.com/js/installation-and-deployment#configuring-syncfusion-bower-packages) to configure the bower execution environment in your local machine. Then install a bower extension in your Visual Studio code to complete a configuration.

![](getting-started_images/getting-started_img12.JPG)
![Loads File in ASP.NET Core Application](getting-started_images/getting-started_img12.JPG)


* In **bower.json** file specify our Syncfusion packages with our latest version.

![](getting-started_images/getting-started_img13.JPG)
![Specify File in ASP.NET Core Application](getting-started_images/getting-started_img13.JPG)


* Open quick window (Ctrl + p) to run the `bower install` command to install our scripts and CSS to your application **wwwroot -> lib** folder.

![](getting-started_images/getting-started_img14.JPG)
![Folder in ASP.NET Core Application](getting-started_images/getting-started_img14.JPG)


> Recommended to install the “**Bower package watcher**” extension will helps to load the packages whenever save the **bower.json** file.

* Now open your **project.json** file to specify our assembly packages.

![](getting-started_images/getting-started_img15.JPG)
![Bower Package Watcher in ASP.NET Core Application](getting-started_images/getting-started_img15.JPG)

> The ASP.NET Core NuGet packages versioning has been streamlined as 16.1.0.32 in shorter than older versioning (16.1600.0.32) from Volume 1, 2018 service pack 1 release (16.1.0.32). Since all the framework version wise assemblies are grouped into a single package.

Expand All @@ -216,7 +216,7 @@ dotnet restore

{% endhighlight %}

![](getting-started_images/getting-started_img16.JPG)
![Restore Packages in ASP.NET Core Application](getting-started_images/getting-started_img16.JPG)


* Now refer the necessary scripts and CSS files in your **_layout.cshtml** page.
Expand Down Expand Up @@ -274,7 +274,7 @@ N> jQuery.easing external dependency has been removed from version 14.3.0.49 onw

* Finally press F5 key to deploy your project.

![](getting-started_images/getting-started_img17.JPG)
![Press F5 Key in ASP.NET Core Application](getting-started_images/getting-started_img17.JPG)


## ASP.NET Core 1.1.0 Application Using Yeoman with Visual Studio Code:
Expand Down Expand Up @@ -313,46 +313,46 @@ npm install -g yo

{% endhighlight %}

![](getting-started_images/getting-started_img7.JPG)
![Yeoman Generator in ASP.NET Core Application](getting-started_images/getting-started_img7.JPG)


* From the list of available projects, select the **Web Application Basic [ without Membership and Authorization ]** by using arrow keys.

![](getting-started_images/getting-started_img8.JPG)
![Web Application Basic in ASP.NET Core Application](getting-started_images/getting-started_img8.JPG)


* And then provide the project name or simply press the enter key to create the project with default name.

![](getting-started_images/getting-started_img9.JPG)
![Project Name in ASP.NET Core Application](getting-started_images/getting-started_img9.JPG)


### Configure Syncfusion Components in ASP.NET Core Application

* Open Visual Studio Code and open your ASP.NET folder using **Open -> Folder** menu. Now your project folder is loaded in Visual Studio Code application.

![](getting-started_images/getting-started_img11.JPG)
![Open Folder in ASP.NET Core Application](getting-started_images/getting-started_img11.JPG)


* Now configure a Bower execution environment in your local machine based on this [link](https://help.syncfusion.com/js/installation-and-deployment#configuring-syncfusion-bower-packages). Then install a Bower extension in your Visual Studio code to complete a configuration.

![](getting-started_images/getting-started_img12.JPG)
![Configure Bower in ASP.NET Core Application](getting-started_images/getting-started_img12.JPG)


* In **bower.json** file specify our Syncfusion packages with our latest version will loads our scripts and CSS.

![](getting-started_images/getting-started_img13.JPG)
![Bower json in ASP.NET Core Application](getting-started_images/getting-started_img13.JPG)


* Open quick window (Ctrl + p) to run the `bower install` command to install our scripts and CSS to your application **wwwroot -> lib** folder.

![](getting-started_images/getting-started_img14.JPG)
![Bower Installed in ASP.NET Core Application](getting-started_images/getting-started_img14.JPG)


> Recommended to install the “**Bower package watcher**” extension will helps to load the packages whenever save the **bower.json** file.

* Now open your **project.json** file to specify our assembly packages.

![](getting-started_images/getting-started_img15.JPG)
![ASP.NET Core Application file](getting-started_images/getting-started_img15.JPG)

> The ASP.NET Core NuGet packages versioning has been streamlined as 16.1.0.32 in shorter than older versioning (16.1600.0.32) from Volume 1, 2018 service pack 1 release (16.1.0.32). Since all the framework version wise assemblies are grouped into a single package.

Expand All @@ -376,7 +376,7 @@ dotnet restore

{% endhighlight %}

![](getting-started_images/getting-started_img16.JPG)
![Open Command in ASP.NET Core Application](getting-started_images/getting-started_img16.JPG)


* Now refer the necessary scripts and CSS files in your **_layout.cshtml** page.
Expand Down Expand Up @@ -434,4 +434,4 @@ N> jQuery.easing external dependency has been removed from version 14.3.0.49 onw

* Finally press F5 key to deploy your project.

![](getting-started_images/getting-started_img17.JPG)
![Deploy Project in ASP.NET Core Application](getting-started_images/getting-started_img17.JPG)