Posts

A while ago I was writing a small history grid in one of our applications at work. It has a single HistoryItem object, which is fairly straightforward, something like this: Class HistoryItem { public int ID { get{ return _id; } } public DateTime CreateDate { get { return _createDate; } } public String Creator { get { return _creatorName; } } public String Note { get { return _note; } } } This was populated into a List<HistoryItem> and bound to the DataGridView directly:...

After I had changed all my extension methods to be functions and return a new object rather than mutating the self parameter, I changed them all back to be refs. Why? Well mainly because the library I am writing is in VB, and these methods are internal. VB supports ByRef parameters as the first param in an extension method, so no problems there. The only reason I was changing them so that they were C# compatible was so that I could test them with MSpec in C#....

I have been working on a project recently that involves a lot of work with Flags Enums. To aid with this I created a set of Extension Methods: Add(Of T as Structure)(self as T, value as Int) as T Add(Of T as Structure)(self as T, values() as Int) as T Remove(Of T as Structure)(self as T, value as Int) as T Remove(Of T as Structure)(self as T, values() as Int) as T Has(Of T as Structure)(self as T, value as Int) as Boolean HasAll(Of T as Structure)(self as T, values() as Int) as Boolean HasAny(Of T as Structure)(self as T, values() as Int) as Boolean Now the last 3 methods I am happy with - they are self explanatory and do what’s expected....

The Visual Studio Find and Replace dialog is often overlooked, and when parts of it are looked at (Regex searching) it often gets a bad rep. Sure it doesn’t implement all of the Regex syntax (non greedy search springs to mind), but that’s not to say it isn’t useful. For instance, I was working on some code that involved a Model View Presenter type style, but used Subroutines (void methods) rather than WriteOnly properties for brevity (in C# you can do a Set only property in 1 line, VB it takes 5)....

Multilining if statement conditions is bad. I was modifying some code and came across this: If String.IsNullOrEmpty(_selectedGUID) OrElse _ _selectedGUID = FeeAgreement.GetDefaultContractAgreementGuid OrElse _ _selectedGUID = FeeAgreement.DefaultPermAgreementGuid Then fgFeeAgreements.SetCellCheck(rowAdded, 0, CheckEnum.Checked) _selectedTitle = ag.Title _lastIndexRowSelected = rowAdded End If Which at a glance looks like this: Single Line If Variable Assignment Variable Assignment One person suggested that if someone had to do multiline the condition they could at least indent it....

While this is not something I personally would want to do, we (for whatever reason…) are to use MSTest at work (I think it is due to the whole “Its Microsoft, so it’s supported” argument). Now as no one else on the team does any kind of unit testing (serious), the only test projects we have are written by me, on the quiet before being told if I wanted to unit test then use MSTest....

Following on from yesterday’s post about separation on concerns and where to put some undefined logic for a multi state checkbox, I did a fair amount of research. I must say the Quince website is a good repository of UI Design Patterns, as is Welie. I couldn’t find anything like what I was after, which I guess means I shouldn’t be doing it this way? After a while a brainwave struck me: “Gmail lets you select things, how does it do it?...

When I am writing a winform in an MVP style, I often wonder how far to go with the separation. Say I have the following situation: A small form which should display a list of messages, and allow the user to select which ones they want processed. It processes each message in turn. If a message has more than one attachment, a dialog is shown to ask the user to select which attachment should be used for that message....

This morning I read this post by Alfred Thompson about whether we are Software Engineers or something else. I can’t help but agree with him, as I don’t feel we are engineers (yet), our discipline is a little fuzzy to be classified as engineering I think. However I think we are not alone in this boat. Not all engineering disciplines are quite so well cut. My father is an Engineering Pattern Maker....

There seems to be a lot of negativity towards the #Region in .net at the moment, with many people hating them and calling all usages of them ‘retarded’. I can see their point, especially when you see the odd class with regions like this: Class Foo { #Private Members #Protected Members #Friend Members #Public Members #Private Constructors #Protected Constructors #Friend Constructors #Public Constructors #Private Methods #Protected Methods #Friend Methods #Public Methods } Clearly the person who wrote this was ill at the time (I hope…), and besides, where would Protected Friends go?...