I saw this interesting article about using model metadata in ASP.NET MVC to add the aria-required attribute to required input fields. The approaches there are all totally valid and work great if you have the requirement to add the attribute on the server-side.

However, if you’re using jQuery unobtrusive validation, you’ve already got some metadata you can use from the client side. Required fields all get the data-val-required attribute associated with them:

<input
  data-val="true"
  data-val-required="This is a required field."
  id="RequiredField"
  name="RequiredField"
  type="text"
  value="" />

The attribute only exists on required fields. With that, it’s easy enough to jQuery your way to freedom and leisure:

$(function () {
  $('[data-val-required]').attr('aria-required', true);
});

…and now all of your required fields have the appropriate ARIA attribute.

Phoenix is really into the Fisher Price “Little People” figures, particularly the DC Super Friends line. She doesn’t know a lot of words, but she knows “Bapmo!” (Batman) and loves flying them around the room.

A while ago we got her the Batcave playset so she’d have some additional vehicles and stuff, not just figures. This, of course, led to also getting Wonder Woman’s invisible jet and the Batmobile. (OK, maybe it doesn’t hurt that we both like the Super Friends. Come on, when your 18-month-old runs around yelling about Batman, that’s pretty sweet.)

The proliferation of Super-Friends-related items started lending itself to a bit of a storage dilemma, and on top of that, I started thinking back to the cartoons… How can you have the Super Friends without the Hall of Justice?

So I took a cardboard box, went to the craft store and picked up some supplies… and I present to you: The Little People Hall of Justice!

From 20120422 Hall of Justice

The main form is just a cardboard box. The outside is covered in a thin white foam that makes it soft. I lined the inside with tagboard and added a fold-down flap that Velcros shut so you can play inside. The windows on the front are blue tagboard behind some cutouts in the foam. The edges of the cardboard are lined with twill tape to avoid any cardboard cuts. I reinforced the top with additional cardboard so it’s not quite climb-proof, but it should stand up to some reasonable amount of abuse.

I posted several views of it in the photo album if you’re interested. The pictures have captions that explain how things are put together… in case you want to make your own.

Wonder Twin powers ACTIVATE!

I’m working on a fairly major refactoring project, merging a couple of fairly large libraries together that have some overlapping/similar functionality. I figured this would be the perfect time to try out the reasonably new CodeRush Duplicate Code Detection feature.

The solution I’m working on has eight projects - four unit test projects, four shipping class libraries, and a total of 1248 C# code files.

I didn’t have duplicate code detection running in the background during the initial pass at the merge. Instead, I ran the detection after the initial pass to indicate some pain points where I need to start looking at combining code. (Let me apologize in advance - I wanted to show you the analysis results in a real life project, but because it’s a real project, I can’t actually show you the code in which we’re detecting duplicates. I can only show you the duplicate reports. With that…)

First, I started with the default settings (analysis level 4):

Running that pass took about eight seconds. I found a few duplicate blocks in unit tests, which weren’t unexpected. Things having to do with similar tests (specifically validating some operator overload functionality):

I wanted to do a little more, so I turned it up a notch to analysis level 3 and ran another pass. This time the pass took about 12 seconds and I found a lot more duplicates. This time the duplicates got into the actual shipping code and started pointing out some great places to start refactoring and merging code. This pass also grabbed more duplicates across classes (whereas the previous pass only caught duplicates within a single class/file).

Well, since one notch on the analysis level settings was good, two must be better, right? Let’s crank it up to analysis level 2!

Once you get to level 2 and below, you get a warning: Analysis might require significant CPU power and memory. I’m not too concerned with this right now since I’m running the analysis manually, but if you turn on the background analysis mechanism you’d probably want to verify that’s really what you want.

Anyway, the third pass using analysis level 2 still only took about 12 seconds… and re-running it, to verify that time, only took around 5 seconds so I’m guessing there is some sort of caching in place. (But don’t hold me to that.)

Now we’re talking! Tons of duplicates found on the level 2 run. However, while the code is very similar, there aren’t as many “automatic fixes” that the system can suggest.

I don’t fault CodeRush for this - the duplicates will require a bit of non-automated thought to combine, which is why they pay us (programmers). (If they could replace us with scripts, they’d do it, right?) I’m sure the geniuses at DevExpress will shortly replace me with a keystroke in CodeRush so they can hire my cat in my place, but until then, I can use this as a checklist of things to look at.

Out of curiosity, I decided to do another run, this time at level 0 - the tightest analysis level available. This run took ~50 seconds and found so many duplicates it’s insane. Some are actionable, some are what I’d call “false positives” (like argument validation blocks - I want the validation to take place in the method being called so the stack trace is correct if there’s an exception thrown). Still, this is good stuff.

Given the balance between the too-granular detection and the not-granular-enough, I think I’m going to go with the level 2 pass, address those things, and then maybe turn it up from there.

