I can see this working the way UE4 does (i.e. launcher with binaries for people who don't feel comfortable building themselves)
Robert Campbell
@jayrulez
new project system?
that's new new csproj format?
DW01
@DW01
Yeah first thing I noticed was all reference to SS was dropped from the source tree, haha
xen2
@xen2
so in practice, editor + runtime is MIT, only launcher isn't (but of course, nothing prevents you from creating your own distribution channel inside your company if you want)
YotPhiligan
@YotPhiligan
SDK style msbuild
Robert Campbell
@jayrulez
also, what will the new version number be? 3.0 :)?
xen2
@xen2
yes
Daniel Keenan
@dfkeenan
Aww, man. The launcher was one of the things I wanted to fix something in.
xen2
@xen2
let me think about it, but probably I wouldn't mind giving private access to a few people
or even open it but with a different license
Daniel Keenan
@dfkeenan
I only wanted to make it so you could remove projects from the list.
That's been annoying me since it was released.
xen2
@xen2
might be good to at least have an issue tracker for it quickly
xen2
@xen2
@jayrulez yes the new csproj format
Xenko is now a packageref: <PackageReference Include="Xenko" Version="3.0.0.1-dev"/>
Robert Campbell
@jayrulez
That's awesome. So I can use .net standard libs now?
xen2
@xen2
little bit later down the road I want to split libraries to each have its own package
game project is still net461
but you can reference net standard libs I think
just adjust the project type if you want
Robert Campbell
@jayrulez
Yep. That's fine. I want to share a lib between my .net core game server and the xenko project