* try net8 packaging

* explicit assembly binding redirect

* attempt to fix file collision problems

)

* very minor spelling update

* Issue 1102 - added IComparable to EnumMember and a directive to Sort the array within GetEnumValues of MetaType.

* Issue 1102 - added extra compare logic

* Issue 1102 - Removing conditional compilation so that GetEnumValues returns an array sorted by enum value

* Issue 1102 - adjusting sort logic to order from zero to int.MaxValue then from negative int.MaxValue to -1. EnumMembers that have a value outside of int min max ranges return zero. This change impacts sort order for proto2.

* Issue 1102 - todo comment clean up

* Issue 1102 - Added test case for an enum that has negatives and out of range values. Adjusted sort logic to give correct order. Note that out of range values are treated as equivalent no matter the value being compared to, this impacts the context only proto generation.

For example, not positions of B and D

public enum OutOfRangeEnum : long
{
  A = 1,
  B = -4,
  C = int.MaxValue,
  D = ((long)int.MaxValue) + 1,
  E = -int.MaxValue,
  F = ((long)int.MinValue) - 1,
}

/* for context only
enum OutOfRangeEnum {
   ZERO = 0; // proto3 requires a zero value as the first item (it can be named anything)
   A = 1;
   C = 2147483647;
   B = -4;
   // D = 2147483648; // note: enums should be valid 32-bit integers
   E = -2147483647;
   // F = -2147483649; // note: enums should be valid 32-bit integers
}
*/

* Issue 1102 - Correction to sort order so that negatives are from -int.MaxValue to -1.

This changes where out of range values appear, for example, note positions of B, D and F in the context only output;

public enum OutOfRangeEnum : long
{
  A = 1,
  B = -4,
  C = int.MaxValue,
  D = ((long)int.MaxValue) + 1,
  E = -int.MaxValue,
  F = ((long)int.MinValue) - 1,
}

/* for context only
enum OutOfRangeEnum {
   ZERO = 0; // proto3 requires a zero value as the first item (it can be named anything)
   A = 1;
   C = 2147483647;
   E = -2147483647;
   B = -4;
   // D = 2147483648; // note: enums should be valid 32-bit integers
   // F = -2147483649; // note: enums should be valid 32-bit integers
}
*/

…above only) (#1118)

Co-authored-by: ladeak <ladeak87@windowslive.com>

Fixes #1106

* dignostic CS8981 doesn't exist (as 8981 without prefix) in down-level compilers

cross-ref #1107

* reorder to maintain output

…1133)

* adds support for EnumNamePrefix

* update tests

* resolve comments

---------

Co-authored-by: abuyusuf <abuyusuf@microsoft.com>

)

This prevents nested types - e.g. child objects or arrays of child
objects - from being removed by the linker when an application is
trimmed.

This only works at the moment in current unreleased versions of the
.NET SDK (e.g. .NET 6 rc.1.21381.5). It does not work in any publicly
released preview up to and including .NET 6 Preview 6.

See dotnet/linker#2185 for more information.

* Before fix

* Fix the warning output for the CS0078 rule