Friday, June 01, 2007 11:47 AM
by
dodyg
Dynamic Web Conversion Notes
Link to Microsoft.Web.Scripting dll to:
- Extend Microsoft.Web.Script.UI.ScriptPage if you want to extend your dynamic page.
- Extend Microsoft.Web.Script.UI.ScriptUserControl and Microsoft.Web.Script.UI.ScriptMaster as you need.
To use your base classes, specify this in your web.config:
<pages compilationMode="Auto" pageParserFilterType="Microsoft.Web.Scripting.UI.NoCompileCodePageParserFilter"
pageBaseType="xxxPageBase"
userControlBaseType="xxxUserControlBase"
theme="default">
- If you are using Jasper, you extend from Microsoft.Web.DynamicDataControls.DynamicDataPage
Because these are dynamic pages, you specify your parent class in the <%@Page Inherits="xxx" %> statement or %@Control inherits="xxx" %
- The format to do call generic method in IronPython is [type]method(params) where type is T.
- I haven't found a way to do an explicit interface casting from IronPython. You cannot do this "(interface)object". It doesn't work.
- One thing for sure, doing IronPython development is definitely liberating. Python was my second love (check out these articles I wrote for evolt back in 99 before Python was cool). But my cup of tea is still Ruby and I can't wait for John to bloody ship it. My almamater (QUT) is also working on a Ruby.Net implementation.