LoginView Class

I had the exact same problem with the LoggedInTemplate and FindControl. Part of the problem was probably that I was using it inside of a listview that was nested inside of another listview and the loginview control only displays when in "Edit" mode. It was weird, because FindControl worked once I took the LoginView out of the Listview control. I tried the "LoginViewFix" to create a new Login control, but it did not work.

Here is what did work. I added an event handler to handle the "ViewChanged" event the loginview control in the code behind (ViewChanging event did not work). Once it fired, it had no problem finding controls inside of the LoggedInTemplate using FindControl. Here is my code:

void ItemCreated(object sender, ListViewItemEventArgs e)
{
var HelloWorld = "Hello, World!";
var lv = e.Item.FindControl("lv") as LoginView;
if(lv != null)
{
lv.ViewChanged += delegate
{
var tb = lv.FindControl("tb") as TextBox;
if(tb != null)
{
tb.Text = HelloWorld;
}
};
}
}

I used an anonymous delegate because I needed to access the control from a ListViewDataItem and the data that it contained (fired at the ItemCreated event).

Let me know if this works for anyone else.

I have search the whole internet for the VB version of the c# code above, after 2 days I finally got the class I wanted (2 days would quite a performance for a novice like me). So here it is:

Imports System
Imports System.Data
Imports System.Configuration
Imports System.Web
Imports System.Web.Security
Imports System.Web.UI
Imports System.Web.UI.WebControls
Imports System.Web.UI.WebControls.WebParts
Imports System.Web.UI.HtmlControls

Namespace Fix

Public Class LoginViewFix
Inherits LoginView

<TemplateInstance(TemplateInstance.Single)> _
Public Overrides Property AnonymousTemplate() As System.Web.UI.ITemplate
Get
Return MyBase.AnonymousTemplate
End Get
Set(ByVal value As System.Web.UI.ITemplate)
MyBase.AnonymousTemplate = value
End Set
End Property

<TemplateInstance(TemplateInstance.Single)> _
Public Overrides Property LoggedInTemplate() As System.Web.UI.ITemplate
Get
Return MyBase.LoggedInTemplate
End Get
Set(ByVal value As System.Web.UI.ITemplate)
MyBase.LoggedInTemplate = value
End Set
End Property

End Class

End Namespace

Using a couple sites as guides I'm able to access a GridView_SelectedIndexChanged event and get the SelectedDataKey.Value.

Here is how:

Add a Gridview Control to a Admin Role in the LoginView. Add your own named event to the OnSelectedIndexChange event.

<asp:RoleGroup Roles="Admin">
                <ContentTemplate>
                        <asp:GridView ID="GridView1" runat="server" AllowPaging="True" 			AllowSorting="True"                     					AutoGenerateColumns="False"

			DataKeyNames="PCC_ID" DataSourceID="dsPCC"
                        	OnSelectedIndexChanged="MyGVW_SelectedIndexChanged">
                        <Columns>
 			....
                        </Columns>
                        </asp:GridView>
                    	<asp:SqlDataSource ID="dsPCC" runat="server" 					ConnectionString=

			"<%$ ConnectionStrings:PCC_SQL_Connection %

			>"SelectCommand="SELECT [PCC_ID], [Product], [Brand_Name],

			[Cat_Name], [GBU_DisplayName], [PCC_Author], [PCC_name] 

			FROM [vw_PCC]">

		      </asp:SqlDataSource>

                	</ContentTemplate>
</asp:RoleGroup>

CodeBehind:

    Protected Sub MyGVW_SelectedIndexChanged(ByVal sender As Object, ByVal e As  EventArgs)

        Dim MyGVW As GridView = CType(Me.LoginView1.FindControl("GridView1"), GridView)
        Dim MyRow As GridViewRow = CType(Me.LoginView1.FindControl("GridView1"), GridView).SelectedRow
        Dim intPC_ID As Integer
        intPC_ID = MyGVW.SelectedDataKey.Value
        BinaryRender(intPC_ID)
    End Sub

Using the above example I'm able to get the 'Key' Value from the Gridview, which is embeded in a LoginView Control.

Here are the sites I used as examples:

http://quickstarts.asp.net/QuickStartv20/aspnet/doc/ctrlref/login/loginview.aspx

http://forums.asp.net/thread/1666668.aspx

 

Hope this helps,

rwiethorn

rwiethorn<no-Spam>@gmail.com

Typically the templated controls in a LoginView have unique identifiers within the page, but you cannot easily access them at the page level. For instance, if the anonymous template contains a button whose ID is "btnLogin" you will not be able to access it as "this.btnLogin" within the page class. Nikhil Kothari explained this in his blog at http://www.nikhilk.net/SingleInstanceTemplates.aspx.

You can deal with this in several ways, such as by using FindControl, but if you want the convenience of having ASP.NET create the templated control objects automatically, then you must override the LoginView class as follows:

using System;
using System.Data;
using System.Configuration;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;

namespace Fix
{
  public class LoginViewFix : LoginView
  {
    [TemplateInstance(TemplateInstance.Single)]
    public override ITemplate AnonymousTemplate
    {
      get
      {
        return base.AnonymousTemplate;
      }
      set
      {
        base.AnonymousTemplate = value;
      }
    }

    [TemplateInstance(TemplateInstance.Single)]
    public override ITemplate LoggedInTemplate
    {
      get
      {
        return base.LoggedInTemplate;
      }
      set
      {
        base.LoggedInTemplate = value;
      }
    }
  }
}

 

Next you need to register the fixed version of LoginView by adding the following statement to your page:

<%@ Register NameSpace="Fix" TagPrefix="fix" %>

 

Finally, change all instances of <asp:LoginView /> to <fix:LoginViewFix /> in your page file(s).

This solution makes programming convenient, but it also derails the web form designer. That is, after you make the changes above, you will no longer be able to see the templated controls in the designer view. Therefore it's best to make these changes after the page has been designed.

Note that you will still have trouble accessing controls contained within RoleGroup templates. Because the RoleGroup class is sealed, you can't apply the TemplateInstance property as we did for the anonymous and logged-in templates. :-(

To see more examples of how to use this control, refer to the ASP.NET Quickstart Tutorial.

http://www.asp.net/QuickStart/aspnet/doc/ctrlref/login/loginview.aspx