LiteNetwork 2.4.0
dotnet add package LiteNetwork --version 2.4.0
NuGet\Install-Package LiteNetwork -Version 2.4.0
<PackageReference Include="LiteNetwork" Version="2.4.0" />
paket add LiteNetwork --version 2.4.0
#r "nuget: LiteNetwork, 2.4.0"
// Install LiteNetwork as a Cake Addin #addin nuget:?package=LiteNetwork&version=2.4.0 // Install LiteNetwork as a Cake Tool #tool nuget:?package=LiteNetwork&version=2.4.0
LiteNetwork
LiteNetwork
is a simple and fast networking library built with C# and compatible with .NET Standard 2, .NET 5 and .NET 6. Its main goal is to simply the creation of basic socket servers over the TCP/IP protocol.
Initially, LiteNetwork has been initialy developed for game development networking, but can also be used for other purposes.
How to install
LiteNetwork
is shiped as a single package, you can install it through the Visual Studio project package manager or using the following command in the Package Manager Console:
$> Install-Package LiteNetwork
Or you can use the dotnet command:
$> dotnet add package LiteNetwork
Getting started
Create a server
There is two ways of building a TCP server with LiteNetwork
:
- The instance way, by creating a
LiteServer
instance and then run it manually - The service way
- In fact,
LiteNetwork
provides an extension to theServiceCollection
object, and can be integrated in a .NET Generic Host (used by ASP.NET Core, MAUI).
- In fact,
Common code
First of all, you will need to create the user class that will represent a connected user on your server. Simple create a new class
that implements the LiteServerUser
class.
using LiteNetwork.Server;
public class ClientUser : LiteServerUser
{
}
Within this class, you will be able to handle this client's incoming message sent by a client program thanks to the HandleMessageAsync()
method.
You can also be notified when the client connects to the server or disconnects.
using LiteNetwork.Protocol.Abstractions;
using LiteNetwork.Server;
public class TcpUser : LiteServerUser
{
public override Task HandleMessageAsync(byte[] packetBuffer)
{
// Handle incoming messages using a BinaryReader or any other solution for reading a byte[].
}
protected override void OnConnected()
{
// When the client connects.
}
protected override void OnDisconnected()
{
// When the client disconnects.
}
}
Once the server user is ready, you can create the server itself that will handle this TcpUser
type of users.
Create another new class
, and implement the LiteServer<T>
class where T
is the previously created TcpUser
.
public class MyTcpServer : LiteServer<TcpUser>
{
public MyTcpServer(LiteServerOptions options, IServiceProvider serviceProvider = null)
: base(options, serviceProvider)
{
}
}
The server has some hooks that allows you to control its life time, such as:
Method | Description |
---|---|
OnBeforeStart() |
Called before the server starts. |
OnAfterStart() |
Called after the server starts. |
OnBeforeStop() |
Called before the server stops. |
OnAfterStop() |
Called after the server stops. |
OnError(ILiteConnection, Exception) |
Called when there is an unhandled error witht the given ILiteConnection . |
Create the server via instance
Now that the server and user classes are built, you can now instanciate your server and call the Start()
method to start the server.
// Using top-level statement
using LiteNetwork.Server;
using System;
// Create the server configuration, to listen on "127.0.0.1" and port "4444"
var configuration = new LiteServerOptions()
{
Host = "127.0.0.1",
Port = 4444
};
// Create the server instance by givin the server options and start it.
using var server = new MyTcpServer(configuration);
server.Start();
// Just for the example, otherwise the console will just shutdown.
// Do not use in production environment.
Console.ReadKey();
Create the server via service
For this example, you will need to install the Microsoft.Extensions.Hosting
package from nuget in order to build a .NET Generic Host.
// Using top-level statement
using Microsoft.Extensions.Hosting;
using System;
var host = new HostBuilder()
.UseConsoleLifetime()
.Build();
await host.RunAsync();
Then, once your host is setup and running, you can configure the LiteServer
service using the ConfigureLiteNetwork()
method located in the LiteNetwork.Hosting
namespace:
// Using top-level statement
using LiteNetwork.Hosting;
using LiteNetwork.Server.Hosting;
using Microsoft.Extensions.Hosting;
using System;
using System.Threading.Tasks;
var host = new HostBuilder()
// Configures the LiteNetwork context.
.ConfigureLiteNetwork((context, builder) =>
{
// Adds a LiteServer instance for the MyTcpServer class.
builder.AddLiteServer<MyTcpServer>(options =>
{
// This configures the server's LiteServerOptions instance.
options.Host = "127.0.0.1";
options.Port = 4444;
});
})
.UseConsoleLifetime()
.Build();
await host.RunAsync();
Your server is now listening on "127.0.0.1" and port "4444".
Also, since you are using a .NET generic host, it also provides dependency injection into the server and client classes. Hence, you can inject services, configuration (IOptions<T>
if configured, etc..).
Note: You can also add as many servers you want into a single .NET generic host by calling the
builder.AddLiteServer<>()
method with different parameters.
Create a client
There is two ways of building a TCP client with LiteNetwork
:
- The instance way: by creating a
LiteClient
instance and then connect to the remote server manually. - The service way
- In fact,
LiteNetwork
provides an extension to theServiceCollection
object, and can be integrated in a .NET Generic Host (used by ASP.NET Core, MAUI).
- In fact,
Common code
First of all, you will ned to create a new class
that inherit from the LiteClient
class.
using LiteNetwork.Client;
public class MyTcpClient : LiteClient
{
public EchoClient(LiteClientOptions options, IServiceProvider serviceProvider = null)
: base(options, serviceProvider)
{
}
}
Just like a LiteNetwork server, the client has some hooks that allows you to control the client lifetime, such as:
Method | Description |
---|---|
HandleMessageAsync() |
Called when the client receives a message from the server. |
OnConnected() |
Called when the client is connected to the remote server. |
OnDisconnected() |
Called when the client is disconnected from the remote server. |
OnError(Exception) |
Called when there is an unhandled error within the client process. |
Create the client via instance
Using the previously created client, you can now create a new instance of the MyTcpClient
class, set the correct options to connect to the remote server and then, call the ConnectAsync()
method.
// Using top-level statement
using LiteNetwork.Client;
using System;
var options = new LiteClientOptions()
{
Host = "127.0.0.1",
Port = 4444
};
var client = new CustomClient(options);
Console.WriteLine("Press any key to connect to server.");
Console.ReadKey();
await client.ConnectAsync();
// Do something while client is connected.
Create the client via service
For this example, you will need to install the Microsoft.Extensions.Hosting
package from nuget in order to build a .NET Generic Host.
// Using top-level statement
using LiteNetwork.Client.Hosting;
using LiteNetwork.Hosting;
using Microsoft.Extensions.Hosting;
var host = new HostBuilder()
.ConfigureLiteNetwork((context, builder) =>
{
builder.AddLiteClient<MyTcpClient>(options =>
{
options.Host = "127.0.0.1";
options.Port = 4444;
});
})
.UseConsoleLifetime()
.Build();
// At this point, the client will connect automatically once the host starts running.
await host.RunAsync();
Once your program starts, your MyTcpClient
will try to connect to the remote server ("127.0.0.1" and port 4444). Also, since you are using the .NET generic host, it also provides the dependency injection mechanism into the client. Hence, you can inject services, configuration (IOptions<T>
if configured), logger, etc...
Note: You can also add as many clients you want into a single .NET generic host by calling the `builder.AddLiteClient<>() method with different parameters.
Protocol
Packet Processor
TBA.
Thanks
I would like to thank everyone that contributed to this library directly by fixing bugs or add new features, but also the people with who I had the chance to discuss about networking problematics which helped me to improve this library.
Credits
Package Icon : from Icons8
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net5.0 was computed. net5.0-windows was computed. net6.0 is compatible. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 is compatible. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
.NET Core | netcoreapp2.0 was computed. netcoreapp2.1 was computed. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed. |
.NET Standard | netstandard2.0 is compatible. netstandard2.1 was computed. |
.NET Framework | net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
MonoAndroid | monoandroid was computed. |
MonoMac | monomac was computed. |
MonoTouch | monotouch was computed. |
Tizen | tizen40 was computed. tizen60 was computed. |
Xamarin.iOS | xamarinios was computed. |
Xamarin.Mac | xamarinmac was computed. |
Xamarin.TVOS | xamarintvos was computed. |
Xamarin.WatchOS | xamarinwatchos was computed. |
-
.NETStandard 2.0
- Microsoft.Extensions.DependencyInjection (>= 3.1.20 && < 5.0.0)
- Microsoft.Extensions.Hosting.Abstractions (>= 3.1.20 && < 5.0.0)
- Microsoft.Extensions.Logging.Abstractions (>= 3.1.20 && < 5.0.0)
-
net6.0
- Microsoft.Extensions.DependencyInjection (>= 6.0.0 && < 7.0.0)
- Microsoft.Extensions.Hosting.Abstractions (>= 6.0.0 && < 7.0.0)
- Microsoft.Extensions.Logging.Abstractions (>= 6.0.0 && < 7.0.0)
-
net7.0
- Microsoft.Extensions.DependencyInjection (>= 7.0.0 && < 8.0.0)
- Microsoft.Extensions.Hosting.Abstractions (>= 7.0.0 && < 8.0.0)
- Microsoft.Extensions.Logging.Abstractions (>= 7.0.0 && < 8.0.0)
-
net8.0
- Microsoft.Extensions.DependencyInjection (>= 8.0.0)
- Microsoft.Extensions.Hosting.Abstractions (>= 8.0.0)
- Microsoft.Extensions.Logging.Abstractions (>= 8.0.0)
NuGet packages (3)
Showing the top 3 NuGet packages that depend on LiteNetwork:
Package | Downloads |
---|---|
LiteNetwork.Extensions
Super simple packet handling support for LiteNetwork. |
|
HeavyNetwork
Package Description |
|
LiteNetwork.Extensions.Processing
Super simple packet handling support for LiteNetwork. |
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated |
---|---|---|
2.4.0 | 576 | 1/21/2024 |
2.3.0 | 1,535 | 7/30/2023 |
2.2.0 | 1,055 | 12/28/2022 |
2.1.0 | 992 | 11/12/2022 |
2.0.0 | 1,051 | 5/27/2022 |
2.0.0-rc.6 | 213 | 5/14/2022 |
2.0.0-rc.5 | 131 | 4/24/2022 |
2.0.0-rc.4 | 129 | 4/23/2022 |
2.0.0-rc.3 | 118 | 4/23/2022 |
2.0.0-rc.2 | 131 | 4/23/2022 |
2.0.0-rc.1 | 124 | 4/23/2022 |
1.0.4 | 1,052 | 1/23/2022 |
1.0.3 | 1,010 | 1/22/2022 |
1.0.2 | 852 | 12/22/2021 |
1.0.1 | 807 | 12/22/2021 |
1.0.0 | 909 | 11/8/2021 |