ASP.NET MVC Overview Part 2

February 14, 2010 13:36 by wjchristenson2

In Part1, I discussed the basics of what the MVC pattern is and how Microsoft has incorporated MVC into ASP.NET.  In this segment, I am going to discuss some general advantages of ASP.NET Web Forms and ASP.NET MVC.  Neither flavor of ASP.NET will be the superior choice in all circumstances.  Therefore knowing the advantages to each will help.

I’ve found through my development career that there’s never a right or wrong way to do something.  Scott Guthrie posted recently the following which is very true, “Great developers using bad tools/frameworks can make great apps.”  The same principal applies to bad developers using great tools/frameworks… inevitably they will create bad applications.  Just because one framework may shine better in certain situations may not mean its better.  If the developers using the superior technology cannot grasp or develop it properly, its full potential will not be realized.  So keep these principals in mind when evaluating the two.

Advantages of ASP.NET MVC
1) Separation of model, view, controller results in reduction of complexity, promotes parallel development, and easier to maintain.
2) Enables full control over rendered HTML (leaner html rendering).
3) Works much better with automated testing as all core contracts are interface based.  You can run unit-tests without having to run the controllers under an ASP.NET process.
4) Does not use view state or postbacks (no view stage = quicker load times).
5) Framework is very extensible and pluggable.
6) Supports existing markup (aspx, master pages, ascx, inline expressions).
7) Supports existing session, caching, authentication, etc.
8) Easy integration with javascript frameworks.
9) Follows the design of a stateless web.


Advantages of ASP.NET Web Forms
1) Commonality between windows forms development in that it uses the event model.
2) Usage of view state and server forms helps manage state more easily.
3) Promotes RAD more so than MVC as more controls/components are available.
4) Less complex than MVC and generally requires less code.
5) More mature as it’s been around since the 1990’s.

ASP.NET MVC Overview Part 1 (General ASP.NET MVC Overview)
ASP.NET MVC Overview Part 2 (Advantages of MVC and Web Forms)
ASP.NET MVC First Impressions


GridView Column Sorting - Up/Down Arrows

December 7, 2008 19:32 by wjchristenson2

In this article, I will show you how to manually sort the GridView WebControl and display sort direction arrows.  The GridView has built-in sorting capabilities, however if we want visual feedback as to what column is being sorted and to what direction, we have to perform this ourselves.  While extending the GridView WebControl would be optimal, I'm going to show a quick way to get it done without creating a new GridView control.  Maybe in a future post I'll show how we can create a custom GridView control with sort arrows.  Here is a picture of what our final sorted GridView will look like.

Here is the HTML markup of our GridView:


   1:            <asp:GridView 
   2:              ID="GridView1" 
   3:              runat="server" 
   4:              AutoGenerateColumns="False" 
   5:              DataKeyNames="CustomerID" 
   6:              CssClass="gridview" 
   7:              RowStyle-CssClass="gridview_itm" 
   8:              AlternatingRowStyle-CssClass="gridview_aitm" 
   9:              HeaderStyle-CssClass="gridview_hdr" 
  10:              PagerStyle-CssClass="gridview_pgr">
  11:              <Columns>
  12:                <asp:TemplateField>
  13:                  <HeaderTemplate>
  14:                    <asp:LinkButton ID="CustomerID_SortLnkBtn" runat="server" Text="Customer ID:" ToolTip="Click to Sort Column" CommandName="Sort" CommandArgument="CustomerID" CausesValidation="false" />
  15:                    <asp:ImageButton ID="CustomerID_SortImgBtn" runat="server" Visible="false" ToolTip="Click to Sort Column" CommandName="Sort" CommandArgument="CustomerID" CausesValidation="false" />
  16:                  </HeaderTemplate>
  17:                  <ItemTemplate><%#Eval("CustomerID")%></ItemTemplate>
  18:                </asp:TemplateField>
  19:                
  20:                <asp:TemplateField>
  21:                  <HeaderTemplate>
  22:                    <asp:LinkButton ID="CompanyName_SortLnkBtn" runat="server" Text="Company Name:" ToolTip="Click to Sort Column" CommandName="Sort" CommandArgument="CompanyName" CausesValidation="false" />
  23:                    <asp:ImageButton ID="CompanyName_SortImgBtn" runat="server" Visible="false" ToolTip="Click to Sort Column" CommandName="Sort" CommandArgument="CompanyName" CausesValidation="false" />
  24:                  </HeaderTemplate>
  25:                  <ItemTemplate><%#Eval("CompanyName")%></ItemTemplate>
  26:                </asp:TemplateField>
  27:                
  28:                <asp:TemplateField>
  29:                  <HeaderTemplate>
  30:                    <asp:LinkButton ID="ContactName_SortLnkBtn" runat="server" Text="Contact Name:" ToolTip="Click to Sort Column" CommandName="Sort" CommandArgument="ContactName" CausesValidation="false" />
  31:                    <asp:ImageButton ID="ContactName_SortImgBtn" runat="server" Visible="false" ToolTip="Click to Sort Column" CommandName="Sort" CommandArgument="ContactName" CausesValidation="false" />
  32:                  </HeaderTemplate>
  33:                  <ItemTemplate><%#Eval("ContactName")%></ItemTemplate>
  34:                </asp:TemplateField>
  35:              </Columns>
  36:            </asp:GridView>

