Get Data in a Generic List after the Post Back

First you have to create a class 

    [Serializable]
    public class Keyword
    {
     
        [Serializable]
        public class Item
        {
            public string KeywordId { get; set; }
        }

        [Serializable]
        public class KeywordList
        {
            public List<Item> KeywordId()
            {
                return null;
            }
        }

    }

   
   Then after in a page .cs File

  public string ItemsValues = "Keyword";
      
  public List<Keyword.Item> Items
        {
            get
            {
                if (!(ViewState[ItemsValues] is List<Keyword.Item>))
                {
                    ViewState[ItemsValues] = new List<Keyword.Item>();
                }
                return (List<Keyword.Item>)ViewState[ItemsValues];
            }
       }



Adding item in List 

  Items.Add(new Keyword.Item
            {
                KeywordId = e.Entry.Value

            });

Removing item in List



  Items.Remove(new Keyword.Item
            {
                KeywordId = e.Entry.Value

            });


Retrive data after the Postback

          List<Keyword.Item> Keyword_List= (List<Keyword.Item>)ViewState[ItemsValues];

           if (Keyword_List.Count > 0)
            {
                foreach (var data in Keyword_List)
                {
                    string id = data.KeywordId;
                }
            }






Comments

Post a Comment

Popular posts from this blog

Stack vs Heap So far we have seen how to declare basic type variables such as int , double , etc, and complex types such as arrays and structs. The way we have been declaring them so far, with a syntax that is like other languages such as MATLAB, Python, etc, puts these variables on the stack in C. The Stack What is the stack? It's a special region of your computer's memory that stores temporary variables created by each function (including the main() function). The stack is a "FILO" (first in, last out) data structure, that is managed and optimized by the CPU quite closely. Every time a function declares a new variable, it is "pushed" onto the stack. Then every time a function exits, all of the variables pushed onto the stack by that function, are freed (that is to say, they are deleted). Once a stack variable is freed, that region of memory becomes available for other stack variables. The advantage of using the stack to store variable...
Read more

Validate Mobile Number with 10 Digits in ASP.Net

Here is the code for validating textbox for 10 digit mobile number. .ASPX File: <asp:TextBox ID="TextBox1" runat="server"></asp:TextBox><br\>     <asp:RegularExpressionValidator ID="RegularExpressionValidator1" runat="server"        ControlToValidate="TextBox1" ErrorMessage="RegularExpressionValidator"      ValidationExpression="[0-9]{10}"></asp:RegularExpressionValidator>
Read more
What is  Abstraction? Abstraction is another good feature of OOPS. Abstraction means to show only the necessary details to the client of the object . Do you know the inner details of the Monitor of your PC? What happen when you switch ON Monitor? Does this matter to you what is happening inside the Monitor? No Right, Important thing for you is weather Monitor is ON or NOT. When you change the gear of your vehicle are you really concern about the inner details of your vehicle engine? No but what matter to you is that Gear must get changed that’s it!! This is abstraction; show only the details which matter to the user.  Let’s say you have a method "CalculateSalary" in your Employee class, which takes EmployeeId as parameter and returns the salary of the employee for the current month as an integer value. Now if someone wants to use that method. He does not need to care about how Employee object calculates the salary? An only thing he needs to be concern is name...
Read more