I realize that this post is probably misplaced, but I didn't see an obvious place in the silverlight forums either.
I have an ASP.Net site using Infragistic controls and it works beautifully (thanks Infragistics!) in all normal browsers (Chrome, Firefox, IE).
However, when I try to view this site in a Silverlight WebBrowser control (OOB), I get javascript errors. When I track down the errors, it is when using the $find command to try to get a reference to an Infragistic object. For example:
var bmdropdown=$find("<%= BookmarkList.ClientID %>");
Returns an object that I can manipulate in IE, Firefox, & Chrome, but it returns NULL under the Silverlight WebBrowser control.
For context, $get operations work under both.
Here is the BookmarkList definition:
<ig:WebDropDown ID="BookmarkList" runat="server" DisplayMode="DropDownList" Width="180px" ClientEvents-SelectionChanged="ChangedBookmark"></ig:WebDropDown>
Additional Info:
The <%= BookmarkList.ClientID %> correctly resolves in both cases to WebSplitter1_tmpl0_BookmarkList
While I don't understand the underlying problem, on the surface this doesn't look like an Infragistics problem. Here is the resolution I posted in the silverlight forums (http://forums.silverlight.net/p/238644/592299.aspx/1?p=True&t=634515172719235238)
Thank you for your response. I actually "solved" this accidentally.
Based on some installation problems I was having on a server, I was messing with the "Enable Content Expiration" option of the IIS 6 HTTP Headers configuration page. I noticed that when I set this to 1 minute instead of never, my page would successfully load every minute, but refreshes would fail within that minute.
I changed the server settings to "Expire Immediately" and now the page works every time. Again, this page has always worked in Chrome, FF, & IE. It just failed in the WebBrowser control.
I'm a bit ignororant of Web Technologies (old-school C programmer forced to evolve). After reading up on Content Expiration, it doesn't appear that there will be any functional impacts--just efficiency (basically it won't cache anything). Can you tell me if there will be any adverse consequences to turning this option on? And do you know why this is necessary to get the WebBrowser control to work?