If your referring to the ObjectDataSource here is an example:

Note that in this example I am setting a session variable in code that is used. The GetBlogEntries and AddBlogEntry procedures must accept a value of type string. I have them both as optional values set to a blank string, such as:

      Dim strSPROC As String = ""
      If Category.Trim = "" Then
         strSPROC = "blog_GetBlogEntries"
      Else
         strSPROC = "blog_GetBlogEntriesByCategory"
      End If

Thanks for your reply,

yes i was refering to ObjectDataSource,

Actually i am total beginner, i could not follow exactly what you explained me,

Could you please  explain little bit more.

And  i have a question about your reply : there is  AddBlogEntry  procedure in your code instead of InsertBlogEntry ?

jwadsworth:

If your referring to the ObjectDataSource here is an example:

<asp:ObjectDataSource ID="ObjectDataSourceBlogEntries" Runat="server"    
     TypeName="BlogManager"    SelectMethod="GetBlogEntries" InsertMethod="AddBlogEntry">
      <SelectParameters>
         <asp:SessionParameter DefaultValue=""
            Name="category"
            Direction="input"
            SessionField="blogcategory"
            Type="string"
            ConvertEmptyStringToNull="false" />
         </SelectParameters>
      <InsertParameters>
         <asp:SessionParameter DefaultValue=""
            Name="category"
            Direction="Input"
            SessionField="blogcategory"
            Type="string"
            ConvertEmptyStringToNull="false" />
      </InsertParameters>
</asp:ObjectDataSource>

Note that in this example I am setting a session variable in code that is used. The GetBlogEntries and InsertBlogEntry procedures must accept a value of type string. I have them both as optional values set to a blank string, such as:

 

Public Shared Function GetBlogEntries(Optional ByVal Category As String = "") As Generic.List(Of Blog)
   Using connection As New SqlConnection(ConfigurationManager.ConnectionStrings("Personal").ConnectionString)

      Dim strSPROC As String = ""
      If Category.Trim = "" Then
         strSPROC = "blog_GetBlogEntries"
      Else
         strSPROC = "blog_GetBlogEntriesByCategory"
      End If

      Using command As New SqlCommand(strSPROC, connection)
command.CommandType = CommandType.StoredProcedure
         connection.Open()
         If Category.Trim <> "" Then command.Parameters.Add(New SqlParameter("@Category", Category))
            Dim list As New Generic.List(Of Blog)()
            Using reader As SqlDataReader = command.ExecuteReader()
               Do While (reader.Read())
                  Dim temp As New Blog(CInt(reader("EntryID")), CStr(reader("Category")), CStr(reader("EntryTitle")), CStr(reader("EntryText")), CStr(reader("UserName")), CDate(reader("DateCreated")), CInt(reader("IsDeleted")), CInt(reader("CommentCount")))

                  list.Add(temp)
               

Loop
            End Using
            Return list
         End Using
   End Using
End Function

Here is maybe a little simpler example. You would of course need to change the procedure name referenced as the InsertMethod. You would also need to add a value to be accepted in your procedure.

On your page you have the ObjectDataSource. You would specify the TypeName as the class that your procedure resides in. Then specify the procedure in the InsertMethod. Next, inside the <InsertParameters> tag you would declare the type of asp: parameter to user. In this case I chose a SessionParameter. There are 7 different types of parameters that you can use. Play with the intellisense to see the others. In the SessionParameter below, the SessionField property refers to the name of the session variable I have set elsewhere in code. The Name property refers to the name of the variable used in the Procedure such as MyFunction(Byval category As String), where category is the variable referred to in the Name property below.

<asp:ObjectDataSource ID="ObjectDataSourceBlogEntries" Runat="server"    
     TypeName="BlogManager" InsertMethod="AddBlogEntry">
      <InsertParameters>
         <asp:SessionParameter DefaultValue=""
            Name="category"
            Direction="Input"
            SessionField="blogcategory"
            Type="string"
            ConvertEmptyStringToNull="false" />
      </InsertParameters>
</asp:ObjectDataSource>

Then you have your procedure that is referred to in the InsertMethod above.

Public Shared Function GetBlogEntries(Optional ByVal category As String = "") As Generic.List(Of Blog) 

 ' In here you would have code that uses the Category value passed in to Insert into the database.

End Function

Thanks for your reply.

I have few more questions.Please check the following if  my understanding is on right path or not.

Q 1. These are the 7 different parameters which you mentioned in your reply  ?

   Parameter

  QueryStringParameter

   ControParameter

   SessionParameter

   FormParameter

   CookieParameter

  ProfileParameter

Q 2    First you assigned    InsertMethod="AddBlogEntry"

 becasue  InsertMethod gets  the name of the method that the ObjectDataSource control invokes to insert data  ?

Q 3 You decalred SessionParameter inside <InsertParameter>

because  InsertParameter gets the parameters collection that contains the parameters that are used by the InsertMethod method i.e AddBlogEntry  ?

jwadsworth:

Here is maybe a little simpler example. You would of course need to change the procedure name referenced as the InsertMethod. You would also need to add a value to be accepted in your procedure.

On your page you have the ObjectDataSource. You would specify the TypeName as the class that your procedure resides in. Then specify the procedure in the InsertMethod. Next, inside the <InsertParameters> tag you would declare the type of asp: parameter to user. In this case I chose a SessionParameter. There are 7 different types of parameters that you can use. Play with the intellisense to see the others. In the SessionParameter below, the SessionField property refers to the name of the session variable I have set elsewhere in code. The Name property refers to the name of the variable used in the Procedure such as MyFunction(Byval category As String), where category is the variable referred to in the Name property below.

<asp:ObjectDataSource ID="ObjectDataSourceBlogEntries" Runat="server"    
     TypeName="BlogManager" InsertMethod="AddBlogEntry">
      <InsertParameters>
         <asp:SessionParameter DefaultValue=""
            Name="category"
            Direction="Input"
            SessionField="blogcategory"
            Type="string"
            ConvertEmptyStringToNull="false" />
      </InsertParameters>
</asp:ObjectDataSource>

Then you have your procedure that is referred to in the InsertMethod above.

Public Shared Function GetBlogEntries(Optional ByVal category As String = "") As Generic.List(Of Blog) 

 ' In here you would have code that uses the Category value passed in to Insert into the database.

End Function

 

Q1. Yes those are the seven differnt parameters

Q2. Yes.

Q3. Yes. In the case that you use the SessionParameter you would have a session variable set somewhere in code.

Thanks for your reply.

I have another question not related to previous post, i put this question in forum but could not get it, if possible please explain it to me .

Case:  I am talking about Personal Wesbite Starter , In Admin/Photo.aspx method,

there are  code lines:

<itemtemplate>

<%# Container.DataItem %>

</itemtemplate>

</asp:datalist>

My question is What does <%# Container.DataItem %> does in the above lines  of code ?

I'm not 100% sure about this but I think Container refers to the object or source that the DataList is bound to. DataItem refers to the item in the collection being bound.