So why exactly do we want to move away from Controls to MVC?

Funny, check this post on From handling by Scott Guthrie. Why exactly do we want to move away from the ASP.NET Control model to MVC? To write more code? Even creating a form becomes harder. Wasn’t MVC designed to display… Models? I might be to tired right now to understand this. But I can’t see a clear reason for me to go to MVC Form handling. Everything described was implemented together with LINQ to SQL(or Entities) in 10 minutes, with some generated classes(the LINQ stuff) and 20 lines of HTML and ASP.NET controls, and another 20 lines of boilerplate C# code. Yes I tried it.

I’m missing the clue. Are you still on track? Correct me if I’m wrong, but isn’t making this model development once again more sophisticated? I can see the purpose of MVC for large amounts of data. For a year now I’m writing notes to myself on how to create a DSL for generating this model out of Sitecore. But in ALL my notes, I’ve never mentioned form data. And the funny thing is, in this example you can only use 1 specific url to post your data too.

I don’t want to to Sitecoreish, but one of greatest things about Sitecore is that I can place my forms anywhere and reuse in on any page… I’m getting more unsure where Microsoft has designed the MVC framework for. Scott Guthrie says at the end:

Important: If you don’t like the MVC model or don’t find it natural to your style of development, you definitely don’t have to use it.  It is a totally optional offering – and does not replace the existing WebForms model.  Both WebForms and MVC will be fully supported and enhanced going forward (the next release of ASP.NET WebForms will add richer URL routing features, better HTML markup/client-side ID/CSS support, and more).  So if after reading the above post you think “hmm – that doesn’t feel natural to me”, then both don’t worry, and don’t feel like you should or need to use it (you don’t). 

Let’s say it in another way: I’ve been interesting in the MVC model since the first moment. I hoped it could improve productivity for you guys out there, writing div’s and lists on daily base. With the identical data. So far it seems to be only designed for Database driven applications, similar to phpMyAdmin, but less flexible. That’s not where I was looking for. Hopefully Scott gives us a better impression next time, right now I’m completely unsatisfied with it.

For those who mention that MVC will help us in test driven approaches. You’re 200% right. But… a test driven approach can only succeed when you create software to reach requirements. You can’t write a Unit test in part x of the application when a Unit test in part y of the application tells you the opposite. One of those will fail, certainly. The requirements of our customers are quite clear in general: we want flexible websites which can be controlled from a CMS. So far that seems to be impossible. So a test driven approach doesn’t make sense at all.
Some recent news from our R&D department proved me that I’m not 100% right in this post: we’re trying to be as less dependant of the HttpContext as possible. We’re working on ways to let Sitecore run outside of the HttpContext. No ETA’s and product announcement from me, just to inform you, that we take your requirements(even when it are quality or development requirements) serious.

You might think I’m to critical, guess I’m. But I’ll give MVC, when it will be released, another serious change. Our R&D team believes, like I do, in the pattern itself. We have to look further into it, how and under which circumstances we can support it once released. That will definitely be a nice challenge.

Apple is not always better than Microsoft *Updated*

It’s funny, these days people are extremely pleased about the products from Apple. I’m absolutely happy with the usability of the iPhone, I like my iPod and I’m still asking Michael Seifert(our CEO) if I can get the first Sitecore Macbook Air ;). Enough commercials. I’m a fanatic Microsoft user. Most likely you are as well. Sometimes I like it, although I’ve got my doubt about usability and release management. We’ve seen enough of that with the .NET 3.5 SP1 release.

But why for god’s sake, can’t Apple manage it to make iTunes a usable application on Windows? It’s crazy. A company so much focused on usability creates a slow unusable application with a huge memory footprint. Porting your application settings from your previous installation to a new one is a hell. And than the installer. Everyone who has to install Quicktime, iTunes or Safari is used to it:

apple update

My god, 77.25 MB’s? And now only 31.80 MB? I lost clue. Even more annoying: A while ago I decided not to install Safari. Wrong, total mistake. You get triggered all the time(sometimes on a daily base) if you want to install this browser. NO!! Ask me only once, don’t be Googlish(you know with their ugly toolbar in every open source installation).
Finally after the installation above, I received the following message:

apple restart

So, Apple, who’s always critical about Windows, can’t even create an installer which doesn’t have to restart? Although I have to give them one credit… my iPod survived a trip in the washing machine :). Sorry for my dirt, but it seems like commercial companies of this size can’t score a positive figures on all sides. And, that’s even worst, this is nothing new, they don’t seem to care, otherwise it was fixed long ago.

Updated: thank you commenter for updating my spelling, I always welcome people to let me learn from my mistake. Unfortunately my commenter is the kind of person who accesses a public computer and doesn’t use his real email. So I’m unable to thank him. Sorry!

64-bit server but still running on Sitecore 5.3

There seem to be a couple of issues with some libraries referenced in 5.3 when you run those libraries on an 64-bit environment. A while ago I heard about a trick which would allow you to run IIS in 32-bit mode, even when the OS is running on 64-bits. Today a partner called me with the exact same question. So I’ve redirected this person to the knowledge base from Microsoft: How to switch between the 32-bit versions of ASP.NET 1.1 and the 64-bit version of ASP.NET 2.0 on a 64-bit version of Windows

I haven’t found any time to test it. So all experiences are welcome!

Update: The partner just contacted me and told me it’s working. Of course both them and we don’t recommend such a solution. But in some cases you simply have no choice. Thanks for sharing.