October 2004 - Posts
I just finished previewing a portion of Pro ADO.NET with VB.NET 1.1.
I must say that I began my reading with a little bit of scepticism figuring that this was yet another rehash of the MSDN Library. I am happy to report that I was wrong.
If you think that when it comes to ADO.NET you have been there, done that, got the t-shirt, then you really should pick up a copy of this book. The authors of Pro ADO.NET really take the time to teach the real nuts and bolts of using ADO.NET effectively and efficiently using concrete examples. Topics that are covered include ADO.NET architecture, Data Sets, Data Adapters, Data Readers, data relationships, performance optimizations, and much more. If you are looking for something to fill the gap that the MSDN Library or books that are near carbon copies of the MSDN Library have not filled, then look no further. This book is the one. If you ever wanted to take that next step and truly become an ADO.NET guru, I recommend adding this book to your collection.
Warning! Rant on whiners follows....
A colleague of mine sent me an article about the current hiring situation in the IT Industry, and it got me thinking. Man am I sick and tired of those who constantly blame others for them not being capable of finding work. I am sure you know a few them... You know the type...
The articled reaffirmed for me that as a consultant you have to be flexible and be able to adapt to market conditions. It’s the whole supply and demand thing. If there are not enough people that want your services, then find something else to do. If I have to become a teacher, construction worker, author, presenter, whatever.. You do what it takes. Hopefully you can find a demand for something that also fits your interests and passions. That is one of the things I DO love about this country (Canada) and I am sure the same can be said for the U.S. and others. I can be whatever I want to be and nobody can do a damn thing to stop me. Watch me!
We have two choices
1) Sit and feel sorry for ourselves and blame the rest of the world for us being out of work
2) Get off our ass and do something about it and take accountability for our situations.
I prefer the second option.
1) I have a web server control, lets say TextBox1 (System.Web.UI.WebControls.TextBox) declared (not dynamically created in code behind) inside a form on my aspx page
2) This control has the runat="server" attribute
2) Inside the PageLoad event I dynamically create another TextBox control (TextBox2) and set its Text property to some text "My New Text"
3) Still inside the PageLoad event I try set TextBox1 = TextBox2
4) Now that TextBox1 points to TextBox2 I look at the value of the Text property on TextBox1 (in the Watch window) and see that it is equal to "My New Text"
5) Great so far... Not so fast. When the page gets rendered TextBox1 does not contain the string "My New Text"
6) HOW COME????