Transfering info from one web form to another (c# ASP.Net)

omb0wyn5ehpij9 · 20-04-2009 03:05PM #1

Hey all,

i'm doing a project in college at the moment. On one web form I have the user entering a number. I need to use this number in a different form and I can't work out how to do this, even after hours of googling :rolleyes::o

Can anybody out there help me?!

Thanks

Creamy Goodness · 20-04-2009 03:27PM

you could achieve it by using sessions,

something like this may help http://msdn.microsoft.com/en-us/library/ms178581.aspx

store the number entered by the user in a session, then when you need to use it again, retrieve the value from the session and input it where ever ya need it.

Sean^DCT4 · 20-04-2009 07:27PM

If you are passing just an integer to another web form then I would suggest using the QueryString. Request.QueryString["whatever"].

Example:

Button Click Event on page calls:

Response.Redirect("APageWithQueryString.aspx?MyPassedVal=123");

On your APageWithQueryString.aspx page you can retrieve the value using

int myPassedInValue = Convert.ToInt32(Request.Querystring["MyPassedVal"]);

Note: MyPassedVal is the querystring field. 123 can be any string you want

comer_97 · 24-04-2009 10:45AM

you could also use a HTTPContext too. They have made it very unintuitive.

John_Mc · 24-04-2009 10:48AM

comer_97 wrote: »

you could also use a HTTPContext too. They have made it very unintuitive.

What do you mean?

comer_97 · 24-04-2009 09:05PM

John_Mc wrote: »

What do you mean?

Do you mean how it is unintuitive or how to use a httpcontext?

HTTPContext stuff

As for it being unintuitive, why doesn't .net embrace the humble html form? It's worked well for years and works well, why change it?

Once .net gets to the presentation layer it is a shambles. It's use of css is terrible and trying to do anything clientside is really complex, unnecessarily so.

Hopefully XAML will change this but I've yet to use it professionally.

Giblet · 24-04-2009 09:09PM

You can use CSSFriendly adapters, and the new MVC framework is pretty decent, doesn't rely on postbacks!

Still, there were some mistakes made initially, but they are trying to rectify them.

clearz · 24-04-2009 10:35PM

comer_97 wrote: »

why doesn't .net embrace the humble html form? It's worked well for years and works well, why change it?

You can use HTML foms perfectly easily by just using the HTML controls instead of the Web Controls

comer_97 wrote: »

Once .net gets to the presentation layer it is a shambles. It's use of css is terrible and trying to do anything
clientside is really complex, unnecessarily so.

You really have 3 different choices with .NET
HTML Controls
Web Forms
MVC
Each have their uses and misuses. But there is something for everyone and every type of site/application here

comer_97 wrote: »

Hopefully XAML will change this but I've yet to use it professionally.

XAML's only use on the web is with Silverlight and adds nothing new to plain old HTML pages.

Transfering info from one web form to another (c# ASP.Net)

Comments