I tried a quick work around by saving to Session state instead of the DataCache. This failed as well, so I quess there must be some serialization going on there as well. And in hind sight, even if it did work, some of the providers for session state such as
the SqlProvider definantly will serialize objects if used.
The only thing I can think of, is to save the file stream every time cmdAdd_Click is called. So instead of saving the HttpInputControl to the DataCache, you serialize the file itself. First, this would work for both 1.1 and 2.0 versions of DNN. And as an added
benefit, the entire serialized object will not be saved, just the file itself, so there may be performance gains this way.
None
0 Points
76 Posts
Re: DNN 4.0 Module upload issue
Nov 15, 2005 03:12 PM|dstgroup|LINK
The only thing I can think of, is to save the file stream every time cmdAdd_Click is called. So instead of saving the HttpInputControl to the DataCache, you serialize the file itself. First, this would work for both 1.1 and 2.0 versions of DNN. And as an added benefit, the entire serialized object will not be saved, just the file itself, so there may be performance gains this way.
DST Consulting Engineers