Assorted Frustrations

 If you want a table like thing for a Legend you can take a look at the following.  Putting this in the Load event works.  However...this code was never actually used.  Why?  Because it takes up too much chart real estate, and when the pages to a small width the chart resizes too small and becomes unreadable.  Too bad. :(.   ////Create a new legend called "Legend3".          Chart1.Legends.Add(new Legend("Legend3"));           ////Set Docking of the Legend chart to the Default Chart Area.          Chart1.Legends["Legend3"].Docking = Docking.Left;          Chart1.Legends["Legend3"].Alignment = StringAlignment.Center;                   ////Assign the legend to Series1.          Chart1.Series["Series1"].Legend = "Legend3";          Chart1.Series["Series1"].IsVisibleInLegend = true;          LegendCellColumn lccSym = new LegendCellColumn("Sym", LegendCellColumnType.SeriesSymbol, "");          lccSy

Not something I would have thought would be a large problem, but turned out to be.  Reading that XML quickly without some kind of font color scheme takes forever and is error prone.  For me at least hah.   Found a post on SO about someone saying their VS had lost that ability for their XAML files and that someone suggested to reset the user settings.  It worked for them for XAML, and that method worked for me for my XML.  Sweet.  Just open up the command prompt for the relevant visual studio and type in  devenv /resetuserdata. http://stackoverflow.com/questions/13582209/no-xaml-color-formatting-in-visual-studio-2012

Some old checklist I had made a while back on converting an asp page to asp.net.  It was kind of a pain, and it popped up again, because a fellow co worker was asking about it.  It might be of some use. 1)       First I created an aspx page, then copied the asp over it excluding the original ASP directive at the top. 2)       Make sure class names, filenames, locations are correct. 3)       Need to use Codefile instead of CodeBehind in the Page directive. 4)       Make sure the language in the directive matches the code.   In that asp page I was converting the language was “C#”, but the script language was “VB”. 5)       Since this is asp.net make sure you are using Partial keyword in code behind for the class declaration type. 6)       May need to have new includes. 7)       “ '__o' is not declared. It may be inaccessible due to its protection level.                 Will show as a compiler Error, but is not actually an error that will stop you from running the

I like the simple answer: http://www.u-convert.com/ and then select "To UpperCase".  The problem of trying to get correct capitalization on names is something I saw on a couple blogs.  Some used recursion and others just did more simple manipulations.  However, if they are all caps then everything is consistent without having any possible complaints from all though McCoy's and DeForest's and similar names.