The last couple of days (well actually for my parts it’s more like months or years) we have been discussion the management of dynamic controls in ASP.NET pages. In my experience this is a very common scenario and I haven’t still found a great way to handling it.

To explain better I’ll just a very simple fictive scenario; imagine that a page has a button “Create new control”. Next to the button is a textbox in which you can type the typename of the control to create (CheckBox, TextBox etc.). When you click the button the control, of the right type, is created.

Now for the “hard” part. Below the created control is another button “What was entered?”. When that button is clicked the code should, of course, read the content of the dynamically created control and print the value that was entered.

Pretty simple, eh? Well it’s not so...

Yesterday I followed a few links from the “Go around twice if you are happy”-video and as it turns out there are a whole community doing these kind of “nice” punk actions.

If you want to see some similar stuff try the WoosterCollective, especially the following categories (some are quite strong, you have been warned, but most are fun or just good):

• http://www.woostercollective.com/activism/
• http://www.woostercollective.com/chalk/
• http://www.woostercollective.com/fun/
• http://www.woostercollective.com/3d/

Also be warned - it is almost impossible to stop browsing the site…

Here are two short videos that made me happy in the morning. The first is a song with Oh Laura. The lead is performed by a friend of mine, Jörgen Kjellgren.

The second one is a… well, prank, maybe. Some people have put up some signs in an Arabic town which say things like “Stop here if you would rather have been in bed” or “Turn around twice in the roundabout if you are happy.” Then they have filmed the result. It’s quite gratifying to watch.

And no one is getting hurt, no misfortune is happening to anyone. And still, it’s funny. Just think…

My company, Avega, is back from a conference on Iceland.

The conference in it self was a great success. Very well organized, good weather (which does NOT happen often at Iceland, from what i understand), great fun with great people.

But once again I come to think about how blessed I am with my surroundings. I’ll give you an picture which I have experienced several times the last year or so:

Think about when you have done something extra with others, for example went to a camp, a great vacation or some thing else of that kind. When you are traveling home you always get a strange feeling with a strong sense of wanting it to go on, don’t you?

Well, for me, it does!

This weekend I have had some great times with a great bunch of people. Lots of interesting, fun and engaging discussions and get...

The European is now to an end and some shocking results was delivered…. Here is the complete results, where you can note that the Oberoesterreich Brass Band were placed 10/11 which is really strange since they got some raving reviews.

For our Swedish contender things didn’t work out to well. I think that the approach to a competition is shown very clear with the results. For band - with a lot of amateurs, like Stavanger, Cory or Willebroek - it’s life and death stuff. For bands with mostly pros things aren’t as serious. And then you don’t win any competitions against the other group. A 9 place for Stockholm Brass Band may have been a correct adjudication.

And for me things went quite well. My predictions had the right three top bands, but not in the right order. I am not a big fan...

It’s that great time of the year when the best brass band competition in world takes place - the European Brass Band Championships. Historically this is where the best bands plays at the very highest level. This year the event takes place in Norway, in Stavanger.

We Swedes are of course strengthen by the win of WindCorp in Grenland, which from what I understand was a great display from the band. We’ve come to expect nothing less from that great band.

The Swedish band competing in Stavanger is Stockholm Brass Band. I wish them all the best and really hope that they can impress the judges - they sure have all the potential to do so. I’ll be keeping my thumbs crossed all weekend.

So how will it all go down? The test piece is quite modern and not very “brass bandy”. So that will probably promote...

You have to see this amazing performance….

Took me a while to understand but she is recording herself and the replaying it while continue to add voices, rhythm etc… and finally produces a wonderful sound and a quite catchy song.

Don’t try this at home, boys and girls. She is a professional

One thing that really surprised me was that when tests fail in my build script the build script happily ran along after that!? Isn’t one of the ideas with Continuous Integration that the build script only will emit working versions?

Well in this article Aaron Hallberg (Swedish relatives?) shows us how to handle this. What he basically does is to check the status of the test-run and then update the status of the complete build.

I extended his code to use the test-status-flag on the tasks that follow the test, i.e. the publish task. This task deploys the executables to my test server, update the documentation etc.

So now I’ve got my desired result which is that failing test leads to failing the whole build.

When you have a testing framework in place you of course want to test it each build. But of course, you also want to know much code your tests are covering, a.k.a. CodeCoverage.

It is in a way quite easy to accomplish in your build script. The only catch is the complete lack of documentation. Benjamin Day led the way (he he - it rhymes).

What you need to do is two things:

1. First configure the tests to run. This is easily done by adhering to good naming standards (all test assemblies ending with tests.dll). Then you can add create an item group called TestContainer, like below. This will run through all your tests.

   <ItemGroup> <TestContainer Include="$(OutDir)\%2aTests.dll" /> </ItemGroup> 

2. Secondly (and here is the secret) you need to specify that the tests are to be run under code coverage....

This is a great song from a great old show - Macken.

I just love his way of taking out the worst in life.