Microsoft Student Partner (MSP) Capacity Build up Training (Session 03)

Microsoft Student Partner (MSP) Capacity Build up Training (Session 03)
Course Title: Object Oriented Programming with C#
Venue: East West University, Dhaka, Bangladesh
Date: 25 June, 2016
Speaker / Trainer: Md. Mahedee Hasan,
Microsoft MVP, Visual Studio and Development Technologies
Software Architect, Leadsoft Bangladesh Limited
Trainer, Leads Technology Limited.

Microsoft Student Partner (MSP) Capacity Build up Training (Session 01)


Microsoft Student Partner (MSP) Capacity Build up Training (Session 01)
Course Title: Object Oriented Programming with C#
Venue: East West University, Dhaka, Bangladesh
Date: 28 May, 2016
Speaker / Trainer: Md. Mahedee Hasan,
Microsoft MVP, Visual Studio and Development Technologies
Software Architect, Leadsoft Bangladesh Limited
Trainer, Leads Technology Limited

CRUD and search operation in ASP.NET MVC application using partial view

What is Partial View in ASP.NET MVC?

  • Partial view is a view which is rendered in another view
  • Partial view render portion of pages
  • Using partial view, you can reuse portion of page
  • Partial view is similar to a normal view with .cshtml


  • Project overview

    Here I create an application to keep basic employee information. View, add, update and delete option of an employee is in the application. I used partial view to show employee information in grid. Here I showed how do you run CRUD operation using partial view in most manageable way.
    Let’s come to the implementation of the project.

    Tools and Technology used
    I used following tools and technology to develop the project –

    1. Visual Studio 2013
    2. Visual C#
    3. ASP.NET MVC 5
    4. Entity Framework 6
    5. Razor view engine
    6. JQuery

    Step 1: Create a ASP.net MVC Project
    From Visual studio 2013, choose File->Project -> ASP.NET Web application as below

    0106_01

    Select MVC Template and click OK

    0106_02


    Step 2: Change or Add Connection String

    Change or Add connection string in Web.config as follows

    
    

    Step 3: Create model classes

    Create three model classes Dept, Designation and Employee as follows.

    Dept Class

    using System;
    using System.Collections.Generic;
    using System.ComponentModel.DataAnnotations;
    using System.ComponentModel.DataAnnotations.Schema;
    
    namespace Web.HRM.Models
    {
        public class Dept
        {
            public Dept()
            {
                ActionDate = DateTime.Now;
            }
    
            [Key, DatabaseGenerated(DatabaseGeneratedOption.Identity)]
            public int Id { get; set; }
    
            [Display(Name = "Dept")]
            public string Name { get; set; }
    
            public virtual List Employees { get; set; }
            public DateTime ActionDate { get; set; }
        }
    }
    
    

    Designation Class

    using System;
    using System.Collections.Generic;
    using System.ComponentModel.DataAnnotations;
    using System.ComponentModel.DataAnnotations.Schema;
    
    namespace Web.HRM.Models
    {
        public class Designation
        {
            public Designation()
            {
                ActionDate = DateTime.Now;
            }
            [Key, DatabaseGenerated(DatabaseGeneratedOption.Identity)]
            public int Id { get; set; }
            [Display(Name = "Designation")]
            public string Name { get; set; }
            public virtual List Employees { get; set; }
            public DateTime ActionDate { get; set; }
    
        }
    }
    

    Employee Class

    using System;
    using System.ComponentModel.DataAnnotations;
    using System.ComponentModel.DataAnnotations.Schema;
    
    namespace Web.HRM.Models
    {
        public class Employee
        {
            public Employee()
            {
                ActionDate = DateTime.Now;
            }
    
            [Key, DatabaseGenerated(DatabaseGeneratedOption.Identity)]
            public int Id { get; set; }
    
            [Display(Name = "Employee Code")]
            public string EmpCode { get; set; }
    
            [Display(Name = "Full Name")]
            public string FullName { get; set; }
    
            [Display(Name = "Nick Name")]
            public string NickName { get; set; }
    
            [Display(Name = "Designation")]
            public int DesignationId { get; set; }
    
            [ForeignKey("DesignationId")]
            public virtual Designation Designation { get; set; }
    
            [Display(Name = "Department")]
            public int DeptId { get; set; }
    
            [ForeignKey("DeptId")]
            public virtual Dept Dept { get; set; }
    
            public string Phone { get; set; }
            public string Email { get; set; }
            public string Address { get; set; }
            public DateTime ActionDate { get; set; }
        }
    }
    
    


    Step 4: Create a Context class

    Create HRMContext Class in Model folder.

    using Microsoft.AspNet.Identity.EntityFramework;
    using System.Data.Entity;
    
    namespace Web.HRM.Models
    {
    
        public class HRMContext : IdentityDbContext
        {
            public HRMContext()
                : base("DefaultConnection", throwIfV1Schema: false)
            {
            }
    
            public static HRMContext Create()
            {
                return new HRMContext();
            }
    
            public DbSet Depts { get; set; }
            public DbSet Designations { get; set; }
            public DbSet Employees { get; set; }
        }
    }
    
    

    Step 5: Create Controller and Views
    Click Right button on Controller Folder->Add Controller. Now choose scaffolding template as follows. Click Add.

    0106_04

    Now select context, model name and type controller name as EmployeeController as follows.

    0106_05

    Step 6: Modify the controller
    Modify EmployeeController as follows.

    using System;
    using System.Collections.Generic;
    using System.Data.Entity;
    using System.Linq;
    using System.Net;
    using System.Web.Mvc;
    using Web.HRM.Models;
    
    namespace Web.HRM.Controllers
    {
        public class EmployeeController : Controller
        {
            private HRMContext db = new HRMContext();
    
            // GET: /Employee/
            public ActionResult Index()
            {
                var employees = db.Employees.Include(e => e.Dept).Include(e => e.Designation);
                return View(employees.ToList());
            }
    
            // GET: /Employee/Details/5
            public ActionResult Details(int? id)
            {
                if (id == null)
                {
                    return new HttpStatusCodeResult(HttpStatusCode.BadRequest);
                }
                Employee employee = db.Employees.Find(id);
                if (employee == null)
                {
                    return HttpNotFound();
                }
                return View(employee);
            }
    
            // GET: /Employee/Create
            public ActionResult Create()
            {
                ViewBag.DeptId = new SelectList(db.Depts, "Id", "Name");
                ViewBag.DesignationId = new SelectList(db.Designations, "Id", "Name");
    
                List lstDept = db.Depts.ToList();
                ViewBag.DeptList = lstDept;
    
                List lstDesignation = db.Designations.ToList();
                ViewBag.DesignationList = lstDesignation;
    
                return View();
            }
    
            // POST: /Employee/Create
            // To protect from overposting attacks, please enable the specific properties you want to bind to, for 
            // more details see http://go.microsoft.com/fwlink/?LinkId=317598.
            [HttpPost]
            [ValidateAntiForgeryToken]
            public ActionResult Create([Bind(Include = "Id,EmpCode,FullName,NickName,DesignationId,DeptId,Phone,Email,Address")] Employee employee)
            {
                if (ModelState.IsValid)
                {
                    employee.ActionDate = DateTime.Now;
                    if (employee.Id != 0)
                        db.Entry(employee).State = EntityState.Modified;
                    else
                        db.Employees.Add(employee);
                    db.SaveChanges();
                    return RedirectToAction("Create");
                }
    
                ViewBag.DeptId = new SelectList(db.Depts, "Id", "Name", employee.DeptId);
                ViewBag.DesignationId = new SelectList(db.Designations, "Id", "Name", employee.DesignationId);
                return View(employee);
            }
    
            // GET: /Employee/Edit/5
            public ActionResult Edit(int? id)
            {
                if (id == null)
                {
                    return new HttpStatusCodeResult(HttpStatusCode.BadRequest);
                }
                Employee employee = db.Employees.Find(id);
                if (employee == null)
                {
                    return HttpNotFound();
                }
                ViewBag.DeptId = new SelectList(db.Depts, "Id", "Name", employee.DeptId);
                ViewBag.DesignationId = new SelectList(db.Designations, "Id", "Name", employee.DesignationId);
                return View(employee);
            }
    
            // POST: /Employee/Edit/5
            // To protect from overposting attacks, please enable the specific properties you want to bind to, for 
            // more details see http://go.microsoft.com/fwlink/?LinkId=317598.
            [HttpPost]
            [ValidateAntiForgeryToken]
            public ActionResult Edit([Bind(Include = "Id,EmpCode,FullName,NickName,DesignationId,DeptId,Phone,Email,Address,ActionDate")] Employee employee)
            {
                if (ModelState.IsValid)
                {
                    db.Entry(employee).State = EntityState.Modified;
                    db.SaveChanges();
                    return RedirectToAction("Index");
                }
                ViewBag.DeptId = new SelectList(db.Depts, "Id", "Name", employee.DeptId);
                ViewBag.DesignationId = new SelectList(db.Designations, "Id", "Name", employee.DesignationId);
                return View(employee);
            }
    
            // GET: /Employee/Delete/5
            public ActionResult Delete(int? id)
            {
                if (id == null)
                {
                    return new HttpStatusCodeResult(HttpStatusCode.BadRequest);
                }
                Employee employee = db.Employees.Find(id);
                if (employee == null)
                {
                    return HttpNotFound();
                }
    
                return View(employee);
            }
    
            // POST: /Employee/Delete/5
            [HttpPost, ActionName("Delete")]
            [ValidateAntiForgeryToken]
            public ActionResult DeleteConfirmed(int id)
            {
                Employee employee = db.Employees.Find(id);
                db.Employees.Remove(employee);
                db.SaveChanges();
                return RedirectToAction("Create");
                //return RedirectToAction("Index");
            }
    
    
            public ActionResult _LoadSearchEmployee(string desigId, string deptId)
            {
                List employee = new List();
                int _desigId = 0;
                int _deptId = 0;
                Int32.TryParse(desigId, out _desigId);
                Int32.TryParse(deptId, out _deptId);
    
                employee = db.Employees.Where(p => (p.DeptId == _deptId || _deptId == 0) &&
                    (p.DesignationId == _desigId || _desigId == 0)).ToList();
                return PartialView(employee);
            }
            protected override void Dispose(bool disposing)
            {
                if (disposing)
                {
                    db.Dispose();
                }
                base.Dispose(disposing);
            }
        }
    }
    

    Step 7: Create a partial view
    Create a partial view name _LoadSearchEmployee in Employee Controller. Click right button on _LoadSearchEmployee action -> Add View -> Select “Create as a partial view” as follows.

    0106_06

    Modify the partial view “_LoadSearchEmployee” in Views-> Employee folder as follows.

    @model IEnumerable
    
        @{
            ViewBag.Title = "View1";
        }
    
        

    List of Employees

    @*

    @Html.ActionLink("Create New", "Create")

    *@ @foreach (var item in Model) { }
    @Html.DisplayNameFor(model => model.EmpCode) @Html.DisplayNameFor(model => model.FullName) @Html.DisplayNameFor(model => model.NickName) @Html.DisplayNameFor(model => model.Designation.Name) @Html.DisplayNameFor(model => model.Dept.Name) @Html.DisplayNameFor(model => model.Phone) @Html.DisplayNameFor(model => model.Email)
    @Html.DisplayFor(modelItem => item.EmpCode) @Html.DisplayFor(modelItem => item.FullName) @Html.DisplayFor(modelItem => item.NickName) @Html.DisplayFor(modelItem => item.Designation.Name) @Html.DisplayFor(modelItem => item.Dept.Name) @Html.DisplayFor(modelItem => item.Phone) @Html.DisplayFor(modelItem => item.Email) | @Html.ActionLink("Details", "Details", new { id = item.Id }) | @Html.ActionLink("Delete", "Delete", new { id = item.Id })

    Step 8: Create a View
    Right click on Create action -> Add View as follows.

    0106_07

    Modify the “Create” View and javascript bottom of the view in View->Employee folder as follows.

    
    @model Web.HRM.Models.Employee
    
    @{
        ViewBag.Title = "Create";
    
        var lstDept = ViewBag.DeptList;
        var lstDesignation = ViewBag.DesignationList;
    
    }
    
    @*

    Create

    *@ @using (Html.BeginForm()) { @Html.AntiForgeryToken()

    Employee Information


    @Html.ValidationSummary(true) @*@Html.HiddenFor(model => model.Id)*@
    @Html.LabelFor(model => model.EmpCode, new { @style = "width : 150px", @class = "control-label col-md-2" }) @Html.EditorFor(model => model.EmpCode) @Html.ValidationMessageFor(model => model.EmpCode) @Html.LabelFor(model => model.FullName, new { @style = "width : 150px", @class = "control-label col-md-2" }) @Html.EditorFor(model => model.FullName) @Html.ValidationMessageFor(model => model.FullName)
    @Html.LabelFor(model => model.NickName, new { @style = "width : 150px", @class = "control-label col-md-2" }) @Html.EditorFor(model => model.NickName) @Html.ValidationMessageFor(model => model.NickName) @Html.LabelFor(model => model.DesignationId, "Designation", new { @style = "width : 150px", @class = "control-label col-md-2" }) @Html.DropDownList("DesignationId", "---Select Dept---") @Html.ValidationMessageFor(model => model.DesignationId)
    @Html.LabelFor(model => model.DeptId, "Dept", new { @style = "width : 150px", @class = "control-label col-md-2" }) @Html.DropDownList("DeptId", "---Select Dept---") @Html.ValidationMessageFor(model => model.DeptId) @Html.LabelFor(model => model.Phone, new { @style = "width : 150px", @class = "control-label col-md-2" }) @Html.EditorFor(model => model.Phone) @Html.ValidationMessageFor(model => model.Phone)
    @Html.LabelFor(model => model.Email, new { @style = "width : 150px", @class = "control-label col-md-2" }) @Html.EditorFor(model => model.Email) @Html.ValidationMessageFor(model => model.Email) @Html.LabelFor(model => model.Address, new { @style = "width : 150px", @class = "control-label col-md-2" }) @Html.EditorFor(model => model.Address) @Html.ValidationMessageFor(model => model.Address)
    || @Html.ActionLink("Clear", "Create", "Employee", null, new { @class = "btn btn-primary" }) @*@Html.ActionLink("Back to List", "Index")*@

    @Html.Label("Dept: ", new { @style = "width : 150px", @class = "control-label col-md-2" }) @Html.DropDownList("DeptSearch", new SelectList(lstDept, "Id", "Name"), "---Select Dept---", new { @style = "width : 200px", @class = "form-control" }) @Html.Label("Designation: ", new { @class = "control-label col-md-2" }) @Html.DropDownList("DesigSearch", new SelectList(lstDesignation, "Id", "Name"), "---Select Designation---", new { @style = "width : 200px", @class = "form-control" })
    } @*
    @Html.ActionLink("Back to List", "Index")
    *@


    @{ Html.RenderAction("_LoadSearchEmployee", new { desigId = "", deptId = "" }); }
    @section Scripts { @Scripts.Render("~/bundles/jqueryval") }

    Step 9: Modify the RouteConfig
    Modify route configuration in App_Start in RouteConfig.cs is as follows. Main reason to modify this class to run the create page by default.

     
    using System.Web.Mvc;
    using System.Web.Routing;
    
    namespace Web.HRM
    {
        public class RouteConfig
        {
            public static void RegisterRoutes(RouteCollection routes)
            {
                routes.IgnoreRoute("{resource}.axd/{*pathInfo}");
    
                routes.MapRoute(
                    name: "Default",
                    url: "{controller}/{action}/{id}",
                    defaults: new { controller = "Employee", action = "Create", id = UrlParameter.Optional }
                );
            }
        }
    }
    

    Now run the application, you will see the following output. You can add, view, update and delete employee information in a same page. Thanks for your patience.

    0106_08

    Cascading Dropdown List in ASP.Net MVC a sample demonstration

    Last couple of weeks I found a good number of requests from my trainees and some .NET developers. They request me for sample code or a demonstration of cascading dropdown list in ASP.NET MVC. That’s why, I am writing this article. Cascading dropdown list is actually a parent child dropdown list. In this article I showed two dropdown lists one is category dropdown list and other is product dropdown list. Product dropdown list will be populated on the basis of category (selected category).

    Let’s implement cascading dropdown list in ASP.NET MVC

    Tools and Technology used
    I used following tools and technology to develop the project –

    1. Visual Studio 2013
    2. Visual C#
    3. ASP.NET MVC 5
    4. Entity Framework 6
    5. JQuery Ajax

    Step 1: Create a ASP.NET MVC Project
    Open visual studio and then go
    File -> Project -> ASP.NET Web Application
    Create an ASP.NET MVC project

    Step 2: Install Json.NET
    Click right button on Project -> NuGet Packages

    2015-12-04-01

    • Select and install Json.NET

    2015-12-04-02

    Keep note that in this moment, your internet connection must on.

    Step 3: Create a local database
    Click right button on App_Data folder -> Select Add -> SQL Server Database.

    2015-12-04-03

    Type Item name as InventoryDB. You can choose any type you want. You will see Inventory.mdf file is created in App_Data folder

    Step 4: Modify connection string.
    Modify connection string as below because you are using localdb.

    
      
        
      
    
    

    Step 5: Create a model for the application.

    Create a model name Category in model folder

        public class Category
        {
            public int Id { get; set; }
            public string Name { get; set; }
            public List Products { get; set; }
        }
    

    Create a model name Product in model folder

        public class Product
        {
            public int Id { get; set; }
            public string Name { get; set; }
    
            public int CategoryId { get; set; }
    
            [ForeignKey("CategoryId")]
            public virtual Category Category { get; set; }
        }
    

    Create a model name Item in model folder

        public class Item
        {
            public int Id { get; set; }
            public string Name { get; set; }
    
            [Display(Name = "Category")]
            public int CategoryId { get; set; }
            [ForeignKey("CategoryId")]
            public virtual Category Category { get; set; }
    
            [Display(Name = "Products")]
            public int ProductId { get; set; }
            [ForeignKey("ProductId")]
            public Product Product { get; set; }
        }
    
    

    Step 6: Create Context Class
    Create a context class in model folder name InventoryDBContext as follows

        public class InventoryDBContext : DbContext
        {
            public InventoryDBContext()
                : base("DefaultConnection")
            {
    
            }
    
            public DbSet Categories { get; set; }
            public DbSet Products { get; set; }
            public DbSet Items { get; set; }
        }
    
    

    Step 7: Enable Migration

    Go to Tools-> NuGet Package Manager -> Package Manger Console
    Type the following command in package manager console to enable migration
    PM> Enable-Migrations -ContextTypeName InventoryDBContext

    After pressing enter you will see a class name Configuration is created in Migrations folder with some codes.
    Now add seed data in Seed method of Configuration class in Migrations folder as follows.

        internal sealed class Configuration : DbMigrationsConfiguration
        {
            public Configuration()
            {
                AutomaticMigrationsEnabled = false;
            }
    
            protected override void Seed(Web.Mahedee.net.Models.InventoryDBContext context)
            {
                context.Categories.AddOrUpdate(
                    p => p.Name,
                    new Category
                    {
                        Name = "Electronics",
                        Products = new List { 
                            new Product{Name = "Mobile"},
                            new Product{Name = "Laptop"},
                            new Product{Name = "Television"},
                            new Product{Name = "Camera"}
                        }
    
                    },
    
                    new Category
                    {
                        Name = "Men ware",
                        Products = new List 
                        { 
                            new Product{Name = "Footware"},
                            new Product{Name = "Clothings"},
                            new Product{Name = "Watches"},
                            new Product{Name = "Hand bag"},
                            new Product{Name = "Sun Glass"}
                        }
                    },
    
                    new Category
                    {
                        Name = "Baby & Kids",
                        Products = new List 
                        { 
                            new Product{Name = "Baby footware"},
                            new Product{Name = "Kids clothigs"},
                            new Product{Name = "Baby care"}
                        }
                    },
    
                     new Category
                    {
                        Name = "Books",
                        Products = new List 
                        { 
                            new Product{Name = "Introduction to C#"},
                            new Product{Name = "ASP.NET MVC Begineer to Professional"},
                            new Product{Name = "ASP.NET Web API Security"},
                            new Product{Name = "SPA with ASP.NET MVC"}
                        }
                    }
    
                    );
            }
        }
    

    Step 8: Add Migration and Update database
    In package manager console write the following command to add a migration.

    PM> add-migration firstmigration

    A file will be created in Migrations folder something like below.
    File Name: 201512041037292_firstmigration

    Update the file, in AddForeignKey section and set false for cascadeDelete as follows.

       public partial class firstmigration : DbMigration
        {
            public override void Up()
            {
                DropForeignKey("dbo.Categories", "Item_Id", "dbo.Items");
                DropForeignKey("dbo.Products", "Item_Id", "dbo.Items");
                DropIndex("dbo.Categories", new[] { "Item_Id" });
                DropIndex("dbo.Products", new[] { "Item_Id" });
                CreateIndex("dbo.Items", "CategoryId");
                CreateIndex("dbo.Items", "ProductId");
    
                AddForeignKey("dbo.Items", "CategoryId", "dbo.Categories", "Id", cascadeDelete: false);
                AddForeignKey("dbo.Items", "ProductId", "dbo.Products", "Id", cascadeDelete: false);
    
                DropColumn("dbo.Categories", "Item_Id");
                DropColumn("dbo.Products", "Item_Id");
            }
            
            public override void Down()
            {
                AddColumn("dbo.Products", "Item_Id", c => c.Int());
                AddColumn("dbo.Categories", "Item_Id", c => c.Int());
                DropForeignKey("dbo.Items", "ProductId", "dbo.Products");
                DropForeignKey("dbo.Items", "CategoryId", "dbo.Categories");
                DropIndex("dbo.Items", new[] { "ProductId" });
                DropIndex("dbo.Items", new[] { "CategoryId" });
                CreateIndex("dbo.Products", "Item_Id");
                CreateIndex("dbo.Categories", "Item_Id");
                AddForeignKey("dbo.Products", "Item_Id", "dbo.Items", "Id");
                AddForeignKey("dbo.Categories", "Item_Id", "dbo.Items", "Id");
            }
        }
    

    Write the following command in package manager console to update database.
    PM> update-database –Verbose

    Step 9: Add Items Controller

    • Right click on Controllers folder -> Add -> Controller
    • Select MVC 5 Controller with views using Entity Framework and the click Add

    2015-12-04-04

    • Select Item as Model class and InventoryDBContext as context class and click Add button as follows

    2015-12-04-05

    ItemsController and Views will be created automatically.

    Step 10: Update Items controller

    • Modify the following action of Items controller
            public ActionResult Create()
            {
                List lstCategory = db.Categories.ToList();
                lstCategory.Insert(0, new Category { Id = 0, Name = "--Select Category--" });
    
                List lstProduct = new List();
                ViewBag.CategoryId = new SelectList(lstCategory, "Id", "Name");
                ViewBag.ProductId = new SelectList(lstProduct, "Id", "Name");
                return View();
            }
    
    
    • Add the following action in the Items controller
            public JsonResult GetProductsByCategoryId(int id)
            {
                List products = new List();
                if (id > 0)
                {
                    products = db.Products.Where(p => p.CategoryId == id).ToList();
    
                }
                else
                {
                    products.Insert(0, new Product { Id = 0, Name = "--Select a category first--" });
                }
                var result = (from r in products
                              select new
                              {
                                  id = r.Id,
                                  name = r.Name
                              }).ToList();
    
                return Json(result, JsonRequestBehavior.AllowGet);
            }
    
    

    Step 5: Modify the Create View of Items folder
    Modify the Create View as follows.

    @model Web.Mahedee.net.Models.Item
    
    @{
        ViewBag.Title = "Create";
    }
    
    
    
    
    

    Create

    @using (Html.BeginForm()) { @Html.AntiForgeryToken()

    Item


    @Html.ValidationSummary(true, "", new { @class = "text-danger" })
    @Html.LabelFor(model => model.CategoryId, "Category", htmlAttributes: new { @class = "control-label col-md-2" })
    @Html.DropDownList("CategoryId", null, htmlAttributes: new { @class = "form-control" }) @Html.ValidationMessageFor(model => model.CategoryId, "", new { @class = "text-danger" })
    @Html.LabelFor(model => model.ProductId, "Product", htmlAttributes: new { @class = "control-label col-md-2" })
    @Html.DropDownList("ProductId", null, htmlAttributes: new { @class = "form-control" }) @Html.ValidationMessageFor(model => model.ProductId, "", new { @class = "text-danger" })
    @Html.LabelFor(model => model.Name, htmlAttributes: new { @class = "control-label col-md-2" })
    @Html.EditorFor(model => model.Name, new { htmlAttributes = new { @class = "form-control" } }) @Html.ValidationMessageFor(model => model.Name, "", new { @class = "text-danger" })
    }
    @Html.ActionLink("Back to List", "Index")
    @section Scripts { @Scripts.Render("~/bundles/jqueryval") }

    Now run the application and type the following URL .

    http://localhost:61767/Items/Create

    You will see the following output. Now select category from category dropdown lsit, you will see product dropdown list is populating on corresponding category.

    2015-12-04-06

    Means, it’s working…!! Cheers!!!

    ASP.NET Application Performance Tuning and Scalability Improvement (Part – 1)

    Every developers and customer wants his/her application performed well. But it is very tricky to improve performance of a web application. It’s actually depends on different parameter like HTML client, HTTP network, Web server, middle-tier components, database components, resource-management components, TCP/IP networks, and database servers. Sometimes performance of the application increases drastically, if you change a single parameter. Sometimes you have to change multiple parameters. Here are the some performance optimization tips for ASP.NET web applications which may help you to increase performance of ASP.NET Application.

    Prepare release with release mode
    When prepare release for deployment, select release mode instead of debug mode.

    How affect in performance?

    • If you choose debug mode instead of release mode, you are creating pdb (program database – uses for debugging) files which creates extra overhead. For this reason you may face timeout problem.

    Best Practice

    • Always prepare release in release mode.

    Release mode

    In Web.Config, Set debug=”false”
    Set debug=”false” in web.config as follows after deploying your application. By default debug=”true” when you create a web application. It is necessary to set debug=”true” in development environment.

      
        
      
    

    How affect in performance?

    • If you set debug = “true”, application requires the pdb information to be inserted into the file and that results in a comparatively larger file and hence processing will be slow.

    Best Practice

    • In deployment server, set debug = “false” in web.config

    Turn off Tracing unless until required
    Sometimes developers need to trace the application to monitor the executions of application or a pages. It requires for application diagnostic purposes.

    How affect in performance?

    • When trace is enabled it loaded extra information to the pages which degrades performances.

    Best Practice

    • Always set trace enabled = “false” unless or until you required to monitor a page’s executions. Set trace enable = “false” as follows in web.config.
    
        
    
    

    Carefully manage session state
    Session state is a very useful feature of asp.net. Though, ASP.NET manages session state by default, we must pay attention of session memory management.

    • How affect in performance?
    • When you store your data in in-process or on a state server or in a SQL Database, session state, it requires memory.
    • It is also time consuming when you store or retrieve data in-process or state server or SQL server.

    Best Practice

    • If your page is static, it is recommended not to use session state. In such cases where you don’t need to use session state, disable it on your web form using the following directive:
      <@%Page EnableSessionState="false"%>
    • In case you use the session state only to retrieve data and not to update, make the session state read-only using the following directive.
      <@%Page EnableSessionState ="ReadOnly"%>
    • If your application session state is out of process then consider carefully whether there is a need of the state server or SQL Server mode.
    • SQL Server session mode provides lower performance than state server mode.
    • Try to avoid keeping object in session. Since it requires serializing then de-serializing which affected in performance.
    • Use client-side state management than server side.

    Disable View State of a page if not required

    • It stores data in the generated HTML using hidden field not on the server.
    • View State provides page level state management
    • As long as the user is on the current page, state is available and the user redirects to the next page and the current page state is lost
    • View State can store any type of data because it is object type but it is preferable not to store a complex type of data due to the need for serialization and deserialization on each post back

    How affect in performance?

    • It increases the total payload of a page when submitted and when serving request.
    • Serialization and deserialization of the data is required when submitting data and gets requested data.
    • View state increases the memory allocations on the server.

    Best Practice

    • Pages that do not have any server postback events can have the view state turned off.
    • The default behaviour of the View State property is enabled, but if you don’t need it, you can turn it off at the control or page level.
    • Within a control, simply set the EnableViewState property to false, or set it globally within the page using this setting.

      <%@ Page EnableViewState="false" %>

    Use finally block to release resources
    We always uses try, catch and finally block for exception handling. Finally block executes whether any exception occurs or not.
    How affect in performance?

    • Sometimes application occupy resources where as it doesn’t need it. It is occur due to bad programming.

    Best Practice

    • Always use a finally block to release resources like closing database connections, closing files, disposing objects and other resources.

    Avoid unnecessary round trips to the server

    How affect in performance?

    • Unnecessary round trips significantly effect on web application performance.
    • It increases network latency and downstream server latency.
    • Many data-driven Web sites heavily access the database for every user request. While connection pooling helps, the increased network traffic and processing load on the database server can adversely affect performance.

    Best Practice

    • Keep round trips as minimum as possible
    • Use Ajax or partial page load instead of full page reload or refresh.

    Choose low cost authentication
    Authentication is a main factor for a secured applications. You must take decision which authentication will you use? Keep in mind, passport authentication is slower than form-base authentication which is slower than Windows authentication.

    Use paging in grid view
    In asp.net web application to show data in tabular format, generally we use grid view. Besides this we also uses DataGrid, JQgrid, Telerik grid, Kendo Grid etc. For huge number of data we cannot think general way because it takes huge time to load.

    Best Practice

    • To load grid view faster take advantages of paging, it shows small subsets of data at a time. JQGrid is faster than asp.net grid view because it does everything in client side.

    Minimizes number of web server control

    How affect in performance?

    • The uses of web server controls increase the response time.
    • Web server controls go to the server executes all of its life cycle and then rendered on the client side.

    Best Practice

    • Don’t use server control unless until required. Use HTML elements where suited.