G
Garry Hall
Guest
Being Matt's "pingee", I'll chime in. During the development of the subclassed RadForm controls, we did identify that there would be a problem if customers wanted to use different Telerik versions in different projects. We have a theoretical solution to this, but have yet to implement it. The result would (hopefully) be that each project would need to run its own AVM, as once an assembly is loaded into the CLR, this is the assembly that will be used for the life of the session (a .NET limitation, not an AVM limitation). There would also possibly be no need to provide a redirection in the app config file, but that is only on paper at the moment. This work is currently scheduled for a TBD future release. It was not implemented in 11.6 for a couple of reasons: 1) There had been no feedback from the ESAP that anyone was suffering from this; 2) It was identified relatively late in the 11.6 release cycle, and given there was no feedback identifying a need, the dev time was instead spent on other things. If you see this as a pressing need, Product Management needs to hear this, in order to prioritise this work higher. Please use the appropriate mechanism in order to let them know. However, until this is addressed, we would appreciate you "kicking the tires" of the OERadForms, to iron out any issues with them. This would make the future implementation of a per-AVM OERadForm a little easier to maintain.
Continue reading...
Continue reading...