Re: Web Application Timeout - C# Discussion Boards

1-Dec-10 5:48

Hi All,

We have a web application that timesout when the user is in a textbox typing. If the user moves out of the text box however, the timeout period appears to be reset. Is there a way to prevent the web application timing out (reset the timeout period) when the is typing in a textbox?
Our users access the web application using IE.

Thank you,
Mel

T M Gray1-Dec-10 5:51

T M Gray

1-Dec-10 5:51

What kind of timeout? Is it a session timeout? What is your code doing when the user moves out of the textbox?

MWRivera1-Dec-10 6:26

1-Dec-10 6:26

Yes, this is a session timeout.
There is no code that states if the user moves from one field to another, restart the timeout session time.
If I understand correctly this is the default behaviour of a session. Please correct me if I'm wrong. Any advice/help would really be appreciated.

Thank you,
Mel

MWRivera1-Dec-10 6:28

1-Dec-10 6:28

Maybe someone knows of a way to renew the session on keystroke within a textbox?

Thanks

Dave Kreskowiak1-Dec-10 7:16

Dave Kreskowiak

1-Dec-10 7:16

That would take a roundtrip to the server and a refresh of the page. The default session timeout for IIS is, I believe, 20 minutes.

I think a better solution would be to create a very small frame in your page that refreshes itself every 15 minutes or just short of whatever your session timeout is.

A guide to posting questions on CodeProject[^]

Dave Kreskowiak

MWRivera2-Dec-10 3:47

2-Dec-10 3:47

Dave, thank you for your reply.

Are you suggesting I put a frame in the page and then within the frame put the textbox? Would I then be able to refresh the page through the frame when a character is entered in the textbox, therefore refreshing the session on keystroke?
The reason for this is that I want the session to expire if the user has no interaction for a period of time, but if there is activity including text entered in the textbox then I want the session renewed.

Thank you,
Mel

Dave Kreskowiak2-Dec-10 12:55

Dave Kreskowiak

2-Dec-10 12:55

MWRivera wrote:
Are you suggesting I put a frame in the page and then within the frame put the textbox? Would I then be able to refresh the page through the frame when a character is entered in the textbox, therefore refreshing the session on keystroke?

No, I'm not saying that.

I'm saying that you leave the Textbox where it is, not caring ANYTHING ABOUT IT AT ALL, NOT EVEN A SINGLE KEYSTROKE! Then the very small frame has a very small page that refreshes itself every so often, possibly 80% of the session timeout. That lone little page is enough to keep the seesion from timing out.

BUT, there is a problem. If you do this, the session will NEVER timeout so long as the user has that page in the browser. If they go home for the night, the session stays running for the entire time the browser is open.

MWRivera wrote:
The reason for this is that I want the session to expire if the user has no interaction for a period of time

That's what the session timeout is for.

MWRivera wrote:
but if there is activity including text entered in the textbox then I want the session renewed.

Web applications cannot handle this situation. If the user is taking longer than the default 20 minutes to fill in a page and submit it, the correct course of action is to increase the session timeout, but only if you consider the side-effects of doing so.

A guide to posting questions on CodeProject[^]

Dave Kreskowiak

MWRivera3-Dec-10 4:52

3-Dec-10 4:52

Yes, that could be a problem with the session not expiring as we would then be relying on the user to logout or close the browser.

I didn't expect that there would be no way of refreshing the session when a user types in a textbox.

I guess this is something I will have to share with my team and go from there.

Thank you for your feedback.

Mel

Execute And wait

JDM67631-Dec-10 5:08

1-Dec-10 5:08

I'm using the following code to run REGASM.EXE to register and create TLB files for some .NET assemblies. The output message indicates that the registration of each assembly was successful however since they are under an installation folder in C:\Program Files, the output message from REGASM doesn't show the full path of the assembly that was registered or exported as a tlb. It just shows 'C:\Program'. Is there any way to fix the output message so that it shows the full path?

private static bool ExecuteAndWait(string _FileToExecute, string _CommandLine, ref string _outputMessage, ref string _errorMessage)
{

    Process p = null;

    try
    {
        p= new Process();
        p.StartInfo.FileName = _FileToExecute;
        p.StartInfo.Arguments = _CommandLine;
        p.StartInfo.RedirectStandardError = true;
        p.StartInfo.RedirectStandardOutput = true;
        p.StartInfo.UseShellExecute = false;
        p.StartInfo.CreateNoWindow = false;
        p.Start();

        _errorMessage = p.StandardError.ReadToEnd();
        p.WaitForExit();

        _outputMessage = p.StandardOutput.ReadToEnd();
        p.WaitForExit();

        if (p.ExitCode != 0)
        {
            return false;
        }

        return true;
    }
    catch (Win32Exception _Win32Exception)
    {
        // Error .
        Console.WriteLine(&quot;Win32 Exception caught in process: {0}&quot;, _Win32Exception.ToString());
        return false;
    }
    catch (Exception _Exception)
    {
       // Error .
        Console.WriteLine(&quot;Exception caught in process: {0}&quot;, _Exception.ToString());
        return false;
    }
    finally
    {
        // close process and do cleanup .
        p.Close();
        p.Dispose();
        p = null;
    }
}

