Here are a few examples of "core" packages: Today, Xenko 3.1 brings Xenko as a set of smaller NuGet package, each containing one assembly, with proper dependencies:Īs a result, it is now possible to create a game project that references only the packages you want. Xenko 3.0 paved the way by making Xenko compatible with the new project system (game projects were referencing Xenko using a PackageReference). However, due to limitations (hello nfig and project.json!), we were leveraging NuGet more as a distribution medium than proper NuGet packages: Xenko 3.0 is still a monolithic single package and it would not work out of the box when referenced from Visual Studio without using Xenko Launcher and Game Studio. Xenko was always a big proponent of NuGet: since first version, Xenko was distributed as a NuGet package. Many thanks to the community and all the contributors who made this release possible: aggror, Eideren, alexb910, comradekingu, flabbie, CharlesWoodhill, Artaki, indigozero, dfkeenan, dominikjancik, erictuvesson, Hyperpred, louies0623, Lucifer2031, Ethereal77, mostafa901, Kryptos-FR, shinkitsunemaru, phr00t, Polymo, profan, xendez, Scorp-121, SleepyMode, tebjan, xen2, WhyPenguins, OoElectron, joreg, meriaizen86, rgawry, SantosSi, xwellingtonx, SilentCLD, HoSeCoin, Swann Martinet, WaldiS and pansan. Please note that Visual Studio 2017 is not supported anymore, please upgrade to 2019. One of the major change is turning the engine into modular NuGet packages, published on. ![]() Xenko tooling resolves assemblies dynamically using NuGet API.Xenko Packages are now distributed on.Xenko assets are also distributed as part of package. ![]() Package layout: following best NuGet practices.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |