Question

What I could use to solve the problem: C#, ASP.NET, Javascript.

2 Webpages: Index.aspx – Work.aspx.

Index.aspx: Stadistics and info about the work they’re going to do once they hit the link that redirects them to Work.aspx.

Work.aspx: Start working with clients.

So, what I need to accomplish is a single instance of Work.aspx. Because while they are working with Work.aspx, Index.aspx is still open (they need to research data and stuff), but if they hit the link for Work.aspx they get to open another instance and that’s not what I want.

I don’t know what’s the best way for accomplishing this since all Ive found on Mutex is based on winforms. (if it happens to be that you have some link with info for handling mutex in a webform then I may be able to start there, but I havent found that yet)

Any help would be very much appreciated.
Thanks.

EDIT.
Work.aspx is a popup, so employees have both webforms open at the same time.

Answer 1

If I understand what you’re asking, you might try using the Hyperlink.Target property to always open Work.aspx in the same named window.

<asp:Hyperlink runat="server" ... NavigateUrl="Work.aspx" Target="work" ... />

Update in response to comment

they trigger a few things in order to populate Work.aspx with the info they need …

What you need to do is “remember” the state of Work.aspx server-side, e.g. by storing state data in Session (or somewhere else: e.g. a database). Then each time Work.aspx is requested, render a version with the appropriate state.

What I can think of right now is: When they open work.aspx for the first time. Set a Session variable to true. And every next time they hit START-WORKING again, check that session variable beforehand to know if they are allowed or not. Were you refering to something like this Joe?

I think they should always be “allowed” to open a new Work.aspx. After all, the user may have closed the previous Work.aspx window, and you won’t know about this server-side. You should always allow the user to “start working” – but display Work.aspx with the most recent state, which you’ve saved somewhere server-side (e.g. Session).