The first step is to acquire customers from the Northwind database in the form of a DataTable.  We will then acquire a DataView object from our DataTable, and sort the view.  Once the data in our DataView has been sorted, we will then bind the GridView to the sorted DataView.  To accomplish the data retrieval, sorting, and data binding, I've created the following method:


   1:      Private Sub GridView1_DataBind()
   2:          Dim dt As DataTable = New DataTable()
   3:   
   4:          'fill our datatable w/ customers from the DB
   5:          Using conn As New SqlConnection(System.Configuration.ConfigurationManager.ConnectionStrings("NorthwindConnectionString").ConnectionString)
   6:              Dim sql As String = "SELECT [CustomerID], [CompanyName], [ContactName] FROM [Customers] WITH (NOLOCK)"
   7:              Dim cmd As SqlCommand = New SqlCommand(sql, conn)
   8:              Dim reader As SqlDataReader = Nothing
   9:   
  10:              Try
  11:                  conn.Open()
  12:                  reader = cmd.ExecuteReader(CommandBehavior.CloseConnection)
  13:                  dt.Load(reader)
  14:              Finally
  15:                  If Not reader Is Nothing AndAlso Not reader.IsClosed Then
  16:                      reader.Close()
  17:                  End If
  18:              End Try
  19:          End Using
  20:   
  21:          If dt.Rows.Count > 0 Then
  22:              'get a dataView object from our dataTable of customers
  23:              Dim dv As DataView = dt.DefaultView
  24:   
  25:              'if the user has elected to sort the gridview
  26:              If Not String.IsNullOrEmpty(Me.SortBy("GridView1")) Then
  27:                  'get the sort expression and apply it to our dataView
  28:                  Dim sortExpr As String = Me.SortBy("GridView1") & " " & IIf(Me.SortDirection("GridView1") = WebControls.SortDirection.Ascending, "ASC", "DESC").ToString()
  29:                  dv.Sort = sortExpr
  30:              End If
  31:   
  32:              'bind the dataView to our GridView
  33:              Me.GridView1.DataSource = dv
  34:              Me.GridView1.DataBind()
  35:          End If
  36:      End Sub

The logic is pretty straight forward.  Take note to line 28.  I am using 2 properties to store what column I am sorting by and what direction it is being sorted.  I persist the values in the ViewState and I also pass what GridView I either want to retrieve or store values for.  This allows me to have more that 1 sorting GridView on my page at a time using the same 2 properties.  Here's the code for the 2 properties to assist us with sorting.


   1:      ''' <summary>
   2:      ''' Gets or sets the column name to be sorted.
   3:      ''' </summary>
   4:      ''' <param name="GridViewID">The unique ID of the GridView.</param>
   5:      ''' <value></value>
   6:      ''' <returns></returns>
   7:      ''' <remarks></remarks>
   8:      Private Property SortBy(ByVal GridViewID As String) As String
   9:          Get
  10:              Dim o As Object = ViewState(GridViewID & "_SortBy")
  11:              If Not o Is Nothing Then
  12:                  Return o.ToString()
  13:              Else
  14:                  Return String.Empty
  15:              End If
  16:          End Get
  17:          Set(ByVal value As String)
  18:              ViewState(GridViewID & "_SortBy") = value
  19:          End Set
  20:      End Property
  21:   
  22:      ''' <summary>
  23:      ''' Gets or sets the sort direction.
  24:      ''' </summary>
  25:      ''' <param name="GridViewID">The unique ID of the GridView.</param>
  26:      ''' <value></value>
  27:      ''' <returns></returns>
  28:      ''' <remarks></remarks>
  29:      Private Property SortDirection(ByVal GridViewID As String) As SortDirection
  30:          Get
  31:              Dim o As Object = ViewState(GridViewID & "_SortDirection")
  32:              If Not o Is Nothing Then
  33:                  Return DirectCast(o, SortDirection)
  34:              Else
  35:                  Return WebControls.SortDirection.Ascending
  36:              End If
  37:          End Get
  38:          Set(ByVal value As SortDirection)
  39:              ViewState(GridViewID & "_SortDirection") = value
  40:          End Set
  41:      End Property

