These are chat archives for AvaloniaUI/Avalonia

24th
Dec 2017
Jeremy Koritzinsky
@jkoritzinsky
Dec 24 2017 03:24
@kekekeks any chance you saw the conversation David Fowler and I just had on the nearest-wins issue on NuGet/Home? Sounds like consumers of Avalonia won't have an issue with package downgrade unless we do or one of our dependencies does. Basically for us to be at fault for the downgrade warning, we'd have to resolve a downgrade warning we get by keeping the downgrade. It's an odd design I agree, but it seems like it won't affect us in terms of giving a good UX to our users.
Nikita Tsukanov
@kekekeks
Dec 24 2017 08:19
@jkoritzinsky we are already encountering this issue with AvalonStudio
And if you try to use Avalonia 0.5 with .NET Core 2.0
You'll get somewhat like 20 package downgrade errors
The problem is that if we reference anything from "bcl" packages from nuget
And new SDK will reference the same package using transitive dependencies
our references might take precedence over them
and cause downgrade errors
Matthijs ter Woord
@mterwoord
Dec 24 2017 09:37
that's even the case if avalonia references >= version ?
Nikita Tsukanov
@kekekeks
Dec 24 2017 09:45
yep
something-something transitive dependencies, something-something nearest-wins
Matthijs ter Woord
@mterwoord
Dec 24 2017 09:47
ok.
Matthijs ter Woord
@mterwoord
Dec 24 2017 12:58
Alrighty, made a repro case for my templating/visual tree issue with current master.. See #1333
any ideas would be greatly appreciated..
Jeremy Koritzinsky
@jkoritzinsky
Dec 24 2017 18:45
Those errors though are in Microsoft's packages I'm pretty sure though. It's not our issue. Also can you post some of those package tree examples in that issue on the NuGet page so they can see what's happening (and if it should be happening)?
Nikita Tsukanov
@kekekeks
Dec 24 2017 21:05
<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>exe</OutputType>
    <TargetFramework>netcoreapp2.0</TargetFramework>
    <RuntimeIdentifiers>win7-x64;ubuntu.14.04-x64;osx.10.10-x64</RuntimeIdentifiers>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Avalonia" Version="0.5.1"/>
    <PackageReference Include="Avalonia.Desktop" Version="0.5.1"/>
  </ItemGroup>

</Project>
run dotnet restore
it will give you tons of errors related to Microsoft.Extensions.DependencyModel
Nikita Tsukanov
@kekekeks
Dec 24 2017 21:12
I'd prefer to stay away from "bcl" packages and only use netstandard or libraries that depend only on netstandard