Greg Robinson's Blog

I report it, you decide

Click Once

Custom Authentication in Windows Forms

DataBinding Stuff

Favorite Links

My book contribution

My Book Reviews

My Personal Life

Richmond, VA .NET Users Group

Smart Client Stuff

What I am reading

September 2004 - Posts

Potential .NET opportunities in Richmond, VA

I am aware of a possible VB.NET, Windows Forms position in Richmond, VA, starting sometime around the first of the year.  This position is not a definite to date.

I am also aware of a C# position this is a definite.

The ideal candidate (for the VB.NET position) should have 2+ years experience with VB.NET Windows Forms, 2+ years experience with SQL Server and have an advanced understanding of OOP. 

The ideal candidate for the C# position is the same, except of course 2+ years experience with C#

Full time employee preferred, though a contact consultant will be considered.

Please send your resume to greg@cds-am.net if interested. 

Please pass this along to anyone you know who may be interested. 

 

 

 

Best Kept Secrets in .NET

Just got my copy of this book from Apress to review.  I read the first chapter last night.  I learned a few new tricks that I will use right away.

Formal review of the book on it's way.

 

Editing a control that is not databound

Lesson learned this week.  We have a form with controls bound to a DataTable.  When editing a field in the DataTable that was not bound to a control, we tried to do the following:

1) Get the current DataRow

2) with the current DataRow, set the DataColumns new value: DataRow.Item("my_datacolumn") = "new value"

This never worked. 

So we then added a control on the form and bound it to "my_datacolumn" .  We hid this control under another control so the user would not see it.  We turned off it's TabStop so a user could not tab into it. 

At run time, when we wanted  to edit the field we would set focus onto the control, set it's text property then set focus to another control.  Why did we do this?  To force the validated event to fire on the control to databinding would push the new value to the datacolumn.  

This works though it's a hack. 

A better solution?

Use a DataRowView instead of the current DataRow.

When a DataRow is in the middle of an edit  transaction and you want to update a field at runtime, and the field is not bound, update the DataView, not the DataRow.

Thanks to Mark Boulter at MS for this tip.

 

Career advise

In case you missed this one:

http://www.lhotka.net/WeBlog/PermaLink.aspx?guid=b28971dc-ac4b-4494-8a21-7a5105a39b07

Rocky wrote a great blog on what it takes to be successful in our field.  He took the words right out of my head!

 

APress has asked me to review some .NET books

http://www.apress.com/

Too cool.  I get to read some new .NET books, review them and interview the authors. 

One of the first books is by the author of the first Object Oriented Programming book I ever read; "Doing Objects in Microsoft Visual Basic 6" by Deborah Kurata. 

 

My Latest Favorite Site

My new favorite site:

http://www.buymeabeer.com/

All kinds are welcome

 

More Posts