I have recently integrated anthem.net into a module I developed for dotnetnuke.
I followed the instructions from this thread to do it, and it seemed to work fine.
http://sourceforge.net/tracker/index.php?func=detail&aid=1411848&group_id=151897&atid=782464
I was doing my testing in Firefox, and everything went as planned. When I tried testing in IE,
I ran into a big problem.
I have a listbox that has some items in it. I have a selectedindexchanged event added to
this listbox so that when a user clicks an item in the listbox, some text fields and checkboxes
are automatically populated.
I use an anthem listbox, and it's declared like this:
<anthem:listbox id="lstformFields" runat="server" AutoCallBack="true"
updateaftercallback="true"></anthem:listbox>
I also have an anthem linkbutton that updates the fields after a user has modified the values
in the fields. That linkbutton is declared like this:
<anthem:linkbutton id="cmdUpdateformField" runat="server" cssclass="CommandButton"
causesvalidation="false">Update Field Properties</anthem:linkbutton>
cmdUpdateformField has a click event associated with it in the codebehind to do the
actual updating.
When I click cmdUpdateformField, the code runs fine, and my fields are updated.
But when I go back to the listbox and select a different value, the
selectedindexchanged event should fire off again. Instead, IE just hangs there and
eventually, I have to kill the IE process in Task Manager.
While IE was hanging, I checked the IE process, and it was using 50% of the processor!
That CPU utilization persisted until I killed the process. This always seems to happen after
switching back between selecting an item a couple times and trying to click my cmdUpdateformField
button. Like I said before, when I'm in Firefox, this does not happen. After I click my update button
and then select a different item in the listbox, the selectedindexchanged event fires off fine,
and it populates my fields like it should.
I tried doing a simpler anthem.net implementation with another module where I simply
added two numbers and put the result in a textbox. I noticed the more calls anthem.net made,
each time, the processor utilization would increase along with the amount of memory that IE
was using. Eventually, it got to the point where IE locked up while using over 50% of
the processor. I tried replicating this on Firefox, and it didn't lock up. I even clicked
my "Get result" button repeatedly and rapidly, but I didn't get any lockups.
Has anyone run into problems similar to mine using anthem.net controls in dotnetnuke in IE?
Does dotnetnuke not like to play nice with things that require asynchronous calls/lots of
javascript? I really didn't know where else to post, and this was the only thread I could find that was
actively discussing anthem.net + dotnetnuke.