Enforce file width standard

Ignia maintains a 128 character width standard for files. And, for the most part, that's honored. But a handful of areas—and especially comments, broke over the 128 character limit. In most case, this was likely due to refactoring or automated renames which made `<see/>` references longer. Regardless, the vast majority of these are fixed here. (There are a handful that were left as is due to Ignia not having a good multi-line standard for breaking up particular types of references; we'll want to establish a consistent way of handling those.)

Author: JeremyCaney

Ignia.Topics.Web/TopicRepository.cs

@@ -39,7 +39,11 @@ public static class TopicRepository {
     /// <summary>
     ///   Gets a list of available <see cref="ContentTypeDescriptor"/> objects from the Configuration.
     /// </summary>
-    [Obsolete("The TopicRepository class is obsolete, as is the ContentTypes property. Instead, clients should use Dependency Injection with the ITopicRepository interface.", false)]
+    [Obsolete(
+      "The TopicRepository class is obsolete, as is the ContentTypes property. Instead, clients should use Dependency " +
+      "Injection with the ITopicRepository interface.",
+      false
+    )]
     public static ContentTypeDescriptorCollection ContentTypes {
       get {
         if (_contentTypes != null) {
@@ -55,7 +59,11 @@ public static ContentTypeDescriptorCollection ContentTypes {
     /// <summary>
     ///   Static reference to the root <see cref="Topic"/>.
     /// </summary>
-    [Obsolete("The TopicRepository class is obsolete, as is the RootTopic property. Instead, clients should use Dependency Injection with the ITopicRepository interface.", false)]
+    [Obsolete(
+      "The TopicRepository class is obsolete, as is the RootTopic property. Instead, clients should use Dependency Injection " +
+      "with the ITopicRepository interface.",
+      false
+    )]
     public static Topic RootTopic {
       get {
         if (_rootTopic == null) {
@@ -75,7 +83,11 @@ public static Topic RootTopic {
     /// <remarks>
     ///   The web.config stores information such as data providers, views directory, etc.
     /// </remarks>
-    [Obsolete("The TopicRepository class is obsolete, as is the Configuration property. Instead, clients should use Dependency Injection with the ITopicRepository interface.", false)]
+    [Obsolete(
+      "The TopicRepository class is obsolete, as is the Configuration property. Instead, clients should use Dependency " +
+      "Injection with the ITopicRepository interface.",
+      false
+    )]
     public static TopicsSection Configuration {
       get {
         if (_configuration == null) {
@@ -98,11 +110,18 @@ public static TopicsSection Configuration {
     ///   Pulled from the implementing website's configuration via the <see
     ///   cref="Ignia.Topics.Configuration.TopicDataProviderManager"/>.
     /// </remarks>
-    [Obsolete("The TopicRepository class is obsolete, as is the TopicProviders property. Instead, clients should use Dependency Injection with the ITopicRepository interface.", false)]
+    [Obsolete(
+      "The TopicRepository class is obsolete, as is the TopicProviders property. Instead, clients should use Dependency " +
+      "Injection with the ITopicRepository interface.",
+      false
+    )]
     public static ITopicRepository DataProvider {
       get {
         if (_topicRepository == null) {
-          throw new Exception("The TopicRepository has not been configured with an instance of ITopicProvider. Configure the application by setting the TopicRepository.DataProvider in e.g. the global.asax file.");
+          throw new Exception(
+            "The TopicRepository has not been configured with an instance of ITopicProvider. Configure the application by " +
+            "setting the TopicRepository.DataProvider in e.g. the global.asax file."
+          );
         }
         return _topicRepository;
       }

Ignia.Topics.Web/WebFormsTopicRoutingService.cs

@@ -200,7 +200,8 @@ public string View {
           // Validate the content-type after the slash, then validate it against available views
           for (var i = 0; i < splitHeaders.Length; i++) {
             if (splitHeaders[i].IndexOf("/", StringComparison.InvariantCultureIgnoreCase) >= 0) {
-              // Get content-type after the slash and replace '+' characters in the content-type to '-' for view file encoding purposes
+              // Get content-type after the slash and replace '+' characters in the content-type to '-' for view file
+              // purposes
               var acceptHeader = splitHeaders[i]
                 .Substring(splitHeaders[i].IndexOf("/", StringComparison.InvariantCultureIgnoreCase) + 1)
                 .Replace("+", "-");
@@ -214,9 +215,9 @@ public string View {
 
         /*----------------------------------------------------------------------------------------------------------------------
         | Pull from topic attribute
-        | Pull from Topic's View Attribute; additional check against the Topic's ContentType Topic View Attribute is not necessary
-        | as it is set as the default View value for the Topic
         >-----------------------------------------------------------------------------------------------------------------------
+        | Pull from Topic's View Attribute; additional check against the Topic's ContentType Topic View Attribute is not
+        | necessary as it is set as the default View value for the Topic
         \---------------------------------------------------------------------------------------------------------------------*/
         if (viewName == null && !String.IsNullOrEmpty(topic.View)) {
           IsValidView(contentType, topic.View, out viewName);