Okay, I've dug a little deeper and now believe that the client profile
can be supported with just a single assembly and one breaking change.
The breaking change would be that users would need to change this:
<system.web>
<httpModules>
<add
name="ar.sessionscope"
type="Castle.ActiveRecord.Framework.SessionScopeWebModule,
Castle.ActiveRecord" />
</httpModules>
</system.web>
Into this:
public class Global : System.Web.HttpApplication
{
public override void Init()
{
base.Init();
SessionScopeWebModule.Init(this);
}
}
Internally, the web module class would be generated at runtime through
IL emission. Is anyone aware of any showstoppers with this approach?
Is anyone aware of issues with medium trust, signing, or anything like
that?
Does this technique appeal to people more than the last two?
Patrick Earl
--
You received this message because you are subscribed to the Google Groups
"Castle Project Development List" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/castle-project-devel?hl=en.
