Improve Build System Epic about stride HOT 5 CLOSED

A good number of large projects on NuGet (i.e. Discord.NET, Newtonsoft.JSON, etc..) also tend to utilise metapackages to make referencing all components or specific subsets of components easier on the developer. Given how many libraries Xenko creates, this could be an idea.

We could, for example, do this:

• Xenko (overall metapackage)
  • Xenko.Graphics (compartmentalised render backends)
  • Xenko.Editor (Game Studio / "native" UI for editor and extensions)
  • Xenko.Tests (unit testing)
  • etc

as well as individual library packages for the adventurous.

from stride.

Yes, metapackages would still be possible. However, in practice, since PackageReference are transitive, I expect referencing Xenko.Engine should transitively pull everything a simple game need so they might not even be necessary. This goes in line with what https://github.com/dotnet/corefx and .NET Standard are doing.

from stride.

will there be a webGL export ?

from stride.

@weekendkoder this is discussed in: #70

from stride.

@tebjan .. okay. Thx.

from stride.