I'm just dipping my toes into server-side scripting.
The Global.asa file seemed really nice, but am I understanding correctly that the application onstart event is fired ONLY when the server is started/re-started or when the FIRST user logs onto an ASP application?
If that's the case, then all the changes I keep making to my Global.asa file are pretty useless, right? (which seems to be the case -- i.e., my pages are not using any of the new information). Code:
I have absolutely no idea how global.asa works. I've read through quite a number of articles and they're all fine and dandy but implementing it on my (first) ASP application just doesn't work. It's amazing how ASP.NET automates everything for you.
Anyway, I need to store session variables and I have no idea how to. I have no global.asa file, but I can declare session variables fine. So does that mean that somewhere in the ASP process, a Session_OnStart() method's already running.
If I create a global.asa file, I put it in the same directory with other ASP files right?
A global.asa file should contain the basic four application/session methods... and shouldn't really contain much code, unless I want to start a variable with a default value. True or false (I say true). Code:
I have one application folder containing all ASP code files. I want host multiple sites pointing to same code. Can I do this ? If YES then how I can assign diffrent global.asa to each application...
I am trying to write a sub that will delete a spreadsheet file created by the web user. THis is the code I have inserted into the global.asa file, but it is not working.
sub Session_OnEnd 'delete the temporary excel spreadsheet Set objFSO = Server.CreateObject("Scripting.FileSystemObject") objFSO.DeleteFile(Server.mappath("temp/<%=session.sessionid%>.xls")) Set objFSO = Nothing end sub
I have made sure that the temp folder has permissions set for the IUSR_machinename account to be able to delete files. I am running IIS 5 on a windows 2000 server.
I still have no clear idea of Application_OnEnd functioning on w2000 both Pro and Server. I have this sub in my global.asa which is supposed to save Application scope variables to a file. (then Application_OnStart will restore theses variables from the file)
It worked fine on local w98/PWS and on ISP NT4-Server/IIS4 To initiate Application_OnEnd and Application_OnStart for test purposes it was sufficient to re-upload global.asa Also Application_OnEnd were fired and registered by global.asa when shutting Windows down in a proper way.
On w2000 re-uploading global.asa does not trigger Application_OnEnd.Nevertheless it does trigger Application_OnStart Neither does Application_OnEnd work on shutting W2K down Is it a known behavour or I am having some anomaly? Perhaps w2k need a different syntax for Application_OnEnd?
my understanding was when IIS restarts that time when the first session is requested application_on Start is called. My session time out is 1 minute. after every session time out happens when the session is requested then it goes to application_onStart first. Isn't application on start just happens only when IIS restarts and first session requested.
Until now I've only seen VBScript to handle application and session events (e.g. Application_OnStart, Session_OnStart). Is it possible to do this directly in JavaScript or do I have to write VBScript proxies?
In Global.asa I have mentioned two sub routines 1> Session_OnStart and 2>Application on Start but both of them are not at all initiated when I restart IIS.
Please Tell me why is this happening, I have tried ever ....
I have a couple ASP applications running on my server (non .NET) I would like to be able to get a sum total of how many active sessions I have running. I can do this within each app individually as I can just use an Application variable and add/subtract as the sessions are created or deleted. I am trying to come up with a sum total of all sessions between the two (or more) apps running on this server. That way I can tell if it is safe to reboot the box without affecting anyone or not.
I'm trying to add a "user-verifacation" thingy to my site. my problem is using/accessing session variables.
all the tutorials say that the global.asa should only have the script tags (<script...> & </script>) and inside the script itself only have the application/session onstart/end.
I've created this global.asa file and put it in my site-root folder:
Is it possible to create a global variable from within a Sub so it is available to another function in the same web page?
I want to tap a database for information within a Sub procedure but end the Sub after assigning the values to global variables.
Simply defining the variables as global (outside the Sub) and setting them to empty strings does not do the trick. The variables don't persist after the Sub procedure is complete.
i have a logon page, i create session variables for every person who logs on, but when their session times out, i want to redirect them (or have a popup window) that tells them that they have been logged off, but i have no success.' global.asa:
<script language="vbscript" runat="server">
Sub Session_OnEnd Response.Redirect "loggedout.asp" End Sub
</script>
but it doesnt work, i set the timeout to 1 minute, and i lose the session variables, but i cant seem to redirect them to the loggedout page!
I am making a testing project to get my hands on ASP classic. I have a question about Global Scope Variables e.g in PHP we make a file where we define some values which are global, e.g site URL, site title etc, and then we can include that in any page to get that value.
I read Global.asa works very good in fact we dont need to include that in every page to use stuff within this file. I read some examples but they are mostly about functions in this file. Can anybody guide me please how to define variables in Global.asa to use them sitewise?
I have a piece of vbscript that returns the user logged on to the machine. it is as follows:
<script language="vbscript"> Set WshNetwork = createObject("WScript.Network") stringUser = (WshNetwork.userName) 'store username in variable stringUser document.write("Username: " & stringUser) 'output value to web page </script>
Now I need to use the value of stringUser on other pages of my asp application for database queries, form values etc. I have tried to call stringUser from inside <%..........%>, but it doesn't recognize the variable. Everytime I try to output the value from wthin asp code, it just appears as blank space. Any ideas?
I am trying to run a Session_OnStart Script based on a Session variable that is created on a .asp page. The problem is that when I reference the Session in Global.asa It has no value but it has a value on the .asp page level. Is there a certain way that I have to reference a Session in Global.asa?
What I have is somthing like the following:
Sub Session_OnStart If Session("NIS")<> "" Then Run The Routine End If End Sub
Based on the above the routine does not run because Global.asa does not seem to get the value of Session("NIS").
I am using IIS 6.0 and am trying to use application variables to track uasge. They work fine as long as there is an active client but about 20 minutes after the last activity they are reset to the default values declared in the global.asa file.
I'm building a web app with a lot of ASP files which I'd like to split out into several different subfolders. However, I noticed that application variables that I set up in my Application_OnStart event sometimes survive switching to a different folder while at other times they do not. I am relatively new to ASP so I'm not sure if I'm doing something that inadvertently unassigns these variables.
One thing I kow I'm not doing is explicitly reassigning or unassigning them.My other option is to assign them in a default.asp or some other generic file that I replicate in all my folders and include in the entry point asp file to each folder,but I'd rather avoid the redundancy so as not to complicate maintenance further.
can I put together an object (not too big, just a small array or something) and chuck it in an Application variable or are there better ways to do this? Sessions are okay if it's a better alternative to Application but I'd rather skip cookies if I can.
I would like to know what are the Advantages & Disadvantages of using Application variables in an ASP page. In my application I would like to store some physical paths from database to application variables.
I'm in a dilemma whether to hold this values in application variables or in server side variables in an include file. Please help me with this..
I have initialized some session variables in Global.asa for our web application. But these session variables are returning null values; it is was working fine before; Recently we have rebuild our servers.
Please let me know if anyone of you have some idea?
users login and can navigate an administration area, however, at random (it seems) when you click on a link to navigate to another spot in the admin portion the application variable used to denote the user as an admin is getting changed, and therefore load the homepage because it thinks you are not logged in. any suggestions? need more info?
I've got two domain names sharing the same IP address that use ASP VBScript If I set a session variable with domain 1, it is only available for domain 1 - this is correct? If I set an application variable with domain 1, the app variable is sharing across all domains using that IP address - this is correct? This is the behavior I am seeing and I want to make sure that my server is set up correct. I especially want to make sure application variable behavior is correct.
Has anyone worked with Application variables in an array format? I need to create a list of 40 items using some sort of persistant array. I can do this with a DB, but in this case, it would not be efficient.
I did a few tests by trying to pass an array to an Application var, but can't seem to get it back.
<% Dim MyArray(39) 'populate the array Application("myArray") = myArray %>
then on another page, I tried
<% Dim myArray(39) myArray = Application("myArray") 'loop through the retrieved elements %>
This doesn't seem to work.. anyone did something similar with good results?
i would need to know if i can permanently modify the content of the global.asa file.
I am writing a web log in form that enables users to change their password (i dont need much security, this is more for practical purpose so i use application variables), these passwords are defined in the Application_OnStart() event but i would like to be able to change them without having to manually rewrite them.
I want to store the link of the page that each user of my web site visited so it can help me to personalise information for each user depending on the pages visited.I don''t know what kind of variable should I use.
If I understand well, a Session variable is deleted when the session end so when a user close the browser and then reconnect to my web site, the session variables used the first time will be deleted and I can''t keep track of the pages visited.Same thing for the application variable except that the variables will be deleted when the application stops.
I intend to use application variables to control access to editable blocks on an intranet site. There are about 300 blocks currently and that may grow to as many as 400 as time goes along.
Using the scheme I am thinking of an application variable will contain the username of the person currently editing a block. Is there a way to "destroy" the application variable so it no longer occupies memory or is this anything to be concerned about? I don't plan to place much more than a 20 character string into the variable.
What are the best methods for using global constants and variables? I've noticed that many people put all global constants in a file and include that file on every page. This is the best way of doing it - is it not? Once the application has loaded the page it is cached and is immediately available for other pages.
With global variables - the best thing to do would be to use application variables - so long as there weren't too many declared. Is there another (easy) way of using global variables apart from using application variables?
I'm using application variables for a web based sales tracking application. I use the variables for stuff like connection string, database name, etc. I store the values in a asp file that is included in a login page. The assignments are in a procedure that I then call on the login page. This is done everytime a user connects to the login page.
what's happening to the variables? Are they being overwritten everytime a user accesses the page? I'm not checking for the existence of the variables. I just call the routine everytime the page is accessed. I know the values are shared for all users but, I was wondering if I should check for the existence of variables? Will it free up resources? Should I be using locks?
