In a .NET 3.5 solution, if you write something simple like the following:
```
uint test = uint.MaxValue;
test.ShouldBeEquivalentTo(uint.MaxValue);
```
Then you will get the following compilation error using FluentAssertions NuGet package version 3.0.107:
__Error 1 'uint' does not contain a definition for 'ShouldBeEquivalentTo' and no extension method 'ShouldBeEquivalentTo' accepting a first argument of type 'uint' could be found (are you missing a using directive or an assembly reference?)__
This also applies to ushort and ulong, but primitives such as; byte, sbyte, short, int and long, are all OK.
```
uint test = uint.MaxValue;
test.ShouldBeEquivalentTo(uint.MaxValue);
```
Then you will get the following compilation error using FluentAssertions NuGet package version 3.0.107:
__Error 1 'uint' does not contain a definition for 'ShouldBeEquivalentTo' and no extension method 'ShouldBeEquivalentTo' accepting a first argument of type 'uint' could be found (are you missing a using directive or an assembly reference?)__
This also applies to ushort and ulong, but primitives such as; byte, sbyte, short, int and long, are all OK.