Are you using the latest version of monorail now? If yes, you should inherit from Castle.MonoRail.Framework.Views.Aspx.PageBase instead Page. There you'll find the ControllerContext and other useful properties.
But On May 24, 11:34 am, Jason Meckley <[email protected]> wrote: > OK, I see what's happening. I didn't know this even existed, or if it still > does. this feature is like duct tape and bungee cords to combine the two > frameworks. maybe it was designed as a way to get people to use monorail. I > find the two are distinct enough that there isn't value in attempting to > combine the two (webforms and mvc, not specific to monorails). My > conclusion, it might be possible, but it's not advisable. either embrace > webforms or embrace MVC don't try to marry the two. > > now, you could put together your own MVP framework for webforms, I've done > that in the past. the code still isn't as clean, but you can separate the > view from the logic and allow for easier automated testing. -- You received this message because you are subscribed to the Google Groups "Castle Project Users" 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-users?hl=en.
