The question is: How do you play with nvelocity in shared hosting environments where medium trust is a common standard?
As I mentioned in my previous post
, it's not so easy to go around it - even if we would like to disable CAS temporarily using the 'Mutex method', we have no permissions to do this ;).
The problem is mostly because of the ReflectionPermission required by NVelocity itself (this is the only way to instantiate objects referenced in templates).NVelocity project is dead since October 2003
, although we may download from sf.net svn repository sources imported 6 months ago from castleproject
. I'm not sure about this, but I think the nvelocity team is not going to take care of the project any more.
I know that some of you use MonoRails with NVelocity as a template engine - don't you have problems with partial trust? Don't you develop any modules for DotNetNuke with some help from NVelocity (I do ;))? Now every one 'good' dnn module has to pass the 'medium trust requirement'
, so the potential usage of NVelocity in dnn is rather small... :(
Don't you find it as a MS battle against different template engines? We may use heavy asp.net templates, because 'the asp.net engine is good and signed by MS' and we cannot use other engines, because 'it is highly recommended to work on medium trust' and so - we do. Of course we may ask our admin to specify for our app custom policy file
, but have you ever tried to do this?
12-13-2006 6:00 PM