These are chat archives for Ruhrpottpatriot/GW2.NET

15th
May 2016
Robert Logiewa
@Ruhrpottpatriot
May 15 2016 16:06
@ErikHumphrey If you don't have the GW2Bootstrapper, you probably should've updated your NuGet Package.
@StevenLiekens Thanks! I'll check it out. Still, there is one problem. DotNetAnalyzers don't work with .NETCore, or at least they didn't a while back. Need to check that.
Steven Liekens
@StevenLiekens
May 15 2016 16:08
almost nothing works with .NETCore as of today
especially not RC2
but they are shipping RC2 in the next few days
Robert Logiewa
@Ruhrpottpatriot
May 15 2016 16:09
yeah. But Analyzers were particular stange, since in .NETCore every file is included if it's on the disk. No option to hide files if you want. You need to delete them
Steven Liekens
@StevenLiekens
May 15 2016 16:09
you can exclude files
Robert Logiewa
@Ruhrpottpatriot
May 15 2016 16:10
oh
is that possible now?
Steven Liekens
@StevenLiekens
May 15 2016 16:11
"buildoptions": {
  "compile": {
    "exclude": "path/or/pattern/**/*.cs"
  }
}
Robert Logiewa
@Ruhrpottpatriot
May 15 2016 16:13
hm
if you exclude from compile, no analyzer based on rosly should run on that file
need to check the analyzers page
Steven Liekens
@StevenLiekens
May 15 2016 16:13
oh
I don't know how that works
Robert Logiewa
@Ruhrpottpatriot
May 15 2016 16:14
since Roslyn analyzers run on each file pre (or post) build.
It didn't work on .NETCore, since there was something wonky with how that system handled files
but that is months old now
Steven Liekens
@StevenLiekens
May 15 2016 16:15
yeah forget everything you knew about DNX projects
Robert Logiewa
@Ruhrpottpatriot
May 15 2016 16:15
huh?
I havn't looked at dnx a while now
Steven Liekens
@StevenLiekens
May 15 2016 16:15
well it's dead
Robert Logiewa
@Ruhrpottpatriot
May 15 2016 16:15
what changed (changes) with RC2?
huh?
ok
Steven Liekens
@StevenLiekens
May 15 2016 16:15
there will be no more DNX in RC2
Robert Logiewa
@Ruhrpottpatriot
May 15 2016 16:15
elaborate
Steven Liekens
@StevenLiekens
May 15 2016 16:16
they replaced dnx/dnu with the dotnet CLI
project.json and .xproj remains the same for RC2 but they will also be gone before RTM
they are bringing .csproj back
Robert Logiewa
@Ruhrpottpatriot
May 15 2016 16:17
you have a link to the page?
Steven Liekens
@StevenLiekens
May 15 2016 16:17
let me see
Robert Logiewa
@Ruhrpottpatriot
May 15 2016 16:17
ty
but csproj is no json, not xml based?
Steven Liekens
@StevenLiekens
May 15 2016 16:17
but to cut a long story short
they will bring back XML projects because that is what works best with msbuild
Robert Logiewa
@Ruhrpottpatriot
May 15 2016 16:17
hm
shame
Steven Liekens
@StevenLiekens
May 15 2016 16:17
project.json will disappear
although they are considering keeping it around for nuget config
project.json might be renamed to nuget.json
and there will be no more packages.config
anyway what I'm trying to say is
they are moving settings out of project.json and back into xproj
and xproj will become csproj
Robert Logiewa
@Ruhrpottpatriot
May 15 2016 16:19
ok
I really need to look at it now
Steven Liekens
@StevenLiekens
May 15 2016 16:19
so that's planned for RTM
Robert Logiewa
@Ruhrpottpatriot
May 15 2016 16:20
did they finally clean up the number of frameworks?
Steven Liekens
@StevenLiekens
May 15 2016 16:20
yes
Robert Logiewa
@Ruhrpottpatriot
May 15 2016 16:20
good
Steven Liekens
@StevenLiekens
May 15 2016 16:20
now there is only netstandard1.0 to netstandard1.4 for compatibility with legacy crap
and netstandard1.5 for all current platforms
Robert Logiewa
@Ruhrpottpatriot
May 15 2016 16:21
ok, if you could give me the explanation page, I'd be really grateful
I'm a bit confused right now
yeah me too
yaaay
empty
Steven Liekens
@StevenLiekens
May 15 2016 16:22
haha
Robert Logiewa
@Ruhrpottpatriot
May 15 2016 16:24
so basically, if i understood it correctly: We switch to the latest netstandard and go on from there?
Steven Liekens
@StevenLiekens
May 15 2016 16:24
no, we switch to the lowest
for maximum compatibility
Robert Logiewa
@Ruhrpottpatriot
May 15 2016 16:24
that'd be netcore?
Steven Liekens
@StevenLiekens
May 15 2016 16:25
I think the lowest we can do is netstandard1.3
because HttpClient is 1.3
Robert Logiewa
@Ruhrpottpatriot
May 15 2016 16:25
ah ok
ah
there's the explanation
Steven Liekens
@StevenLiekens
May 15 2016 16:32
netstandard1.3.png
purple are the platforms we cannot support
Robert Logiewa
@Ruhrpottpatriot
May 15 2016 16:33
ok
Steven Liekens
@StevenLiekens
May 15 2016 16:33
I forgot to make Mono green
oh well
Robert Logiewa
@Ruhrpottpatriot
May 15 2016 17:53
ok
seriously
native .NET compilation on almost every OS?
This message was deleted
AWESOME!
and it seems we can even compile it, so we don't need .NetCore installed
Steven Liekens
@StevenLiekens
May 15 2016 18:15
yup