We have the sort by and sort direction properties (storing/persistance mechanisms).  We have the data retrieval, sorting of the data, and data binding method in place.  Now what we have to do is think about what events we need to account for.  First, on initial page load we'll want to fetch customer data and bind it to our GridView.  We'll only want to bind our GridView the first time the page loads and not subsequent postbacks.


   1:      Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load
   2:          If Not Page.IsPostBack Then
   3:              'bind the gridview on page first load
   4:              GridView1_DataBind()
   5:          End If
   6:      End Sub

Now we are ready to make the magic happen.  We want to handle the GridView's RowDataBound event and either show or hide our up/down arrows if the user has elected to sort a column.


   1:      Private Sub GridView1_RowDataBound(ByVal sender As Object, ByVal e As System.Web.UI.WebControls.GridViewRowEventArgs) Handles GridView1.RowDataBound
   2:          'if the row being dataBound is the header row - toggle sort image visibility/directions
   3:          If e.Row.RowType = DataControlRowType.Header Then
   4:              ToggleSortArrows(e.Row, "GridView1")
   5:          End If
   6:      End Sub
   7:   
   8:      Private Sub ToggleSortArrows(ByVal headerRow As GridViewRow, ByVal gridViewID As String)
   9:          Dim sortImgBtn As ImageButton = Nothing
  10:   
  11:          'loop through each cell in the header row
  12:          For Each tc As TableCell In headerRow.Cells
  13:              'loop through each control in the cell
  14:              For Each c As Control In tc.Controls
  15:                  'if the control is an image button and is our sort image button
  16:                  If TypeOf c Is ImageButton AndAlso c.ID.EndsWith("SortImgBtn") Then
  17:                      sortImgBtn = DirectCast(c, ImageButton)
  18:   
  19:                      'if the image button is in the column being sorted
  20:                      If Me.SortBy(gridViewID) = sortImgBtn.ID.Split(CChar("_"))(0) Then
  21:                          'show the image button and set its image url (sorted column)
  22:                          sortImgBtn.Visible = True
  23:                          If Me.SortDirection(gridViewID) = WebControls.SortDirection.Ascending Then
  24:                              sortImgBtn.ImageUrl = "~/img/uparrow.gif"
  25:                          Else
  26:                              sortImgBtn.ImageUrl = "~/img/dnarrow.gif"
  27:                          End If
  28:                      Else
  29:                          'hide the image button (not a sorted column)
  30:                          sortImgBtn.Visible = False
  31:                      End If
  32:                  End If
  33:              Next
  34:          Next
  35:      End Sub

Basically what we are doing is detecting if the row being DataBound is the header row or not.  If it is, we want to loop through each cell in the header row and get a handle on the column's associated sort image.  We use the ID of the sort image to acquire what column it represents and compare it to our SortBy property.  If it matches, then we want to show the appropriate sort direction image.  We hide the other sort images in non-sorted columns.

