My ASP.NET is a little rusty, but I did a fair bit upon a time. Bottom line, if you drink the Kool-Aid and do it their way, it's not so bad. If you try to tra

My ASP.NET is a little rusty, but I did a fair bit upon a time. Bottom line, if you drink the Kool-Aid and do it their way, it's not so bad. If you try to translate some other web stack concepts into ASP.NET, you're going to be very frustrated. Specific things to understand: Page cycle. Critical. ASP.NET events. Viewstate (nice if you don't lean too hard on it) App_Code/App_Data directories. Master pages (heh) Also MS has some funky way of handling javascript that is non-standard. You add a javascript handler in Page_Load or something like that. I wasn't doing JS back then so can't tell you more. If use a lot of JS you'll want to understand how the IDs for ASP.NET controls are generated. I tried to use a UserControl in a project and wasn't satisfied, couldn't get the different pieces to see each other and talk to each other correctly. Try before you fly. I'd recommend finding a source of examples and starting there. (P.S. If anyone else is curious like me about why someone would want to move from RoR & Django to ASP.NET, read the first post on n00bnotes, it's explained there.)