Why can’t this just work the way it’s supposed to out of the box?
So here’s today’s dilemma (which I’ve solved exactly once for each project I’ve done because once it’s done you don’t have to redo it which makes me think ‘gee… maybe it should be this way to start off with’). When you have a form on your page and want to submit it and get a result via Ajax the results are being displayed on a new page, not in the output div you specified. Read more
Session state is a funny thing. It works really well. But if users don’t stay active, they’ll lose their session. That can make for some really strange problems if session isn’t used immediately. Of course session can be checked for, but that’s a hassle. It would be easier to simply log users out before their session expires. Read more
Wow… I’m just watching this video about how the Model/View/Controller design pattern is going to be implemented in ASP.Net and VB.Net. As many of you know, I enjoy working on and with Ruby on Rails. RoR is entirely based on the MVC design pattern. It’s surprising to me just how similar the ASP.Net implementation of it is.
Considering the benefits of MVC, it’s surprising that Microsoft hasn’t implemented it so rigorously before. Nonetheless, I’m glad to see that they will finally be releasing it. As to the title of the post, the MVC architecture makes a LOT of sense in terms of the web. When we look at the market penetration of VB.Net and ASP.Net versus RoR, it’s clear who the winner is. We, the developers, are!
I don’t really think that Microsoft implementing MVC poses any real threat to RoR. In fact, Ruby on Rails may actually benefit from more people knowing about and being comfortable with it.