Overall, I was really impressed with the speed of this thing. I mean, 1248 files, thousands of classes… and it takes less than a minute to do super-detailed analysis? That’s akin to magic.

Big props to DevExpress for a super-awesome tool that helps me improve my code. And, hey, some of the automatic fixes that are built in don’t hurt, either. :)

If you want to use this on your project, head over and pick up CodeRush. Honestly, it’s the first thing I install right after Visual Studio, and this sort of feature is exactly why.

I think I’m getting old and starting to fall apart.

For the last year I’ve had this Eustachian tube dysfunction that causes me to hear myself really loud in my left ear. If I’m talking, all I hear is me. When it’s really bad, I can hear my heartbeat or my breathing. Walking around would cause a thump-thump-thump sound with every step.

I ran through five days of prednisone and cipro, then 10 days, with no luck. After a 25-day-run of prednisone, I ended up going in on Monday and gettinga tympanostomy tubein my ear.

When they do it, you lay on your side and they drop some anesthetic in your ear. You lay there for a while letting that soak in, then they pop your eardrum and put the tube in. The tube itself is about the size of a pencil lead. It didn’t hurt going in, but there is still some occasional soreness a couple of days later if I yawn really big or bend over such that the blood rushes to my head.

I still hear myself a little, but in general that whole side of my head feels clearer. I’m waiting for a few days before I test to see if I can clear it.

That same day I noticed the left half of my tongue had gone numb. I let it go for a day, but it was still numb, and that freaked me out a bit, so I called the doctor’s office.

When they puncture your eardrum, some of the anesthetic runs through your Eustachian tube into other areas of your head. Apparently some hit my tongue just right (though I didn’t taste anything) and numbed me up. Today, two days later, I’m better… but that lasts a really long time. What was most freaky was that I could feel things on my tongue, I just couldn’t taste, like half of my taste buds had just died. I’m guessing some nerve got hit or something.

I also got some new glasses because Phoenix got ahold of my old ones and decided to rip the arm off. Since my prescription had expired, I had to get a new one. Upon getting my new glasses, I noticed everything looked like I was looking out a slight fish-eye lens – straight lines weren’t straight anymore. Looking at, say, a brick wall was really trippy because the whole thing looked curved. I tried them for a week and took them back.

The optician said I wasn’t adapting to the lens material, so I went from polycarbonate lenses to some other higher-density material. Same thing – weird curvy vision. Again, I tried for a week and never adapted, so I fell back to plastic lenses. (I did inquire as to whether something in my new prescription might be causing this but I was assured it was the lens material.)

I’m wearing the plastic lenses right now and still seeing curvy. Keeping in mind it takes about a week to get my glasses fixed up every time I take them back, we’re going on well over a month now since I first tried to get new glasses. I’ll give these two weeks before taking them back, but right now I hate these stupid glasses with every fiber of my being. I hate that nothing looks right. I really just want my old glasses with my old prescription even if I wasn’t seeing 20/20.

So that’s three of my five senses that have gone out on me recently and I have to say, it’s stressing me out.

I won’t even get into the pressure cooker work has become, or my lack of time to do anything at home, or the bathroom caulk I’ve replaced twice now because I can’t get it to set.

Basically I’m just tired all the time now. I’m hoping things pick up soon because I’m really just falling apart.

I’m working on building a bunch of projects that all follow a specific convention for naming, NuGet packaging, and so on. As part of that, I want to run the build for each component – from clean to package – all at once rather than clean everything, then build everything, then package everything. (For the sake of the article, let’s ignore whether that’s a good idea or not and just stick with me.)

MSBuild has batching, which sort of works like “for-each,” but in examples you see you can really only “batch” on tasks. Targets (groups of tasks) allow you to specify inputs and outputs, but the “outputs” list is assumed to be files, so if it finds the outputs are up to date, it won’t run that input.

Anyway, I found this article that explains how to sort of abuse the inputs and outputs on targets so you can effectively do for-each over a target.

First, create an item list with your inputs and metadata. It doesn’t have to be files. For your inputs, pass the list of parameters. For the outputs, put a dummy value that always evaluates to empty/null – that way it’s never seen as up to date and will always run.

Here’s a sample script:

<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="Start"
  xmlns="http://schemas.microsoft.com/developer/msbuild/2003"
  ToolsVersion="4.0">
  <ItemGroup>
    <SomeValues Include="First">
      <Meta>true</Meta>
    </SomeValues>
    <SomeValues Include="Second">
      <Meta>false</Meta>
    </SomeValues>
  </ItemGroup>
  <Target Name="Start">
    <CallTarget Targets="Parameterized" />
  </Target>
  <Target Name="Parameterized" Inputs="@(SomeValues)" Outputs="%(Identity).Dummy">
    <Message Text="Item = %(SomeValues.Identity)" />
    <Message Text="Meta = %(SomeValues.Meta)" />
    <Message Text="---" />
  </Target>
</Project>

The output, as you’ll see, is that the “Parameterized” target gets called once for each item in the group.