Control type names passed to globalInvoke and globalUpdate don't resolve for UserControls that use CodeFile in their directive.


If you are using the CodeFile attribute (instead of the CodeBehind attribute) in the @Control directive of your UserControls, in order for the globalInvoke or globalUpdate methods to resolve the control type you pass to them, the fully qualified type name of the assembly dynamically generated at runtime must be provided. Of course, the name of this dynamic assembly name is unknown by the developer and this approach simply doesn't work.


peanutbutterlou wrote Jul 7, 2010 at 2:09 PM

Better control type resolution will be implemented for the v1.0.2.0 release of the framework.

wrote Feb 13, 2013 at 2:48 AM