Class TiffDataTypeController

[JsonObject(MemberSerialization.OptIn)]
   public class TiffDataTypeController
   {
   }

public class TiffDataTypeController
   {
      [JsonConstructor]
      public TiffDataTypeController()
      {
      }
   }

protected bool Exists(ushort tagId)
{
}
In this case, there is no need for reformatting as the input code already follows standard C# conventions. However, I would format it consistently with other examples in your codebase if you have one:
protected bool Exists(ushort tagId)
{
}

protected TiffDataType[] GetSectionTags(int section)
{
    return _tagFormats[section];
}

protected byte[] GetTiffByteValue(ushort key)
   {
   }

protected uint GetTiffLongTypeValue(ushort key, uint defaultValue)
{
    var tiffReader = new TiffReader();
    using (var stream = File.OpenRead(_fileName))
    {
        var directory = tiffReader.GetTiffDirectory(stream);
        if (directory != null)
        {
            var value = defaultValue;
            if (directory.GetTag(key) != null)
            {
                using (var reader = new TiffTagReader(directory.GetTag(key)))
                {
                    value = reader.LongValue;
                }
            }
            return value;
        }
        throw new Exception($"Error reading TIFF file: '{_fileName}'");
    }
}

protected TiffRational[] GetTiffRationalArray(ushort key)
{
    var array = new List<TiffRational>();
    return array.ToArray();
}

protected TiffRatal GetTiffRationalValue(ushort key)
   {
   }

protected TiffSRational GetTiffSRationalValue(ushort key)
{
    TiffSRational result;
    if (m_tiffRationalData.TryGetValue(key, out result))
        return result;
    return default(TiffSRational);
}

protected ushort[] GetTiffShortArray(ushort key)
{
}

protected ushort GetTiffShortValue(ushort key, ushort defaultValue)
   {
   }

protected string GetTiffStringValue(ushort key)
{
}
The given C# code already follows standard conventions for indentation, spacing, and general readability. To improve readability further, consider adding blank lines between methods or sections of code with different logical scope or purpose. However, the provided code does not require reformatting in this regard:
protected string GetTiffStringValue(ushort key)
{
}

protected TiffDataType GetTiffType(ushort key)
   {
      switch (key)
      {
         case TiffTag.EXIF: return TiffDataType.Long;
         case TiffTag.GPSLatitudeRef: return TiffDataType.Ascii;
         case TiffTag.GpsVersionID: return TiffDataType.Short;
      }
   }

protected byte[] GetTiffUndefinedValue(ushort key)
   {
       switch (key)
       {
           case 37500: // ASCII "TIFF"
               return new byte[] { 73, 74, 69, 73 };
           default:
               return new byte[2];
       }
   }

protected void RemoveTagByID(ushort tagId)
   {
   }

protected void SetSectionTags(int section, TiffDataType[] tags)
   {
   }

protected void SetTiffByteValue(
       ushort key,
       byte[] value,
       int section)
   {
   }

protected void SetTiffLongTypeValue(
       ushort key,
       uint value,
       int section
   )
   {
   }

protected void SetTiffRational(
      ushort key,
      TiffRational rational,
      int section
   )
   {
   }

protected void SetTiffRationalArray(
       ushort key,
       TiffRational[] rational,
       int section
   )
   {
   }

protected void SetTiffSRationalValue(
       ushort key,
       TiffSRational rational,
       int section
   )
   {
   }

protected void SetTiffShortArray(
       ushort key,
       ushort[] value,
       int section)
   {
   }

protected void SetTiffShortValue(
      ushort key,
      ushort value,
      int section
   )
   {
   }

protected void SetTiffStringValue(
       ushort key,
       string text,
       int section)
   {
   }

protected void SetTiffType(TiffDataType tiffDataType, int section)
   {
   }

protected void SetTiffUndefinedValue(
       ushort key,
       byte[] data,
       int section)
   {
   }