If you have not heard the Waterfall method of software development is coming back strong.  Check out the Waterfall 2006 conference taking place tomorrow.  (For those who are stiull using BlondeStar, this conferce is on April first.  The folks at BlondeStar can help you get there.)

If you still feel that Agile methodologies are better then perhaps you would prefer the upcoming Test Driven Development seminar in Boise, ID.

Today I found out that I will be attending TechEd 2006 in Boston.  Thanks of course to my new employer Pets Best Pet Insurance.  I am looking forward to seeing many friends again and checking out the latest and greatest technologies.  Look for me at the Windows Workflow Foundation and other WinFX sessions.  I will probably hit an IIS 7 session or 2 as well.  Of course I will probably spend a fair amount of time in the cabana area also.

If you are going to be there and would like to say hello in person then lets meet up.

Time is nearing for the first Boise Code Camp.  I will be doing 2 presentations on DotNetNuke and several others will be presenting a lot of other great material.  I put a lot of effort in getting door prizes for the event.  We are close to having enough prizes that most attendees should go home with something.  Of course the session material is the most valuable aspect, but winning a copy of Visual Studio Team Suite with MSDN wouldn't hurt either.

This week I started reading Professional ASP.NET 2.0 Security, Membership, and Role Management by Stefan Schackow.  I can't recommend this book enough.  Stefan is a great guy as well.  I had opportunity to meet him on a couple different visits to Redmond.  I wish I had this book 2 years ago when I started looking at the Membership and Role API's in .NET 2.0.  (Yes, I was looking these things 2 years ago.  They were announced at the PDC in Oct. 2003).

Today I found a bonus nugget of goodness I had to share that is indirectly related to ASP.NET 2.0 security.  On Page 429 Stefan explains why all the SQL objects in the Microsoft SQL providers for .NET 2.0 explicitly reference DBO as the object owner.  (ex. dbo.aspnet_Memberhsip)  It turns out that SQL 2000 takes a performance hit if the object owners are not explicitly declared in stored procedures, views, etc.  The performance hit is significant enough that Microsoft did a QFE on ASP.NET 1.1 SQL Session state.  I had no idea and I figured many others also were clueless about the patch for Session State as well as the performance issue.

Check out Todd Carter's blog for some more details.  It also includes a link to the .NET 1.1 Session State fix.