“There's a technical reason why this currently happens. We end up firing loaded when:
1) we finish parsing the actual UserControl definition.
2) we finish parsing the usage of the UserControl.
While it's a little annoying that we get two loaded events, it gives you more control though since you can use it to figure out if you're done with parsing the defintion or the usage of the user control. We're definately up for suggestions in changing the behavior though.”
Found a nice issue with user controls. The loaded event gets fired twice …