sherman.woo

RegEx Tracer

Puckboy — Wed, 17 May 2006 08:20:00 GMT

Found a regular expression debugger tool called RegEx Tracer from CodeProject. Will have to try it out when I have time.

Visual Studio 2003 Tips and Tricks

Puckboy — Mon, 05 Dec 2005 22:30:00 GMT

MSDN:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsintro7/html/vxurfvisualstudio70defaultshortcutkeys.asp

Shaykatc's WebLog
http://blogs.msdn.com/shaykatc/archive/2004/03/04/83993.aspx

Natural Ergonomic Keyboard 4000

Puckboy — Fri, 02 Dec 2005 19:33:00 GMT

I have tested this out at a local store (obviously very briefly, without a computer attached). Looks like Microsoft has fixed some of the issues I had with the previous generation of keyboards, and have finally come out with a keyboard that can be a match for my (two) beloved MS Natural Keyboard Pros.

See Brian Dela's post here.

ASP.NET Page Life Cycle Overview

Puckboy — Tue, 29 Nov 2005 19:44:00 GMT

http://msdn2.microsoft.com/en-us/library/ms178472.aspx

Init Event Does Not Fire for Any Control

Puckboy — Sat, 26 Nov 2005 05:52:00 GMT

This one is a little weird.

Normally, attaching an Init event handler to a control is pretty straight-forward. Standard, typical stuff. However, we encountered a situation where the init event handlers were not firing for any control on our page.

The page is actually an MS CMS template, but really they are just ASP.NET web pages. Usually these templates inherit from System.Web.UI.Page, but we decided to do the 1.1 "master" page trick by inheriting from another class "BaseTemplate", which in turn inherited from another class "BasePage" which finally inerits from the base Page class.

I don't think this chain of inheritance is the cause, but I do know that the problem is a result of "order of events". From what I understand, the init events in our set up were occuring too late. In other words, the Page Load event had already fired, so the control Init events can't fire (even though their Load events do...); something like the child's OnInit getting called before the page's OnInit event.

The solution was to use the OnInit attribute in declaritive code like this:
<asp:Literal id="myLiteral" OnInit="myLiteral_Init" ... />
The Init method would have to change from the normal "private" to "protected".

An explanation as found in the news groups:
the OnInit event of the Page is too late for registering event handler for sub control(added statically)'s Init event). Because all the static sub control's Init event is fired when they are being added into the parent container which is before the Page's OnInit function. You can try using the suggetion on registering the event handler in aspx page inline.

Worth noting: BUG: Imperatively Wired Control Event Does Not Fire in Visual C# .NET Web Application (http://support.microsoft.com/?id=314965)

dotnet MONSTER... cool.

Puckboy — Fri, 25 Nov 2005 22:20:00 GMT

My first post... came across this site while searching for some other informaiton. In the process, I found that they offer free blog space, and they use Community Server (blog portion is formerly .TEXT). Neat.