I have grown tired of looking up the named colors for my WPF apps. So I wrote a Helper class to make my life a little easier.
After playing around with this idea for a couple hours, I found a Dictionary<string,Color> is the easiest and most flexible way to reach my goal.
I’ve got an amusing problem at work. We need to create a way of passing runtime arguments around our app with safe and consistent results.
One solution is create a global class that sits in the core library. All of the properties would have to be static. At runtime, the bootstrapper updates the properties then we point everything to the global class when we need to know a value.
But it smells. A stinky lit’ hack.
… is not something I’m known for. Being an introvert, I’d rather avoid the uncomfortable dialog. If I can’t avoid it, I want to end it as quickly as possible. My “normal” method is to lay out my argument as logically as possible. If that doesn’t work, I go for the throat and attack the inner most issue at hand. Pulling out the nasty gore and exposing it to daylight, so we can address the core problem and move on as quickly as possible.
So…
I am struggling with my current client. The lead is… um challenging. Let me give you a bit of background.
I have been having problems with the internal testing library in Visual Studio. I get an API error. “The assembly has already been loaded and cannot be loaded into the appDomain.”
Really? <sarcastic response>
Everyone on the team has had intermittent issues for a couple months. One solution seemed to be to clean the solution, close VS, reload VS, open your solution, load the Test View (View -> Tool Bars -> Testing, find the “Test View” icon and click on it). Once the Test View loaded up the assemblies the issue might not appear. Obviously that isn’t an ideal solution.
I tried going through each project, removing any references to the lib, clean, rebuild solution (obviously a failure), then re-add the reference for each missing assembly. That worked once and only once.
My latest effort was to go through each project file and manually edit the reference. I removed the processorArchitecture=MSIL attribute from each entry. I loaded up my solution in VS and went through the usual Test View steps. So far, it works.
Maybe this problem is worse on x64 systems. Our team lead was running Win2008 x64 for months and always struggled with this issue. When I was on WinXP the issue was a minor annoyance that would pop up once a week or so. I switched to Win7 x64 a couple weeks ago and the issue has been a constant irritant ever since.
Hmm…
