Socket.SendFile throws InvalidOperationException when Blocking=false

The behavior of SendFile on non-blocking sockets is undefined (Windows blocks anyway, Linux may send partial data), so we now throw InvalidOperationException early.

Author: laveeshb

src/libraries/System.Net.Sockets/src/System/Net/Sockets/Socket.cs

@@ -1325,6 +1325,13 @@ public void SendFile(string? fileName, ReadOnlySpan<byte> preBuffer, ReadOnlySpa
 
             ThrowIfDisposed();
 
+            // SendFile is not supported on non-blocking sockets.
+            // ValidateBlockingMode() below checks for async mismatch; this checks explicit non-blocking.
+            if (!Blocking)
+            {
+                throw new InvalidOperationException(SR.net_sockets_blocking);
+            }
+
             if (!IsConnectionOriented || !Connected)
             {
                 throw new NotSupportedException(SR.net_notconnected);

src/libraries/System.Net.Sockets/tests/FunctionalTests/SendFile.cs

@@ -37,6 +37,19 @@ public async Task NotConnected_ThrowsNotSupportedException()
             await Assert.ThrowsAsync<NotSupportedException>(() => SendFileAsync(s, null, null, null, TransmitFileOptions.UseDefaultWorkerThread));
         }
 
+        [Fact]
+        public void SendFile_NonBlockingSocket_ThrowsInvalidOperationException()
+        {
+            (Socket client, Socket server) = SocketTestExtensions.CreateConnectedSocketPair();
+            using (client)
+            using (server)
+            {
+                client.Blocking = false;
+                Assert.Throws<InvalidOperationException>(() => client.SendFile(null));
+                Assert.Throws<InvalidOperationException>(() => client.SendFile(null, ReadOnlySpan<byte>.Empty, ReadOnlySpan<byte>.Empty, TransmitFileOptions.UseDefaultWorkerThread));
+            }
+        }
+
         [Theory]
         [InlineData(false)]
         [InlineData(true)]