Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Web Application problems

Status
Not open for further replies.

bigfoot

Programmer
May 4, 1999
1,779
US
I have tried everything to get my apps to work.

What's the deal on deploying them to the web?

ok, so an application must be in a folder marked as a virtual folder with Create application clicked. So every web application I create must be in it's own folder off the root with it's own copy of web.config, and bin folder.

Now I can't share information (session vars) between the applications. All I want to share is user info - who is logged on to my intranet.

Can anyone please help me get this thru my head and put this problem to bed. I talked my company into getting VS2003, now I'm looking bad.

What's the real deal. And how do I use Project copy.
I haven't even had time to mess with the .exe application things in VS, been too busy with these web problems.

 
Been reading more...

So each project I create in VS is an Application unto itself. It is also called an Assembly. The reason it needs it's own folder marked with Create Application is because it is it's own entity, handling security, and private variables.

And that is why I can not use a session var, because it it private to each little Application Island.

OK, so how are you all doing it? Where is a common place that I can store the logged in user's name. Not in the global.asax file, that's private to each application.

Not in session, or application, that's private to each application.

I'm getting this little by little.
What boggles me is that what I think I know is a tiny piece of what I don't yet know, and don't know that I have to know.

I should coin that ;-)

Any and all help would be appreciated - a lot.
 
You could create a 'Parent' application, one controlling App for Logon purposes or the default page only for example, and then your other Applications underneath this, making them, in essence, all part of the same application and able to share the currently unsharable...

Rhys
Thought out... Maybe,
Opinionated... Probably
But it is only an opinion!
 
But then how much of the child app do I copy to the web? It seems to need it's bin folder and web.config files, and then it cry's for me to make it it's own app. If I could get past this, it'd be cool.
 
That works fine. You need to remember to copy the dll into the parent's dll folder.
 
Glad to help...

Rhys
Thought out... Maybe,
Opinionated... Probably
But it is only an opinion!
 
Hi Bigfoot,

If all you want to share is user info between your applications, why not use the database? You could create a separate table to store log on information for all applications and write to/access that table from each application.

laters
 
I thought of that. Tried that too, but what I am sharing is the user logon. I did not want to have to get it from each page. I used to get it from the main page then look up his/her serial number and full name from the database and pass it around in session vars for my reports pages.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top