|
|
We have FLASH using the .NET remoting system. We were running it with .NET 1.1
for years and things worked fine...we need to move to .NET 2.0 and make some
other changes and when we did that for some reason our FLASH movie, who's first
call is a remoting call to a login function returns the dreaded "Error opening
URL http://.../gateway.aspx"...this is the call that doesn't actually get
trapped by any AS error handlers...it just appears in the output window when it
finally craps out 10 seconds or so later...
Strange this is that as soon as we make another call after reloading the FLASH
piece, it works perfectly from then on out...
I'm not positive that this is a result of moving to .NET 2.0, but the
application is largely unchanged from the .NET 1.1 app and all other calls work
flawlessly...I suspect that somehow the .NET dll isn't able to accept the first
call for some reason, then by the time we make the second call, its in memory
waiting for the next request...after a while, we can duplicate the error, but
only after a while.
Anyway...not sure if anyone has a solution to this one...I've seen similar
problems, but this is pretty darn impossible for us to figure out...
Thanks.
|
|