Just tested another control from the CuteWebUI library: Uploader from the "Simple Upload withProgress" sample to see how it will behave. On a simple ASPX page it works just fine but again when loaded asynchronuously using an ASCX user control the Uploader kicks out the same "Object reference not set to an instance of an object" error in a javascript popup. Actually if you just drop any uploader control on an ACX control which is async loaded, the Uploader button won't work unitl a "dummy" Uploader control is placed in the ASPX page with a style="display:none;". This is a usual workaround for all type of FileUploaders on the market incl. ASP.NET, 3rd party etc. This workaround makes the Uploader to start function as expcted, ie: the file browse window pops up but once again when a file is selected and the async uploading starts it ends up with the same error message like above. Could someone at CuteSoft have a look at this please? I'm not about to say how bad the library is, in fact looks great but it is a pain in the *** to debug something with this kind of generic error message. It would be more beneficial to rather throw an custom exception to aide with the debugging than just letting an unhandled exception being thrown.

We would like to purchase license but until this test doesn't come back with a positive result it would be money thrown out the window as we load all our pages as ASCX user control in an async fashion.

Many thanks,

Ben