If you're into automated generation of data manipulation UI, then you must check out BLinq, written by Polita Paulus of Microsoft, at http://www.asp.net/sandbox/app_blinq.aspx?tabid=62

In short, it uses DLinq to generate a DAL, and then builds simple ASP.NET pages using GridView and DetailsView Controls (developed by Polita herself), to manipulate all of the tables from the database.

In my opinion, it serves as a great prove of concept for the whole ASP.NET and Linq technologies, as the fastest RAD tool for web application development.

Just build a database, and in an eye Blinq, you have a way to manipulate it through web app.

I find it great. Aren't you?

Watch this antique commercial, of a nutty chocolate snack-bar that was a huge hit at the eighties in Israel

I've had to take a lot of jokes about having a name of a snack-bar, but now I look at it with a lot of nostalgia ...

Here is a bad image of the snack-bar, acquired from the video:

Have fun ...

I've came across a funny post at Paul Stovell's Blog, about the evolotion of error messages in the Visual Studio Family Products.

http://www.paulstovell.net/Posts/Post.aspx?postId=2e18c36c-83ce-4483-8129-37f2cd9fcf26

Give it a shot, and read the tech stuff there, too. Quite a good one and I recommend it.

Thanks to Oren for pointing that out for me.

I'm developing some Two-Way Databound ASP.NET Server Controls lately, and I use some reflection in order to do the actual binding and unbinding.

During my work, I found out something strange.

Let's consider the next code segment:

bool? myNullableBool = true;
Type t = myNullableBool.GetType();

You'd think that t == typeof(bool?),

but actually, t == typeof(bool)!!!

So it seams that the Nullable<> types in c# 2.0 aren't "real", in the sense that instances of those types, actually are of the corresponded "regular" type, but has some kind of an overload on the = operator, that allow null as a input value.

It's not the behavior that I've expected, and so it caused my a lot of headaches during the development of my binding/unbinding methods.

I guess it is documented on MSDN, but I got to excited about the nullable types feature, that I've started using it without fully understanding it.

So my lesson for today is: study well, and stay out of hell.