Comments on: Ruby on Rails for a .NET Developer – Part 1

By: Free IT Consultation in the DC Metro Area | Emad Ibrahim

Free IT Consultation in the DC Metro Area | Emad Ibrahim — Fri, 27 Jun 2008 12:43:43 +0000

[...] platform (yonkly.com), a couple of contracts for a couple of clients and not to mention all the learning, blogging, writing and speaking that I have been doing. In the process I have learned a lot [...]

By: Emad Ibrahim

Emad Ibrahim — Tue, 29 Apr 2008 01:05:59 +0000

@Jonatha thanks. It’s a little challenging being that everything is different, OS, tools, platform, syntax, language, etc… I am lucky I have been playing with asp.net mvc because the transition is a little easier.

@Antonio great tips. thanks…

One thing that sucks so far has been the documentation.

By: Emad Ibrahim

Emad Ibrahim — Mon, 28 Apr 2008 23:05:59 +0000

@Jonatha thanks. It's a little challenging being that everything is different, OS, tools, platform, syntax, language, etc... I am lucky I have been playing with asp.net mvc because the transition is a little easier.

@Antonio great tips. thanks...

One thing that sucks so far has been the documentation.

By: Antonio Cangiano

Antonio Cangiano — Mon, 28 Apr 2008 09:42:28 +0000

Hi Emad,

welcome to Rails-land! :) A few things to consider:

1) When creating a project, you can specify a “-d mysql” option in order to have the config/database.yml file filled with MySQL specific information, given that the current default is SQLite.

2) You don’t have to manually create the databases. Simply run: rake db:create:all from your project. For a complete list of available tasks, run: rake -T

3) You may want to consider starting to use migrations, rather than defining the tables directly through SQL or MySQL tools.

Best of luck,
Antonio

By: Antonio Cangiano

Antonio Cangiano — Mon, 28 Apr 2008 07:42:28 +0000

Hi Emad,

welcome to Rails-land! :) A few things to consider:

1) When creating a project, you can specify a "-d mysql" option in order to have the config/database.yml file filled with MySQL specific information, given that the current default is SQLite.

2) You don't have to manually create the databases. Simply run: rake db:create:all from your project. For a complete list of available tasks, run: rake -T

3) You may want to consider starting to use migrations, rather than defining the tables directly through SQL or MySQL tools.

Best of luck,
Antonio

By: Jonathan

Jonathan — Fri, 25 Apr 2008 15:09:22 +0000

Good for you! I admire that you’re stepping out of the ‘.NET’ zone for a bit to try something new. I promise you won’t be disappointed Rails.

I’m actually trying to convince my company to switch from .NET to Rails. It’s going to be tough, but going to be SO worth it in the end.

Good luck!

By: Jonathan

Jonathan — Fri, 25 Apr 2008 13:09:22 +0000

Good for you! I admire that you’re stepping out of the ‘.NET’ zone for a bit to try something new. I promise you won’t be disappointed Rails.

I’m actually trying to convince my company to switch from .NET to Rails. It’s going to be tough, but going to be SO worth it in the end.

Good luck!