Session variable from .aspx page to .cs class?

[Torisen]

I've worked with classic ASP and know C by way of Java and a few simple web services, at my new just they have a .net 2003 web app and I've been able to help fix up a few things as I'm getting up to speed, but I have one place where I need to get a value from the .aspx page into the validation code in a C# class.

I don't want to include the value in the method call, because I would then have to include the data in every subsequent method call (a couple dozen, maybe more) for each validation until I hit the save at the bottom.

I set a session variable in the .aspx page and watched it get set in the debugger, and know it's there for the other code, but when I try to reference it in the C# method, I get the build error:
"The name 'Session' does not exist in the class or namespace ..."

I can't find any code examples to figure this out, can anybody help me with this?

Thanks in advance,
Josh

[honeymonster]

HttpContext.Current.Session

[wwb_99]

Though you really should create an object that wraps these variables and place that in the session as well as ship that around to your various methods.

[Torisen]

Thanks, by the way, HoneyMonster. This led me to what I needed.

[Lashman]

Which was what?

[Torisen]

The actual code I used was:

intCompanyID = Int32.Parse(System.Web.HttpContext.Current.Session["session_intCompanyID"].ToString());

and it works like a charm.

[wwb_99]

But what happens when System.Web.HttpContext.Current is null?

You are better off passing parameters into a method and not having this dependence upon a singleton floating around. Yes, I learned that the hard way.

[honeymonster]

^^^ listen to what W says (our own resident W; who is a lot more informed and speaks from experience; not from belief).

[wwb_99]

Who says I'm not divinely inspired?

[Torisen]

yes yes, this I know, but the way this app works (I didn't write it, I just got hired to finish it) is to call the code behind with a validate method to validate a data element against their (often conflicting, I'm finding) business rules. On success, the parameters are then passed to a second method for another element or rule, and so on until the whole dataset is verified. There's a couple dozen methods that pass these parameters on and I'd have to add this data element to each, they're not always called in the same order, depending on what's updated, and one misstep could cause them all to fail. A single floater (which is only required because now they want to ignore one of the business rules completely) seems like the lesser evil. (and definitely less of a maintenance headache)