NanosSharp.Templates
0.2.4
See the version list below for details.
dotnet new install NanosSharp.Templates@0.2.4
NanosSharp Templates
dotnet new templates for NanosSharp packages on nanos world servers.
dotnet new install NanosSharp.Templates
# C# the server compiles and hot reloads, with a server, a client and a shared side
dotnet new nanossharp-script -n MyGamemode -o Packages/my-gamemode
# a package compiled into an assembly, built into its Server folder
dotnet new nanossharp-assembly -n MyGamemode -o Packages/my-gamemode
Use a valid C# identifier as the name, it becomes the class name of the package entry point.
Script package layout
my-gamemode/
.gitignore
Package.toml the nanos world package manifest
MyGamemode.slnx opens all three projects together
Server/
MyGamemode.Server.csproj
MyGamemode.cs the server entry point
Client/
MyGamemode.Client.csproj
MyGamemode.cs the client entry point, sandboxed by the server
Shared/
MyGamemode.Shared.csproj
Shared.cs compiled into both sides
The server compiles Server plus Shared, the client compiles Client plus Shared, each into its own
assembly. Shared is its own project that Server and Client reference, so shared code has one home and one
namespace instead of appearing twice. Every project uses the MyGamemode root namespace, so types from any side
are reachable without extra usings.
SERVER is defined for the server project and CLIENT for the client one. Those symbols apply to side code;
shared code is side neutral, put anything server or client specific in Server or Client. The .csproj files
are only for the IDE and for NuGet PackageReferences, the server compiles the sources itself. Drop the Client
folder if the package has no client code, or the Server folder if it has no server code.
This package has no dependencies.
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.