I'v not clear 100% of your question. but I think you asking whether request.querystring usage. The thing is when you use it others can see what are the parameters. That was happen even you encording url. So it depend on your requirment.for example if you pass username and password as parameter of querystring, that shows in addressbar and anybody can see it. but if you pass page number or search word (like serchengine) it is not a problem because it's not a problem.

But in asp .net you have many options to pass parameters without use querystring.

So to keep code clean and professional, what would you use instead?? I am not too crazy about using Session variables or viewstate as I try to consider cases where session may be disabled or viewstate is turned off by mistake or something happens, say in firefox that causes it not to work as I would expect. But maybe all this is just me being paranoid. How would you handle this yourself?

Actually I use view state to keep my all variable and object. Normally I put my all variables in a class and keep its object in view state and pass it as object through the pages. I think that’s better because I have over 300 variables in my single page. So then I can access my variables in next page. And also I do not use session variables to keep my variables because after some times the variables are cleared. And I personally think session variables are heavy for the system.

You mention that you use  a class to persist your variables. Can you please give me an idea of what you mean here. I mean sample code to give me an idea of what I can use in my case to do this?

normally you want to do someway to pass variables between pages. to do that you have to create properties in your source page.

example

private int age;
private string name;

 public int Age
 {
  get { return age;}
  set { age = value;}
 }
 

 public string Name
 {
  get { return name;}
  set { name = value;}
 }

so you can get that property from next page. But in my case I define seperate class to keep both values. and i define that above properties in my class not axpx.cs page.So then I want to create and instance of that class and assign the properties to the class.and create single properties in aspx.cs page

something like

public MyClass MyClassObject

 {
  get { return myObject;}
  
 }

 Then I can handle the class (for example i can keep that class object in view state.insted of keeping variable in view state.)

Dim Display As Control = Me.LoadControl("~/Controls/TransactionBox.ascx")

Display.ID = "TransactionBx"

End Sub