The only task we have left to account for is how to fire our sorting event.  Take a quick look at our GridView HTML markup.  The header row has both a LinkButton and ImageButton that raise a GridView command event to which we pass the column name that the user wants to sort by.  We then handle the event in our code behind.


   1:      Private Sub GridView1_RowCommand(ByVal sender As Object, ByVal e As System.Web.UI.WebControls.GridViewCommandEventArgs) Handles GridView1.RowCommand
   2:          If e.CommandName.ToUpper = "SORT" Then
   3:              InitializeSort(e.CommandArgument, "GridView1")
   4:              GridView1_DataBind()
   5:          End If
   6:      End Sub
   7:   
   8:      Private Sub InitializeSort(ByVal sortBy As String, ByVal gridViewID As String)
   9:          If Me.SortBy(gridViewID) = sortBy Then
  10:              If Me.SortDirection(gridViewID) = WebControls.SortDirection.Ascending Then
  11:                  Me.SortDirection(gridViewID) = WebControls.SortDirection.Descending
  12:              Else
  13:                  Me.SortDirection(gridViewID) = WebControls.SortDirection.Ascending
  14:              End If
  15:          Else
  16:              Me.SortBy(gridViewID) = sortBy
  17:              Me.SortDirection(gridViewID) = WebControls.SortDirection.Ascending
  18:          End If
  19:      End Sub

Once we capture our sort row command, we initialize our SortBy and SortDirection properties.  We either toggle the direction of the sorted column or the sorted column is a new column to be sorted to which we default the column to be sorted Ascending.

I hope this article helped a bit.  It's a quick way to get a GridView sorted with visual indicators (sort arrows) without creating a new custom GridView control.

GridViewSorting_Soln.zip (90.61 kb)


Save Scroll Position GridView Control

October 29, 2008 16:09 by wjchristenson2

I've seen a lot of articles on the web describing how to scroll a GridView.  Some of those articles may even go a little deeper and show you how to persist the scroll position across PostBacks.  What I haven't been able to find is how to encapsulate the scrolling and saving/persisting of the scroll position into a custom GridView control.  That is what I am going to show you how to do today.

There are many ways a developer may want to scroll their GridView (horizontal, vertical, freezing the header/footer, etc).  I'm not going to go into creating a bullet proof GridView control to accomplish those tasks.  My objective is to show you a technique to save/set the scroll position across PostBacks within a custom GridView control.

Here is what our end GridView control will look like.  First you can see a scrollable GridView.  When we scroll the GridView and then click the PostBack button, the page will perform a PostBack and the <div> will scroll itself back to where we left off.



