Session variables, Query String Question

[checkai]

Here's what I have....

*about 5 different web projects...
*one project is solely for login purposes...
*I need to pass that login information to all of the other pages...however, i don't want user id's in the query string, and I'm not sure if all users' cookies are enabled....

is there a way to encrypt a query string?
can session variables be passed between projects?

thanks,

DLC

 

[bigfoot]

Are you using ASP.NET, or classic ASP?
I know classic ASP, but I am learning ASP.NET fast!

I have the same problem, and I am using Session variables to pass the info. Session variables are active for the whole browser session. If you need more, then use Application variables. I have a few applications that I need to talk. If I can not get them to pass the data in session var's, then I will take someone's advise and write the info to a database. You could also write them to an XML page and read from that. It's really easy since the DataSet object reads and writes XML as it's schema.

I hope this helped, or I gave you some things to search on. I use Google.

Gary

 

[checkai]

I am using .NET to create my web app...i am very unfamiliar with using XML...would that be a secure method to pass user id information?

thanks,

DLC

 

[Zarcom]

May I ask why you have a separate project for the login process? If your thinking reusability why not just create a user control. I just see no reason for having separate projects since separate projects usually mean separate web sites. If in fact you need separate web sites then the session in site is different. You would need to send the data across somehow using a querystring or form variables.

If you look in the last few days here in this forum passing variables around has been discussed in a few topics already and there is some great info there.

That'l do donkey, that'l do
Mark
If you are unsure of forum etiquette check here faq796-2540

 

[bigfoot]

Mark, can you or someone else go into more detail about this subject. We have an Intranet that has a folder for every department, and different applications (forms, reports, etc). I was going to make a new project for each project because the pages were HTML.

Is this a bad thing, or should I create the whole site in VS?
Our designers use Dreamweaver MX, and they may be doing some of the HTML pages.

What is bad about different applications? And do I need to make an application folder for each or just copy the app over to any folder on the master web server.
They are created on my XP development machine.

I guess I need to plan ahead I think.
I also need to deal with old ASP code, as I can not just re-do the whole thing at once.

 

[Zarcom]

<snip>new project for each project</snip>
Not sure I understand what you mean here. What I have done for smaller projects, simple sites with a bit of data access in them, is to have my designer design the site and build it. Then where the data access needs to be he calls up an I-Frame with the address set to the page that I have built. I just keep a simple design white background simple form, and the background of the site itself shows through the I-Frame.

The thing that is bad about different applications is that they have trouble talking to each other. The sessions are the same if you have the apps simply in separate virtual folders for the same site in IIS. However, production servers may have the apps set up in different sites on the same server, depends on your configuration, and the Session is not the same for the apps then
(Correct me if I am mistaken here guys)

Nothing wrong with separate folders to separate departments either it helps keep things tidy. I am not sure what advice to give you since I don't know the situation at all, perhaps you could expand on that a bit. It sounds like the same type of thing just changed around for departments in which case I would have one app that display's different bits for the different departments.

As for old school asp. .NET and the old stuff can run together on the same server so try to break it into managable parts. Take one slice convert to .NET (if thats what your doing) then replace the old asp stuff. The thing is to try and break it up so that that different parts you work on can stand alone. I just find it easier that way even though you can get the two to play nice sometimes.

That'l do donkey, that'l do
Mark
If you are unsure of forum etiquette check here faq796-2540

 

[bigfoot]

When you say one application, what is it exactlly are you saying. That it is one VS project? I have a couple of projects/applications that I wrote in VS.

They don't need to talk to each other, only in session vars.

 

[Zarcom]

Yes 1 VS project, not solution but project. Like I explained above you need to make sure the applications are running under the same site in IIS to be able to share session data between them.

Did this help at all. I am kinda lost right now as to what exactly it is your asking. soo.. ya.

That'l do donkey, that'l do
Mark
If you are unsure of forum etiquette check here faq796-2540

 

[bigfoot]

Ok. Let me try to explane myself. We have an intranet. It has many folders with html pages. I may have 10 applications going. Some for sales, some for accounting, and some for dataprocessing. Each application is a VS project. I should not have any trouble doing this, right?

Also, does each subfolder that the projects live in need to be virtual folders marked as applications, or can I just mark the main folder and all the others be part of the same project?

What is a solution? Would that me my whole Intranet?

Sorry for the newbe questions, but I am new to the .net world. But I am soooo hooked.

 

[Zarcom]

Nope don't see any problems. Your just running many intranet apps across your network yes?
Each VS project does need it's own virtual folder that is marked as an application.

Glad you enjoy our world, I also find .NET programming enjoyable.

That'l do donkey, that'l do
Mark
If you are unsure of forum etiquette check here faq796-2540