I think august is cutting it a little close. I have no idea how much time you've already spent on it, so dunno if a rewrite in a diff technology is the way to go. And you can deploy RoR to IIS. If you want I can send you a white paper. THe idea is that you forward all the requests to a mongrel. I haven't had much luck with the FastCGI that the IIS team provides. It just doesn't want to do it for me. But using mongrels/thin does work for me.
When IronRuby then comes into its own you can always switch to run that app on IronRuby \ my 2c. Cheers Ivan On Fri, Jun 20, 2008 at 8:49 AM, Josh Charles <[EMAIL PROTECTED]> wrote: > Hello All, > > I have a Ruby on Rails codebase that is only partially completed. Due > to circumstances beyond my control, the production server must be IIS, > and there is absolutely no way to change this. Deployment is > currently due in mid August, basically two months away. My question > is this. What are the chances the IronRuby project will be ready to > handle something like this at that point in time? Should I basically > take what we have and rewrite it in something like ASP.NET MVC? > > I've spent sometime working and thinking about ways to make this > happen. My approach, which is probably terrible, was to take the > Web.Routing assembly in a regular ASP.NET application, create a > catch-all route and pass all the information to the dispatch.rb file. > Granted, I haven't actually got this to work, and this is probably a > horrible way to do this. > > In any case, with deployment two months away, I need to make the > decision now to stick with Rails, or make the switch over... > > Sincerely, > Josh > _______________________________________________ > Ironruby-core mailing list > Ironruby-core@rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core >
_______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core