So let's get to it.  First thing we do is create a new control and inherit from the GridView.  We then implement the IPostBackDataHandler to get and set our scroll position across PostBacks.  You'll see the LoadPostData function accomplishes this.  Take note that in line 3 I am referencing the name of my hidden field that I'll go over later.  We also tell the page that our new custom GridView (Me) has data to PostBack and we can do this in the GridView's Init.


   1:      Public Function LoadPostData(ByVal postDataKey As String, ByVal postCollection As System.Collections.Specialized.NameValueCollection) As Boolean Implements System.Web.UI.IPostBackDataHandler.LoadPostData
   2:          'get and set the new scroll position
   3:          Dim postedValue As String = postCollection(Me.ClientID & "_scroll")
   4:          If Not postedValue Is Nothing Then
   5:              Dim presentValue As Integer = Me.ScrollPosition
   6:              Me.ScrollPosition = CType(postedValue, Integer)
   7:              Return Not presentValue.Equals(Me.ScrollPosition)
   8:          End If
   9:      End Function
  10:   
  11:      Public Sub RaisePostDataChangedEvent() Implements System.Web.UI.IPostBackDataHandler.RaisePostDataChangedEvent
  12:          'do nothing
  13:      End Sub
  14:   
  15:      Private Sub ScrollingGridView_Init(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Init
  16:          If Not Me.Page Is Nothing Then
  17:              'indicates that the control has data to postback
  18:              Me.Page.RegisterRequiresPostBack(Me)
  19:          End If
  20:      End Sub

In order to scroll my new custom GridView, I need to wrap my GridView with a <div> tag.  To do this, I can override the Render method like so:


   1:      Protected Overrides Sub Render(ByVal writer As System.Web.UI.HtmlTextWriter)
   2:          If Not Me.Page Is Nothing Then
   3:              Me.Page.VerifyRenderingInServerForm(Me)
   4:          End If
   5:   
   6:          Me.PrepareControlHierarchy()
   7:   
   8:          If Not Me.DesignMode Then
   9:              If String.IsNullOrEmpty(Me.ClientID) Then
  10:                  Throw New HttpException("ScrollingGridView must be parented!")
  11:              End If
  12:   
  13:              writer.AddAttribute(HtmlTextWriterAttribute.Id, String.Format("{0}_div", Me.ClientID), True)
  14:              writer.AddAttribute("onScroll", "saveScrollPos('" & String.Format("{0}_scroll", ClientID) & "', '" & String.Format("{0}_div", Me.ClientID) & "');")
  15:              writer.AddStyleAttribute(HtmlTextWriterStyle.OverflowY, "auto")
  16:              writer.AddStyleAttribute(HtmlTextWriterStyle.Height, "300px")
  17:              writer.RenderBeginTag(HtmlTextWriterTag.Div)
  18:          End If
  19:   
  20:          Me.RenderContents(writer)
  21:   
  22:          If Not Me.DesignMode Then
  23:              writer.RenderEndTag()
  24:          End If
  25:      End Sub

Notice that when I render my <div> that I also wire in a call to my JavaScript function to save the scroll position "onScroll".  At this point I have completed the PostBack data handling and I have shown you how to wrap a <div> around our GridView so we can scroll and it will call a JavaScript function "onScroll" that will save the position to a hidden field.

The next phase is to emit our JavaScripts.  I always emit JavaScript in the PreRender phase of a control's lifecycle as the ClientID should be set at that point.  We need a function to set the scroll position and a function to save the scroll position.  Here they are:


   1:          'generate & register javascript blocks
   2:          Dim key As String = "ScrollingGridView"
   3:          Dim script As StringBuilder = New StringBuilder()
   4:          With script
   5:              .AppendLine("function saveScrollPos(whereID, whatID) {")
   6:              .AppendLine("  document.getElementById(whereID).value = document.getElementById(whatID).scrollTop;")
   7:              .AppendLine("}")
   8:              .AppendLine("function setScrollPos(whereID, whatID) {")
   9:              .AppendLine("  document.getElementById(whatID).scrollTop = (document.getElementById(whereID).value.length > 0) ? document.getElementById(whereID).value : 0;")
  10:              .AppendLine("}")
  11:          End With
  12:          If Not sm Is Nothing Then
  13:              ScriptManager.RegisterStartupScript(Me.Page, Me.GetType(), key, script.ToString(), True)
  14:          Else
  15:              Me.Page.ClientScript.RegisterStartupScript(Me.GetType(), key, script.ToString(), True)
  16:          End If

Notice we either acquire or save the scroll position to our hidden field.  Now how do we emit a hidden field inside our GridView?  My first attempts were to override the Render of the GridView control and emit hidden field there.  It didn't work.  I ended up registering the hidden field via .NET's scripting objects instead.  Check it out:


   1:          'register our hidden field to save our scroll position
   2:          If Not sm Is Nothing Then
   3:              ScriptManager.RegisterHiddenField(Me.Page, String.Format("{0}_scroll", Me.ClientID), Me.ScrollPosition.ToString())
   4:          Else
   5:              Me.Page.ClientScript.RegisterHiddenField(String.Format("{0}_scroll", Me.ClientID), Me.ScrollPosition.ToString())
   6:          End If

Notice that I assign the scroll position to the hidden field's value.  Last thing we need to do is register a startup script to get the persisted scroll position from our hidden field and scroll our <div>.  If you remember we created a JavaScript function for this (setScrollPosition).


   1:          'generate & register startup javascripts
   2:          key = String.Format("{0}_setScrollPos", Me.ClientID)
   3:          script = New StringBuilder()
   4:          script.AppendLine("setScrollPos('" & String.Format("{0}_scroll", Me.ClientID) & "','" & String.Format("{0}_div", Me.ClientID) & "');")
   5:          If Not sm Is Nothing Then
   6:              ScriptManager.RegisterStartupScript(Me.Page, Me.GetType(), key, script.ToString(), True)
   7:          Else
   8:              Me.Page.ClientScript.RegisterStartupScript(Me.GetType(), key, script.ToString(), True)
   9:          End If

Putting it all Together:

In summary, we persist the scroll position of the div that wraps our GridView via a hidden field which is registered via the Page.ClientScript or ScriptManager object.  We wrap the GridView with a <div> by overriding the GridView's Render method.  The <div> saves the scroll position to the hidden field as the <div> is scrolled.  We acquire the value stored in the hidden field via the LoadPostData function.  Once a PostBack occurs, we set the scroll position of the <div> with a startup script.


ScrollingGridView_Soln.zip (97.19 kb)

Show UpdateProgress when using an UpdatePanel with Triggers

August 23, 2008 14:05 by wjchristenson2

with ASP.NET AJAX Extensions 1.0 for ASP .NET 2.0...

You may have come across a situation where an UpdatePanel performs a partial-page update and the associated UpdateProgress control does not display.  The culprit is UpdatePanel AsyncPostbackTriggers.  If an UpdatePanel's partial-page update was triggered by a control outside the UpdatePanel, the UpdateProgress control is oblivious to this fact.  The workaround that I've found is to get a handle to the instance of the PageRequestManager class and add our own events to show and hide the UpdateProgress ourselves via JavaScript before and after the triggered request.

We are going to create a page that will add 2 numbers and show the calculated result.  We will have a TextBox for number 1, a TextBox for number 2, and a label to show the result all within an UpdatePanel.  The calculate Button will be outside the UpdatePanel and will thus be our AsyncPostBackTrigger.  We then have our UpdateProgress control that we want shown while the webpage calculates our results.  Here is the HTML markup to accomplish our base page.

 

   1:          <asp:UpdatePanel ID="UpdatePanel1" runat="server" UpdateMode="Conditional">
   2:            <Triggers>
   3:              <asp:AsyncPostBackTrigger ControlID="Button1" EventName="Click" />
   4:            </Triggers>
   5:            <ContentTemplate>
   6:              <asp:TextBox ID="tbxValue1" runat="server" Text="1" Width="50" /> + <asp:TextBox ID="tbxValue2" runat="server" Text="1" Width="50" /> = <asp:Label ID="lblResult" runat="server" Text="2" />
   7:            </ContentTemplate>
   8:          </asp:UpdatePanel>
   9:          
  10:          <asp:Button ID="Button1" runat="server" Text="Calculate" />
  11:          
  12:          <asp:UpdateProgress ID="UpdateProgress1" runat="server" AssociatedUpdatePanelID="UpdatePanel1" DynamicLayout="true" DisplayAfter="0">
  13:            <ProgressTemplate>
  14:              <div style="background-color: #ffffc9;">Calculating...<div>
  15:            </ProgressTemplate>
  16:          </asp:UpdateProgress>

Now that we have our markup finished, let's handle the click event of our calculate button.  To see the UpdateProgress control for a longer duration, I went ahead and added a sleep timer of 3 seconds to delay the calculation.

 

   1:      Private Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles Button1.Click
   2:          System.Threading.Thread.Sleep(3000)
   3:          lblResult.Text = (CInt(tbxValue1.Text) + CInt(tbxValue2.Text)).ToString()
   4:      End Sub

Now for the actual meat of this post.  The following JavaScript calls the getInstance() method of the PageRequestManager object to get the instance of the PageRequestManager class.  We then add our functions to be called when the the request is initialized and ended.  This will allow us to show our UpdateProgress control when the request is initialized and then hide it again when the request is ended.  Here is the JavaScript to accomplish this.

 

   1:  <script type="text/javascript" language="javascript">
   2:  <!-- 
   3:   
   4:  var prm = Sys.WebForms.PageRequestManager.getInstance();
   5:  var postBackElement;
   6:   
   7:  function CancelAsyncPostBack() {
   8:    if (prm.get_isInAsyncPostBack()) {
   9:      prm.abortPostBack();
  10:    }
  11:  }
  12:   
  13:  prm.add_initializeRequest(InitializeRequest);
  14:  prm.add_endRequest(EndRequest);
  15:   
  16:  function InitializeRequest(sender, args) {
  17:    if (prm.get_isInAsyncPostBack()) {
  18:        args.set_cancel(true);
  19:    }
  20:    postBackElement = args.get_postBackElement();
  21:    if (postBackElement.id == 'Button1') {
  22:      $get('UpdateProgress1').style.display = 'block'; 
  23:    }
  24:  }
  25:  function EndRequest(sender, args) {
  26:    if (postBackElement.id == 'Button1') {
  27:      $get('UpdateProgress1').style.display = 'none';
  28:    }
  29:  }
  30:   
  31:  // -->
  32:  </script>

 

Note that we acquire what element fired the request.  We only want to show/hide our UpdateProgress control if the postBackElement was our calculate button.

 

TriggersUpdateProgress_Soln.zip (45.30 kb)