WPF loves to divide by zero

Ignoring for a moment how worthless the WPF designer is ( and I've not tried the VS2010 one b/c VS2010 is so slow and buggy that I don't want to move my projects there ), it seems like at random points, my large WPF project will compile, and fail to run, with a divide by zero error at the root of the project, in the App class. Rebuilding will fix it, there's never a bug in my code.

string.Split

There is no question that, compared to C++, C# makes working with strings a lot easier. However, some things still don't make sense. I have used the split method on the string class countless times. I could count on one hand the number of times I had more than one argument to split by. Why is there no overload that takes a single string or char, and doesn't force me to write code that creates a single element array inline so I can satisfy the method signature requirements ?

A little thing...

When I create a new project in VS, it gives me two textboxes, one for a project name, and one for a folder. If I type in to the folder textbox, it autocompletes based on paths that exist. This is nice. When I get a list of folders that exist, if I select one and press 'enter', the OK button gets triggered and 'WindowsFormApp1' gets created in the location I chose. Surely the fact that it's the default, useless name, is a clue that I was entering the path first ?