July - 2003 - Archives - Erik Porter's Blog

The HC Update

Thursday, July 31, 2003

Just a little bit on what I've been doing lately... Last week my gf and I went camping. Lots of good and absolutely horrible experiences. A couple highlights: I've seen it all now! Indiana rox! My car sux! I was one happy camper! Went canoeing (sp?). Do you think they're related? ;) There were lots of great views when we went hiking. This stuff reminds me of how much I love photography and would like to get into it (but not with the $2 camera from Wal-Mart) Two days ago, I gave my presentation “Getting Started with WindowsForms” at the

Filed under

| 2 comments »

More Bang For Your Data Acces Buck

Thursday, July 31, 2003

Adam gives a good tip on how to squeeze a bit more out of the DataReader. Great tip! *thumbsup* If you look at his code, you'll notice that you have to access the field you want by Index, which isn't exactly “programmer friendly”. The easiest way to work with it, is to use the GetOrdinal Method of the DataReader to lookup the Index for you. Under the covers, when you use the Indexer to access a field value by the field name, the Framework is calling GetOrdinal to lookup the Index and then accessing the field by Index, so it's

Filed under

| 0 comments »

Assembly Loading Info

Wednesday, July 30, 2003

Great entry from Suzanne Cook. <highlights> <highlight> <info> <![CDATA[In v1.1 and v2.0, Frameworks assemblies are unified. That means that the version of those assemblies that you request is ignored - you get the version that matches the loaded CLR. This only applies when the assembly is loaded by version - that is, by assembly display name, or static reference (AssemblyRef in the CLR metadata).]]> </info> <comment> <![CDATA[Holy cow! This is news to me. Very interesting and actually really cool. Great tidbit of information there! :)]]> </comment> </highlight> <highlight> <info> <![CDATA[However, do not rely on this behavior. You should still fully-specify

Filed under

GeneralNET

| 0 comments »

Edit and Continue Madness

Wednesday, July 30, 2003

No Edit and Continue in C# is all the madness now. The C# team has all kinds of other stuff they work on that is probably more important than E 'n' C, but I'm still with everyone that is all for it in C#. However, productivity has never really seemed to be the main focus of C#, so it makes sense that something that can help you save time not getting in there is appropriate. ;) I am constantly searching for reasons to use C# (other than translating all my demos), but alas...it appears Whidbey will help me reaffirm my

Filed under

Whidbey

| 2 comments »

Quick WindowsForms Tip

Sunday, July 27, 2003

Ok, I saw basically the same question posted twice over at GDN and I just don't understand. Instead of complaining about it, I'll post it as a quick tip. If you have a Form that needs to check a certain condition when it's loading and see if it should continue to load to close itself, don't bother. When programming, you should be thinking about every little drop of efficiency that you can squeeze out of your programs no matter how small. Don't get lazy just because it's not a big deal and won't use many resources. Do it right the

Filed under

| 0 comments »

WindowsForms DataBinding

Sunday, July 27, 2003

I'm in the middle of working on my presentation (yes, that's right, I'm not done yet...I'm a procrastinator and love working under pressure) and happened to have just blogged about Strongly Typed Collections and thought of something I had done in a project a while back related to DataBinding in WindowsForms. Even though it's extremely simple, this will hopefully show you that DataBinding in WindowsForms is extremely powerful. First off, create a new Form, slap a ComboBox in the middle and name it "cmbPeople". Then take the Collection I created in my last post called "PeopleList" and plop it into

Filed under

| 1 comment »

Strongly Typed Collections

Sunday, July 27, 2003

Darren and Robert having been talking a bit about Strongly Typed Collections and it's all good stuff, but what I'm a little lost on is I don't see any mention of inheriting from System.Collections.CollectionBase. This class already Implements IList, ICollection & IEnumberable. My theory is always...the less work, the better. CollectionBase is great and helps you implement Strongly Typed Collections really quickly. Here's a quick example. Public Class Person Private m_ID As Guid Private m_FirstName As String = "" Private m_LastName As String = "" Public Sub New(ByVal FirstName As String, ByVal LastName As String) Me.m_ID = Guid.NewGuid Me.m_FirstName =

Filed under

| 5 comments »