WPF: Always Remember Rebuilding the Solution

This is one funny thing I found while fiddling around with WPF, Cider and the other parts from the newest CTP release: every now and then it’s required to rebuild the complete solution. I suppose it’s not meant to be that  way, but I’ve had all kinds of interesting effects. One time there was a weird exception coming up at runtime, telling me that a Button can’t be cast to a ListBox. The other time it was just some initialization code for a control that was apparently being executed, but didn’t have any effect. Rebuilding the complete solution helped in both cases and my guess is that the problem came up when I made some changes to the XAML code of a window. So if your WPF app seems to behave oddly, always remember rebuilding the solution – it might help.

Sorry, this blog does not support comments.

I used various blog hosting services since this blog was established in 2005, but unfortunately they turned out to be unreliable in the long term and comment threads were lost in unavoidable transitions. At this time I don't want to enable third-party services for comments since it has become obvious in recent years that these providers invariably monetize information about their visitors and users.

Please use the links in the page footer to get in touch with me. I'm available for conversations on Keybase, Matrix, Mastodon or Twitter, as well as via email.