Geeks With Blogs
Running with Code Like scissors, only more dangerous March 2008 Entries
Why doesn't Dispatcher implement ISynchronizeInvoke?
This is a rant. I don't have the answer to the question. So, the latest project I'm working on is a kiosk app in WPF that has to interact with hardware. The hardware has various needs; some of it I need to poll, and others I check on status every given interval. Every class I've created for interacting with the hardware has a SynchronizingObject property, just like the System.Timers.Timer class, and I was pretty happy with myself when I figured out that my event raising implementation was the same ......

Posted On Friday, March 28, 2008 4:56 PM

Model-View-Controller and Assembly Dependencies
The title of this blog post might be a slight misnomer because it isn't dealing with MVC directly. It's dealing with something a little more high level (oddly enough). I'm working on a personal project when I have time. I haven't played around with Battle.net in a while and there's still a fairly active user community around it (not to mention that Starcraft 2 is going to be released one day). On top of everything else, I learned so much about all kinds of topics (design patterns, reflection, UI ......

Posted On Thursday, March 27, 2008 11:00 PM

Thoughts on Generics and Best Practices - Building Cohesive Software
In general, I don't know whether I internalized this as a best practice because it makes sense to me, or because I read it somewhere. But I have this notion that there are only certain places in which it is appropriate to expose a generic member to the outside world, such as when the item is clearly generic in scope. For example, if I wanted to implement a FIFO list to get the behavior of a queue but the performance characteristics of a list, I might call my class ListQueue<T>. As a library ......

Posted On Tuesday, March 18, 2008 9:38 AM

Exceptional Exception Handling: Taking Exception with the Community
I could have gone on with the title for a while longer. Frequently when I'm working on an application, it occurs to me that the user doesn't care about the technical reasons behind an exceptional condition. Typically, the user simply cares that something went wrong; or, sometimes, the user doesn't care, especially if you can make the program recover gracefully. Since the only .NET-sanctioned way to handle errors is through structured exception handling, and since I love SEH, I don't want to be too ......

Posted On Monday, March 3, 2008 10:50 PM

Copyright © Robert Paveza | Powered by: GeeksWithBlogs.net