Erik Lenaerts

Do, or do not. There is no try. - Yoda

June 2007 - Posts

Upgraded to Community Server 2007

After a small delay and some outage, we finished the migration of dotnet6.com to the Community Server 2007 release.

We changed the comment moderation settings to review. So, be patient when adding comment as the blog author will review it and accept it first. This way we hope to fight against the spam dotnet6 was suffering from.

The changes in CS 2K7 towards Google will hopefully affect our ranking as wel.

ASP.NET Tooltip control

We regularly use an advanced tooltip control for web projects hence this ASP.NET Server control. It is based on the LGPL licensed freeware code of walter zorn.

For your convinience I wrapped it into an ASP.NET server control. Basically you can create DHTML based tooltip controls with lots of features. From an ASP.NET point of view it is very easy to use:

  1. Create a reference to the com.dotnet6.tooltip.controls dll.
  2. Drag one of the controls onto the web page
    1. TooltipImage
    2. TooltipHyperlink
    3. TooltipImageButton
    4. TooltipLabel
  3. For the TooltipImage, you can set the defaultImage to : small_blue like in the figure below

The nice part of this control is that you don't need to bother with the Javascript aspects, all javascript is aranged via the Webresource HTTP handler (learn more about it here).

 

Watch more samples here:http://www.walterzorn.com/tooltip/tooltip_e.htm

Download the source code here (.Net 2.0/C#/VS 2005)

Download the release version assembly

ASP.NET single submit button

Dimitris, a colleague here at MSP, recently create a slick new ASP.NET Server control. The control is in fact a button with one additional behavior; it will disable itself after you've clicked on it. This behavior is very interesting for sites where the posting of the form may only be done once.

Since ASP.NET is based on HTTP, forms can easelily be submitted more than once by the user when they click repeatetly on the submit button. For the webserver, requests will be handled as if they were comming from mulitple browsers.

So, basically the click event handler will be executed multiple times which is bad for a submit button that's placing an order. Hence this little control.

The DisableButton control will -supprisingly - disable itself (using client side javascript code) once it has been clicked. This way, the user can't accidentially submit the same form multiple times.

You can download the Visual Studio 2005 project here.

Release version of the assembly