|
Rank: Member Groups: Member
Joined: 6/8/2007 Posts: 13
|
Hi,
I have just uploaded a section of my site which uses the AJAXUploader, but I'm getting the error about AJAXUploader not supporting Partial Trust websites.
Any ideas and suggestions?
I've already spoken to the server hosts, and they are not in a position to change the trust level.
Thanks
Craig
|
|
Rank: Member Groups: Member
Joined: 6/8/2007 Posts: 13
|
Ignore that message, i've found this post. http://www.essentialobjects.com/Forum/Default.aspx?g=posts&t=80Have you found a likely workaround yet? On another site, for a similiar control, they mentioned that adding it to the GAC sometimes solves these problems. Cheers
|
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,194
|
Hi Craig,
Thanks for posting your question here. Unfortunately we are not aware of any workaround for this issue. Adding DLL to GAC is generally considered a workaround for permission issue not because a DLL gets full trust as soon as it's GACCed, but because the default .NET permission settings give full trust to a GACed DLL --- so a GACed DLL gets full trust because of the default permission settings --- in a way similar to an ASP.NET application gets full trust under the default settings as well. When your host company changes the default settings that affect ASP.NET application, they may also change the default settings that affect GACed DLL permission settings, if they do that, then adding the DLL into GAC will no longer automatically give the DLL full trust. Beside, usually when your host company does not want to give you full trust to your application, they won't be happy to put your code into GAC either.
In practice, based on some feedbacks we have from a number of hosting companies, it's rather difficult to stay on partial trust. There are a number of reasons, one of the reason is most "controls" under traditional ASP application are COM based, they obviously require full trust to run and a lot of big application still more or less have those. Another reason is some commercial obfuscating solutions inject native code into the DLL (something similar to a DLL built with VC++, not VC#), and they require full trust to run as well.
Thanks
|
|
Rank: Member Groups: Member
Joined: 6/8/2007 Posts: 13
|
Thanks for the reply.
Uncle Bill rocks again then, making the small person spend more money with stupid updates :)
The only control i've found which works on Medium Trust sites is $400, and for a hobby site, i'm not prepared to spend that amount on a single control. Or more on a dedicated server.
Will just have to remove that functionality till sa suitable solution comes along.
Cheers
Craig
|
|
Rank: Administration Groups: Administration
Joined: 5/27/2007 Posts: 24,194
|
Hi Craig,
You may want to try uploading a rather big file with the uploader that you found claiming support medium trust. We looked into this issue quite thoroughly a while ago and it appears that Microsoft intentionally locked a key interface down and accessing that interface requires full trust. We have concluded without accessing to that interface, the control will not able to "stream" the uploaded files onto disk, instead it can only read the whole file as "one chunk" into memory and then write the whole file onto disk. This effectively defeats the primary purpose of the uploader control. We've seen controls that claim supporting medium trust but in fact it downgrades to nothing more than a normal HTTP file input element when using under partial trust, which makes it unable to handle big files.
Also, many shared hosting companies (probably most of them) run full trust for the reason that I mentioned in my previous post. So you may want to take a look of other hosting companies.
Thanks
|
|