Arka,
I think it's sensable to have a child browser window share the same
sessionID as the parent, otherwise it may break the logics of some web
application utilizing popups(people stores user logins, etc. in Session
variables).
If you really want to run 2 web page in different context, I'll suggest you
to dynamicly generate a prefix and store the prefix list in cookies and
page-specific prefix in a hidden field, so you can call by
Session["page1_var1"]. If the page loads and in cookies you see "page1"
already, you should set the prefix for current page to page2 and then append
to prefix to the cookies. This will ensure it works without breaking logics
of other parts of the web application.
I believe there may be some more convienent way to work on this, but in my
insufficient knowledge this is the way to do.
Regards,
Lau Lei Cheong
"Arka" <ar***@caramail.com> ???
news:11**********************@f14g2000cwb.googlegr oups.com ???...
Hi,
I have an asp.net application and I need to have a link on one page
that starts another "instance" of my app.
I tried with Javascript windows.open and with hyperlinks target=_blank
but both opens a new IE on my App but with the same sessionID...
Ths only solution I see is to open a security hole to allow vbscript to
launch "IExplorer.exe MyURL" on the client when clicking on my link
!!!!
Is there no better way to do this ?
I am using IE 6.028 SP1 + some QXXX Patches / Win2000 and IIS6 on the
server.
Thanks,
Arka