It seam like every one (now including me) is posting excitingly about the new preview of ASP.NET MVC.

Probably to get traffic or whadever.

Most of those goes like "I usually do not do this, but hey- here's the link".

Justice Gray's post is different.

btw, as you are all excited about it, I'd use that to point you to something quite similar, more mature, that lets you "easily build MVC based applications in ASP.NET with routing, intellisense, and total joy, not to mention that it runs on .NET 2.0 " - that would be the MonoRail thing, preferably (by me and a few others) accompanied by AspView.

And since I didn't put the MVC p2 link here, I won't link to MonoRail and AspView. After all, if you're reading this, you probably have those links in your favorites ...

Reading this post from Phil Haack made me jump a little. Oh no, I said, Please don't let the clean IMvcFramework become clumsy.

Ayende has ranted about it better than I would.

Now I see that Phil has issues with ABC as well.

The answers for the ABC problems he shows there are cumbersome. In order to gain "flexibility", you end up polluting your API with "CanSupportCrap" methods, etc.

So, to recap:

1. Phil, (probably inspired by Framework Design Guidelines) claim that using ABC over Interfaces is better as it won't cause breaking changes.
2. Ayende points out that the breaking change won't be to the end user (as in - developers who uses the framework) but rather to the framework maintainer (who works hard anyway and should know his way around), and to framework extenders (again, should not whine about those 'breaking changes'). As an aside, Ayende also brings up the sealed/internal/non-virtual rant.
3. Phil admits to the weaknesses of ABC, just by showing an even weaker way of overcoming them.
4. I recap all that.

Please Please Please keep IHttpContext in place ...

This weekend I've had to pleasure to attend the altnetuk conf in London. This has been quite an amazing experience. I have really liked the way it has ben organized into open-spaces, and I just wish I could've split myself to four, so I'd be able to be at all of the sessions (the F# one was greatly missed ...)

I have met great people, have discussed exciting things, and had a lot of fun.

Most of the people referred to me as "the MonoRail guy" which was quite amusing, as I am only the creator of AspView (which in turn is a shameless idea-and-code ripoff from Brail), and I have very little to do with the actuall coolness and usefulness of MonoRail ... I do hope though that I did manage to address pepole concerns regarding MonoRail, and the Castle Project as a whole.

Interesting (however not surprising) moment:

On the panel dealing with MVC frameworks for ASP.NET, about 25 people were around the table. When people who are actually using MonoRail/ASP.NET MVC for commercial production environment, only 4 have raised their hands. however, all the others said that they wish the could have done that, and the only reason they do not, is the reluctance from their bosses/clients.

After being told that MonoRail would not make his dreams come true, Dylan Beattie have answered:

"MonoRail would not make my dreams come true. It would however, make my nightmares disappear"

Brilliant.

Well, According to Scott Gu we'd be able to download the binaries Next Week,

I can't wait to put my hands on that, and start finding the possibilities of this framework in conjunction with MonoRail.

Actually, it's not much of a challenge, but it is a catchy title.

Or is it?

Anyway, that's the details:

I'd kindly ask all of you ASP.NET Ajax wiz guys (and gals), to supply me with a simple UpdatePanel thing.

What should it do?

I want to have a webpage, based on this template, that on dropdown change, will go to the server with the selected value in the dropdown, and update the data (table) with some crap, based on the sent value.

You can leave the actual data retrieval to a simple method returning an array of string array, or you can go and implement a CodeSmith/DAAB/Whatever based supercool data access code. I would ignore it anyway. I want the Ajax stuff.

Now, to the why.

I am doing that MonoRail presentation at Microsoft's Israel IVCUG (Israel Visual C(#/++) User Group) next week. I might be showing some demos, and I want to be fare when I show a comparison to WebForms stuff, and not come up with a crappy code and say "ha ha", but show something that one of you, my-dear-readers-who-actually-uses-asp-net-ajax-for-living, wrote, and is considered a good example.

Also, I'm lazy. Seriously. Creating a presentation takes a LOT of time and effort, and I do not have much of the first, and rather avoid much of the later.

So, please do send me that code, to my-first-name at that-blog's-hostname.

thanks.

I've posted an article to CodeProject about building my Google Ajax Search Enabled Homepage.

So, go there, read it, comment it, vote for it, tell your friends about it, print it and glue it to your forehead, whatever you think is appropriate.

Unless you didn't like it. In that case, you shouldn't do anything. why bother ? :)

I have loaded a new homepage, and used a little of the Google AJAX Search API to make it interesting. Actually, I'm using it now as my browser's default homepage, instead of google.com

Not only that, but I have documented the process of making it, and have sent it to codeproject, to be published, as my first contribution there, in hope for more to come.

So, please leave your impressions, eiether here or in the codeproject article (I'll post the addresss once it will be up).

As said in the title, ASP.NET Ajax (aka ATLAS) is maturing and reached Beta 1 stage.

I haven't being too mush into it lately, since I've been under the impression that though Microsoft's ASP.NET Ajax library was very rich and had many features, it also suffered from many childhood problems, including too many js errors, and a huge .js script to download.

Now, it has an official name, and a beta release, and it's maturing. The .js was split by functionality, release and debug version of the .js are present, prototyped classes have replaced the closure based ones, and it's better for me cuz I find it easier to *overload* behaviuors when needed.

So try it out and read what Scott Guthrie has to say about it.

Since nowadays I'm more into MonoRail over Brail than into Webforms, I guess that the Core package is what really intresting for me, and I'll try to combine it with AjaxHelper from MonoRail. I hope to report on the matter shotrly.