May 18, 2009 at 7:40 AM
Edited Jul 28, 2009 at 2:42 PM
That was what I thinking of actually but it need to be designed in order not to have 2 codebases for the web project.
The issue is -as I see it- that DotNetOpenId assembly is directly referenced by Kigg.Web assembly. So even if we made another MembershipController that doens't use DotNetOpenId we still reference it and this might still raise the issue.
But here is my suggestion to you! what do you think if you tried the following:
- Remove reference to DotNetOpenId and remove its support totally from your local Kigg project. This will require that you'll update MembershipController and remove few other classes that depends on DotNetOpenId. You'll need to update Web.config too.
- Comment this line on HttpForm class under Kigg.Core.Infrastructure.Http:
ServicePointManager.ServerCertificateValidationCallback += (sender, certificate, chain, sslPolicyErrors) =>
You'll find it on the static constructor of the class
- Remove reference to System.UI.DataVistualization assembly on Kigg.Web (this is also another reason of breaking partial trust). Note that if you did this you'll need to update Web.config to remove handlers and modules related to this assembly.
Currently this is the list I figured out so far that might need to be tracked and resolved in order to support parital trust. However there might be other parts of the code that causes partial trust to fail. This might also be related to IoC that try to
resolve none public types or members of any Kigg types.
Let me know if you are going to apply it so that I can save sometime working on it. and based on your results we can decide where we need to move. If you think you might not be able to work on it, also let me know, I think I can schedule some time later
to work on it.
I think anyway we should discuss supporting partial trust on v3.0 it is important.
BTW, kigg currently also not working on High level of trust, it must be Full :o)