[fr0man]

You might want to work through some ASP.NET MVC tutorials using your language of choice before jumping into Django or Rails. That will give you an easier entry point to learning MVC (which is quite different conceptually from ASP.NET Webforms). Then you can read through some language tutorials and decide whether you prefer Ruby or Python. ASP.NET MVC is nearly identical to Rails minus ActiveRecord, so you could easily jump from there to Rails development. Though if you're going to be developing on a Windows box, Django is much more of a first class citizen there than Rails. I also had a ton of deployment problems trying to deploy Rails to a Windows server. Just a tip: no matter where you dev, don't try deploying to a Windows Server machine unless you have to. Linux plays much more nicely with both Django and Rails.

Edit: Anyone care to explain the downvoting? I'm not whining; I'm just genuinely curious. I thought my post was fairly informative, and I tried to give love to both Django and Rails. I had problems going from C# Webforms to Rails, partly because I was a noob, partly because I was trying to learn a new framework (Rails), a new language (Ruby, which is very different from C#), and partly because Ruby and Rails both have some configuration issues on Windows. It's nothing you can't overcome, but added all together it made for a very steep entry to becoming a Rails developer. The OP sounded like he was coming from a very similar situation to me.