Jacob D Dixon1-Dec-10 5:32

1-Dec-10 5:32

One thing I see wrong is your don't need to p.WaitForExit() twice. The process REGASM.EXE will only exit one time.
Do it more like this:

p= new Process();
p.StartInfo.FileName = _FileToExecute;
p.StartInfo.Arguments = _CommandLine;
p.StartInfo.RedirectStandardError = true;
p.StartInfo.RedirectStandardOutput = true;
p.StartInfo.UseShellExecute = false;
p.StartInfo.CreateNoWindow = false;

p.OutputDataReceived += new DataReceivedEventHandler(p_DataReceived);
p.ErrorDataReceived += new DataReceivedEventHandler(p_DataReceived);

p.Start();

p.BeginErrorReadLine();
p.BeginOutputReadLine();

p.WaitForExit();

Then:

void p_DataReceived(object sender, DataReceivedEventArgs e)
{
      outputmsg += e.Data;
}

Edit:
Of course I just made the error and standard messages go to the same event. You could seperate them if you wanted.

JDM67631-Dec-10 6:10

1-Dec-10 6:10

Wouldn't you need some sort of delegate to do that though? Sorry, I'm still a bit green on C#.

Jacob D Dixon1-Dec-10 7:26

1-Dec-10 7:26

new DataReceivedEventHandler

That is the delegate.

JDM67631-Dec-10 8:09

1-Dec-10 8:09

Thanks. It's still works and it's still doing what it was doing before. Smile | :)

The output passes back a string chopped of path where the tlb file was saved.

ex: "C:\program "

It should bein the following format: C:\Program Files\<app fold="">\<datafolder>\<dllname>

Jacob D Dixon1-Dec-10 8:33

Re: Execute And wait [modified]

1-Dec-10 8:33

Wait a second... Is the REGASM.EXE cutting it off or is it only being cut off when using the Process code?

If you ran the REGASM.EXE from a command prompt does it still cut off the c:\Program?

JDM67631-Dec-10 9:49

1-Dec-10 9:49

Jacob D Dixon wrote:
Wait a second... Is the REGASM.EXE cutting it off or is it only being cut off when using the Process code?

If you ran the REGASM.EXE from a command prompt does it still cut off the c:\Program?

I checked the command line I was passing and I was inadvertently prepending an extra full path of regasm.exe. Not sure why but it was still registering and creating the Tlb. I took off the extra regasm.exe and started getting the following error:

RegAsm : error RA0000 : The name of the type library cannot be specified for assemblies containing embedded type libraries

What I need and haven't figured out how to do is to add double quotes around to full path of the dll and the full path of the destination tlb because one of the folders in the path is "Program Files".

The command line should look something line this:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe "C:\path\to\dll\mydll.dll" /tlb: "C:\path\to\dll\mydll.tlb"

Ok.. I fixed it. Smile | :)

This is what I needed.

string szCmdLine = "\"" + szAssemblyPath + "\"" + " /tlb: \"" + szTlbPath + "\"";

modified on Wednesday, December 1, 2010 3:58 PM

Jacob D Dixon1-Dec-10 11:05

1-Dec-10 11:05

Awesome! Glad it is working for you.

Dalek Dave3-Dec-10 5:35

Dalek Dave

3-Dec-10 5:35

Well Spotted.

------------------------------------

I will never again mention that I was the poster of the One Millionth Lounge Post, nor that it was complete drivel. Dalek Dave

CCC League Table Link
CCC Link[^]

Luc Pattyn1-Dec-10 6:06

Luc Pattyn

1-Dec-10 6:06

JDM6763 wrote:
_errorMessage = p.StandardError.ReadToEnd();
p.WaitForExit();

this sequence doesn't make much sense: ReadToEnd returns what is currently available without waiting, so waiting for the process end after that is meaningless. One way to fix things is first wait for end of process, then ReadToEnd on both streams. Alternatives with events or extra threads would allow to capture (lots of) output while the process is still running.

Smile | :)

Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum

Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.

modified on Wednesday, December 1, 2010 12:34 PM

PIEBALDconsult1-Dec-10 8:08

PIEBALDconsult

1-Dec-10 8:08

Perhaps this[^] might be of some use?

JDM67631-Dec-10 8:14