Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:
You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.
To me it sounds like you need to use javascript to achieve what I believe you are asking. "window.location" might do it. If you need ASP.NET to handle it perhaps have your button pass window.location to the query string?
ASP.NET is server side code after all, and it appears like what you are requesting is dependent on the client.
After initially thinking the same thing when I thought it was an inter-frame thing, it's become clear JavaScript won't work in this case, since the Custom Explorer Bar is not implemented as a webpage within the IE DOM - it's implemented as a separate COM object within Windows.
If he implemented it as a Frame, he could manipulate the contents of the main window, except if the window was on a different domain (which is likely) then you would run into your domain sandbox problem (Access Denied, in JS)
So if all the pages required were on the same domain, you could just write a left hand nav panel. But if any of the pages are out of domain, then you'll get security problems - saying that you might still be able to get some read-only values, such as .location.
After having a look at custom explorer bars, they look like a really crap half-solution, since to do anything halfway decent he's going to have to write (essentially) a Windows application to tie the two things together.
To me it sounds like you need to use javascript to achieve what I believe you are asking. "window.location" might do it. If you need ASP.NET to handle it perhaps have your button pass window.location to the query string?
ASP.NET is server side code after all, and it appears like what you are requesting is dependent on the client.
When the user clicks on a button within MyWindow I want to know what is in the main window so I can decide what/how/when to do some processing.
Request.Referer is not populated.
Bum. Bit of a puzzler then. I haven't used custom windows, so not sure what functionality they offer. A quick look at MSDN reveals that they are implemented as separate COM objects, so you will indeed have to COM into IE.
Not sure I get this, ok you have a webpage displayed in the main window, and you press one of your custom menu options, which then takes the page to your custom handler page (so that Request.Url is now your page rather than the original page) - and from here you need to know what the previous page URL/address was in order to process it in some way? Is that it?
And Request.Referer isn't populated?
If you open IE and then do View>Explorer Bar>Search then a side window is opened next to your main window.
Imagine that instead of the search window it was MyWindow
When the user clicks on a button within MyWindow I want to know what is in the main window so I can decide what/how/when to do some processing.
As regards what is not contained in Request.Url, we are using our own Explorer Bar menus (that can be easily setup - see MSDN) but when we launch a page from that then Request.Url contains our explorer bar webpage rather than the page from the main window, e.g. www.google.co.uk
Not sure I get this, ok you have a webpage displayed in the main window, and you press one of your custom menu options, which then takes the page to your custom handler page (so that Request.Url is now your page rather than the original page) - and from here you need to know what the previous page URL/address was in order to process it in some way? Is that it?
You want the actual text contained within the Address bar of the browser? So you are going to COM into IE/FF/A hundred other generic browsers with no defined COM API in order to get that?
What exactly is in the Address bar of the browser that isn't in Request.Url ?
I appreciate the comment about multiple browsers but this is only a small project and guarenteed to use Internet Explorer v6.
As regards what is not contained in Request.Url, we are using our own Explorer Bar menus (that can be easily setup - see MSDN) but when we launch a page from that then Request.Url contains our explorer bar webpage rather than the page from the main window, e.g. www.google.co.uk
I have used Google, couldn't find anything so posted here. Also the Request.Url object does not provide that information as I have tried it after seeing it mentioned on a few websites.
I think the underlying issue seems to be the Address Bar is within the COM arena........
You want the actual text contained within the Address bar of the browser? So you are going to COM into IE/FF/A hundred other generic browsers with no defined COM API in order to get that?
What exactly is in the Address bar of the browser that isn't in Request.Url ?
I have used Google, couldn't find anything so posted here. Also the Request.Url object does not provide that information as I have tried it after seeing it mentioned on a few websites.
This is the page I always refer to when I need this kind of functionality...
Will have a look, thanks.
I think the underlying issue seems to be the Address Bar is within the COM arena........
Leave a comment: