need to bypass link to open destination page

muybn · June 24th, 2010, 10:34 PM

I have a site on which members can select from a list of links (from a ListView in profiles.aspx) in order to view details of another site member (in profile_detail.aspx), using the following code:

profiles.aspx and profiles.aspx.vb:

Code:

<asp:LinkButton ID="lnkBtnItem" Text="Select" CommandArgument='<%#Eval("UserID") %>' OnCommand="lnkBtn_Command" ForeColor="#FF0000" Font-Bold="true" Font-Size="11px" runat="server" />

Code:

    Protected Sub lnkBtn_Command(ByVal sender As Object, ByVal e As CommandEventArgs)
        Session("UserID") = Convert.ToString(e.CommandArgument)
        Response.Redirect("~/profile_detail.aspx")
    End Sub

I would like to do the following tasks but need guidance:

From a completely different page (in other words, not from profiles.aspx this time), the user clicks on a photo of a site member; the program picks up the UserID associated with the photo from a database table and saves it to a session variable; completely bypasses the profiles.aspx page; goes directly to profile_detail.aspx and displays the correct person.

My problem: I don't how to bypass clicking the link on profiles.aspx.

In other words, I want to go directly to profile_detail.aspx and apply the UserID session variable in displaying the person who matches that UserID.

Any ideas?

muybn · June 24th, 2010, 10:55 PM

OK, it appears that I have it working now. I had an error that came from a change I made in the Where parameters of the LinqDataSource in profile_detail.aspx so I thought I wasn't proceeding correctly.

What happens is that profiles.aspx page's links passes UserID through a session variable to open the correct profile in profile_detail.aspx, so apparently just going to that page from any page with a session variable equal to one of the UserIDs is good enough to display the desired profile.

chroniclemaster1 · June 26th, 2010, 04:24 PM

Quote:

Originally Posted by muybn

OK, it appears that I have it working now. I had an error that came from a change I made in the Where parameters of the LinqDataSource in profile_detail.aspx so I thought I wasn't proceeding correctly.

What happens is that profiles.aspx page's links passes UserID through a session variable to open the correct profile in profile_detail.aspx, so apparently just going to that page from any page with a session variable equal to one of the UserIDs is good enough to display the desired profile.

Absolutely correct. The profile_detail.aspx has the code to look and process the variable from the session.

So ANYWHERE in the application, you just need to store the correct userid in the session whenever someone selects a user; then just take them to the detail page and it should work fine.

FYI don't store too much in the Session since it takes up server resources. If you store big pieces of information in the session (like images, binary data, XML files, etc.) or on a large application with tons of users, this could cause problems - ie the more users and the more data the more server memory gets eaten up. The best practice to maintain scalability is to store just a custom session id and keep the rest of the data in the user's profile (usually a DB, but you can use whatever you want to persist the data) However, a few small pieces of alpha-numerical data like this are just fine for most applications.