Exequiel. That was also my approach but Colin seems to prefer the other approach.
Maybe its a question about control. I think your approach gives more control to the uppgrading process than Colins If anything goes wrong using Colins approach then it could be the old code but also the combination of an old rails 2 structure and configuration and rails 3. A drawback with your approach is that there are many depedents between models and controllers in my application and these could be hard to manage in a syepwise process. Exequiel, did you have any problems with that ??? In addition my controller does not follow the proposed structure that is generated in a rails 3 scaffold with respond_to do |format|, which will be corrected with Exequiel's approach Maybe a good compromise would be to follow Colins advices about source control system and a testdriven approach but then uppgrading it stepwise as propsoed by Exequiel??? On 2 Maj, 21:13, exequiel <efu...@gmail.com> wrote: > I upgraded an app from rails 1.2.3 to rails 3. First, I installed RVM > with both Rails versions (gemset: rails1.2.3 and rails3.0.0), I > created a new Rails 3 app from scratch and I was adding the > controllers (helpers, views, etc) one by one. It was a lot of work but > I was sure that all things were working OK. > > When you do that, you can refactor/update/remove....etc and you'll be > sure you didn't touch the working app. And you need some source > control system (svn or git are OK), just in case you do something > wrong. > > Exequiel. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
