ansaurus

Question

Showing completely different output based on the query-string

Answer 1

+6 A:

You could do the following (simple redirect):

If Request.QueryString("page") = 1 Then
   Response.Redirect("MyPage1.aspx")
Else
   Response.Redirect("MyPage2.aspx")
End If

You could also do this (read more here):

If Request.QueryString("page") = 1 Then
   Server.Transfer("MyPage1.aspx")
Else
   Server.Transfer("MyPage2.aspx")
End If

And finally one more option (show/hide different panels on the page):

If Request.QueryString("page") = 1 Then
   MyPanel1.Visible = true
   MyPanel2.Visible = false
Else
   MyPanel1.Visible = false
   MyPanel2.Visible = true
End If

RSolberg 2009-08-14 21:00:38

@womp: I just got hit with -4 within 20 seconds... Your post does not actually fit the bill. See my note.

RSolberg 2009-08-14 21:13:16

Maybe it wasn't you... every post lost a vote, and I noticed you dropped 6 rep... apologies.

womp 2009-08-14 21:14:16

@womp: no worries, I do hate the gaming the system that goes on here... I know folks go back and fourth on it on META, but when you lose 4 points in the matter of 20 seconds with no explanation as to why, it is very fishy.

RSolberg 2009-08-14 21:15:39

It's always interesting to see which threads generate this kind of activity... invariably it's the "easier" questions

womp 2009-08-14 21:19:23

No kidding... I really see it take off on the jQuery ones. Even seen some where answer #2 was copy paste from #1 (or typed the same) and then answer 1 is voted down at -1...

RSolberg 2009-08-14 21:23:41

Answer 2

+1 A:

You really have a few options, you could:

Response.Redirect(url) to a different page based on the input.
You could have an ASP:Panel with the "visible" property set to false and toggle that value based on the input.

JMP 2009-08-14 21:01:18

Or a MultiView instead of the Panel.

Forgotten Semicolon 2009-08-14 21:02:18

MultiView is probably more suited to this, yes..

Juri 2009-08-14 21:11:44

Answer 3

+4 A:

I would suggest using the MultiView control.

In a nutshell, you would create two multiview "Views", each with the html that you would want to show. Then you could look at the querystring parameter and switch the active view of the multiview accordingly.

This has a lot of advantages to Response.Redirect() like others suggested. First off, that would always generate at least two browser requests. Also, Response.Redirect() throws a ThreadAborted exception behind the scenes, which can confuse people diagnosing the application.

Example MultiView control:

ASPX:

<form id="form1" runat="server">
    <div>
    <asp:MultiView ID="MultiView1" runat="server">
        <asp:View runat="server">
        Hi, this is Page 1
        </asp:View>
        <asp:View runat="server">
        Hi, this is Page 2
        </asp:View>
    </asp:MultiView>    
    </div>
    </form>

Code:

 Protected  Sub Page_Load(ByVal sender As Object, ByVal e As EventArgs)
            If Request.QueryString("page") = "1" Then
                MultiView1.ActiveViewIndex = 0
            Else 
                MultiView1.ActiveViewIndex = 1
            End If
 End Sub

womp 2009-08-14 21:02:04

Looks alot like C# while the person was asking about VB

RSolberg 2009-08-14 21:11:12

Changed to VB. Hardly worth a downvote.

womp 2009-08-14 21:15:27

And so the up-vote shall reflect such a change ;)

RSolberg 2009-08-14 21:16:24

much appreciated :)

womp 2009-08-14 21:18:36

It took me a while, but I changed<asp:MultiView ID="MultiView1" runat="server">to<asp:MultiView ActiveViewIndex="0" ID="MultiView1" runat="server">and it worked perfectly!Thank you so much for your help!

2009-08-17 14:34:01

Answer 4

+1 A:

Why not use different files instead? redirect to different pages. That would avoid having to have if statements everywhere.

OR

put your data in panels and just hide one or the other panel1.visible = (true/false). That's the best thing to do if you have to have it all in the same aspx page.

Eric 2009-08-14 21:02:33

Answer 5

A:

Hi there.

For future reference, you can still use the classic ASP way to control content. Here's an ASPX page I wrote just now:

<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="_Default" %>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"&gt;

<html xmlns="http://www.w3.org/1999/xhtml"&gt;
<head runat="server">
    <title></title>
</head>
<body>
    <form id="form1" runat="server">
    <div>
<%
    if (3 == 9)
    {%>
    <span>Hello</span>
    <%
    }
    else
    {
    %> <span>What?</span > <%
    }

     %>   

    </div>
    </form>
</body>
</html>

When the page renders, it displays 'What?' on the page.

However, I would say that this is bad practise and poor design! Use either womp's suggestion of a multiview, or a page redirect.

Cheers. Jas.

Jason Evans 2009-08-14 21:08:28

Answer 6

A:

I prefer doing it on the ASPX page using DataBinding:

<asp:PlaceHolder runat="server" ID="Messages">
    <asp:Label runat="server" Visible=<%# Request.QueryString("page") = 1 %> Text="Message 1" />    
    <asp:Label runat="server" Visible=<%# Request.QueryString("page") <> 1 %> Text="Message 2"/>
</asp:PlaceHolder>

Then on the server side:

Protected  Sub Page_Load(ByVal sender As Object, ByVal e As EventArgs)            
    Messages.DataBind()
End Sub

Sébastien Ros 2009-08-24 07:35:06

ansaurus

tags:

views:

answers:

Showing completely different output based on the query-string

related questions