Skip to content

SEO-2393 - ASP.NET Core image alt text changes #204

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: hotfix/hotfix-v20.2.0.43
Choose a base branch
from
Open

SEO-2393 - ASP.NET Core image alt text changes #204

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
22f04aa
image alt text changes
Sharly-Atieno Aug 22, 2022
6b3180c
with added
Sharly-Atieno Aug 22, 2022
de5624e
image alt text changes
Sharly-Atieno Aug 22, 2022
7e3b995
image alt text changes
Sharly-Atieno Aug 23, 2022
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
7 changes: 4 additions & 3 deletions aspnet-core/EJTagHelpers.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,13 +1,14 @@
---
layout: post
title: EJTagHelpers | ASP.NET Core | Syncfusion
description: EJTagHelpers
description: Learn here all about EJTagHelpers support in Syncfusion Essential ASP.NET Core control, its elements, and more.
platform: js
platform: aspnet-core
control: Common
documentation: ug
---

# TagHelpers
# TagHelpers in Essential ASP.NET Core

Tag Helpers are used to write server-side code in razor view page. It is a feature of Razor view engine which converts the server-side code into HTML and serves it to the web browser. The main advantage of using Tag Helpers over HTML Helpers is that the Razor markup using Tag Helpers looks like standard HTML and it also has rich **intelliSense** with the scope of existing elements. The most important feature of the Tag Helper is that they can be independent from the C# syntax. Tag helper provides more reliable and reusable code that can be created and used across different views, as and when it is needed.

Expand Down Expand Up @@ -45,7 +46,7 @@ Open a view page to render Syncfusion UI components in Tag Helper Syntax. The fo

We can configure the EJ components with its properties by using tag attributes. It also has rich IntelliSense support which displays all the methods and properties of EJ controls on the page model.

![](ej-tag-helpers_images/ej-tag-helper_image.png)
![ASP.NET Core API configuration with tag helpers](ej-tag-helpers_images/ej-tag-helper_image.png)

## Wiring Client Side Events

Expand Down
56 changes: 28 additions & 28 deletions aspnet-core/GettingStarted/Getting-Started-1-1-0.md
View file
Open in desktop
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 control, its elements, and more.
platform: aspnet-core
control: Common
documentation: ug
---


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

> 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)
![ASP.NET Core web 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)
![ASP.NET Core open project.json](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)
![ASP.NET Core show all files](getting-started_images/getting-started_img6.jpeg)

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

![](getting-started_images/getting-started_img2.png)
![ASP.NET Core open bower.json](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)
![ASP.NET Core script and CSS files loaded](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)
![ASP.NET Core press F5 key](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)
![ASP.NET Core configure file format component](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)
![ASP.NET Core add file](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 system requirement](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)
![ASP.NET Core configure components](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)
![ASP.NET Core loads](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)
![ASP.NET Core file specify latest version packages](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)
![ASP.NET Core folder](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 file specify assembly packages](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)
![ASP.NET Core restore packages](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)
![ASP.NET Core application using Yeoman with visual studio code](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)
![ASP.NET Core project creation wizard](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)
![ASP.NET Core select web application basic](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)
![ASP.NET Core provide project name](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)
![ASP.NET Core open visual studio](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)
![ASP.NET Core configure bower execution](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)
![ASP.NET Core specify file packages](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)
![ASP.NET Core run bower](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 install bower package watcher](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)
![ASP.NET Core open command prompt window](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)
![ASP.NET Core add script manager](getting-started_images/getting-started_img17.JPG)
14 changes: 7 additions & 7 deletions aspnet-core/Grid/Getting-Started.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
---
layout: post
title: Getting started with grid widget for Syncfusion Essential ASP.NET Core
description: How to create the grid, data bind, enable paging, grouping, filtering and add summaries
description: Learn here all about getting started with Syncfusion Essential ASP.NET Core control, its elements, and more.
platform: aspnet-core
control: grid
documentation: ug
---

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

Refer to the [Getting Started](https://help.syncfusion.com/aspnet-core/gettingstarted/getting-started-2-0) page of the introduction part to know more about the basic system requirements and the steps to configure the Syncfusion components in an ASP.NET Core application.

Expand Down Expand Up @@ -94,7 +94,7 @@ In `e-columns` definition, the `text-align` property allows you to align text of

The following output is displayed as a result of the previous code example.

![](Getting-Started_images/Getting-Started2_img1.jpeg)
![ASP.NET Core data binding](Getting-Started_images/Getting-Started2_img1.jpeg)


## Enable paging
Expand Down Expand Up @@ -135,7 +135,7 @@ The paging feature in grid offers complete navigation support to easily switch

The following output is displayed as a result of the previous code example.

![](Getting-Started_images/Getting-Started2_img2.png)
![ASP.NET Core enable paging](Getting-Started_images/Getting-Started2_img2.png)


## Enable filtering
Expand Down Expand Up @@ -178,7 +178,7 @@ To enable filtering, use the `allow-filtering` property of grid is as follows.

The following output is displayed as a result of the previous code example.

![](Getting-Started_images/Getting-Started2_img3.png)
![ASP.NET Core enable filtering](Getting-Started_images/Getting-Started2_img3.png)


## Enable grouping
Expand Down Expand Up @@ -220,7 +220,7 @@ To enable grouping, use the `allow-grouping` property of grid is as follows.

The following output is displayed as a result of the previous code example.

![](Getting-Started_images/Getting-Started2_img4.png)
![ASP.NET Core enable grouping](Getting-Started_images/Getting-Started2_img4.png)


## Add summaries
Expand Down Expand Up @@ -268,4 +268,4 @@ Summaries can be added by setting the `show-summary` to `true` and adding requir

The following output is displayed as a result of the previous code example.

![](Getting-Started_images/Getting-Started2_img5.png)
![ASP.NET Core add summaries](Getting-Started_images/Getting-Started2_img5.png)