Given most programming problems there is an almost endless number of ways to implement a solution for even the most simple task. One of those tasks that many take for granted is string manipulation. When talking to a friend recently about this it brought up the question of which method is faster and better performing. So I decided I needed to look at execution speeds and memory usage of three of the main string manipulation implementations; String.Format, StringBuilder and String Concatenation.
Recently I desired to have support for ASP.NET 4.0 in my web hosting. Since I currently had an unlimited shared Windows hosting plan with GoDaddy I had hoped that the transition would be easy. So, I looked into what they were offered in the way of hosting that supported .NET 4.0. From my search the only offering they had was a Windows Grid hosting plan which was identical to my current plan except it was hosted across multiple servers instead of one shared server. I thought that this would be great, clustered hosting and support for .NET 4.0, unfortunately I was wrong.
The other day while working on a Silverlight application I received the following error:
“Parser internal error: Object writer ‘xClassNotDerivedFromElement’. [Line: N Position: N]
at System.Windows.Application.LoadComponent(Object component, Uri resourceLocator)”
When calling the InitializeComponent() internal method on a custom user control.
So I did what I did best and searched Google for the answer, and while I didn’t end up finding my solution there I did find more about what can cause this error to occur.
Recently, I was working on a project when I came into a problem that I hadn’t dealt with before. You see I was working with a rather large table (200+ fields) and a corresponding archive table for it. The goal was to be able to populate a form with fields from either of the object types as essentially they were the same record type.