Alarm Clock Sample -- Part 4

Parts 1, 2, 3 described my steps to understanding the Alarm Clock Sample program but there are still a few files left many of which may have been autogenerated.

In no particular order:

• assemblyinfo.cs
  An assembly is a compiled file in .NET nomenclature so I assume this file will describe information about the final output file. There are preprocessor directives in this file, I haven't seen them in any other file so far and that makes me think this file was autogenerated (also note the detail and amount of comments). #region has nothing to do with application logic, it's just for editor eyecandy.
  Code in the square brackets looked familiar to me. If you right click on an executable or dll, in the properties dialogue, this code sets up what you will see in the version tab (maybe the summary tab too). Some of the fields don't match though, I changed AssemblyDescription and it was shown in the value of the "Comments" item. Of course the .NET Framework Class Library has all that information in the System.Reflection Namespace.
• resources.designer.cs
  This file states upfront that it is autogenerated. It is the "Resource Designer" that generates the file. From the Visual Studio Reference

  The Resource Designer is a user interface tool that enables you to manage resources (such as strings, images, icons, audio, and other files) for your project. .... Items that you add to the project by using the Resource Designer are placed in the Resources directory for your project. The designer information is stored in a file named Resources.resx, and code for the resource is stored in Resources.Designer.cs....

• resources.resx
  From the above, we know "the designer information is stored here". But that doesn't really help me understand the file. Bechir Bejaoui gives a nice, quick introduction. It looks like these files are not something you would want to write yourself. I guess it would be best to use Visual Studio to generate these if you are going to have a ton of external resources and you want to keep track of them in this way.
• settings.designer.cs and settings.settings
  I couldn't find much information about these two files to help me understand them so I'm putting them together. The best thing I could find was from the Visual Studio Reference . My understanding is that you can use these two files to set up a way to allow changeable but persistent application settings. The user can change some setting in the program and then when they close and reopen it, the settings will still be there. Seems to be a new fangled *.ini file.

The next thing I'm going to do to improve my understanding of C# is rewrite the Alarm Clock Sample in pure C# without help from XAML (I'll try to understand XAML more fully in the future).