Is Avalonia11 supported?

[Ipqbfmgu]

Is Avalonia11 supported?

[VisualMelon]

See https://github.com/oxyplot/oxyplot-avalonia/issues/65

Edit: some clearer notes at the bottom of this issue: https://github.com/oxyplot/oxyplot-avalonia/issues/66#issuecomment-2249983868

[rehakmatej]

Hi, any new info about Avalonia 11 support?

[petryaevve]

Maybe author can update nuget

[aboimpinto]

The "merge" to Avalonia 11 was last year, and since then, no work has been done ... maybe some of us could merge the project. make the changes and create a new Nuget package. I don't see that the Author will be back to maintain this package.

[VisualMelon]

Per #65, you need to use the 2.1.0-Avalonia11 package

dotnet add package Oxyplot.Avalonia --version 2.1.0-Avalonia11

There are additional notes on style changes in the same thread.

How we will deal with the 10/11 divide going forward is not clear.

[aboimpinto]

Hello, and thanks for the answer. I tried that, but it didn't work, so I wrote my answer.

1. Is the new version compatible with dotnet 8? I'm evaluating the migration to Avalonia11 and dotnet 8, and looks like this tool is not ready for this

2. Not even the code in GitHub works I cloned the GitHub code, and not even that worked on my machine. I could go from there and try to make it work for my setup and possibly propose a PR, but I'm having problems there.

3. I'm familiar with the problems regarding maintenance of the OpenSource projects Can you guys share the problems that you are having? Is financing? Are developers? Is what? Maybe it could be developers and companies that are willing to help. Without talking, there is no way to solve the issues. I'm not the only one with this problem, and I'm sure I'm not willing to help.

thanks Paulo Aboim Pinto

[VisualMelon]

I wasn't aware the existing package had such issues: I'll look into today.

1. Should be; I use it against .NET 8 for Work, but I don't know which Avalonia version we're on at the moment
2. If you can share what you were trying that would be useful (versions of avalonia etc.)
3. Problem from my side is mostly that I don't have the time and energy to sink into design work; fixing stuff that's just fundamentally broken is much easier though

[aboimpinto]

The main problem is with the examples. I have some issues accessing avaloniaUI Nuget repository.

I could not run any other example than AvaloniaExamples

In the end, to make it work, I just added the OxyPlot.Avalonia, to my project, changed the TargetFrameowork to net8.0 and added the new Style referenced in the example, and it's working.

[VisualMelon]

Looks like you have the Avalonia nightly stream configured: if you disable that in the list of Nuget sources it should go through. (I've removed the NuGet.config that was causing this now)

Testing on Win10, can't find any obvious problems running the code-base under Avalonia 11.0.0 or 11.1.0 with .NET 8. Did you get it to work with the package then?

[aboimpinto]

not with the package ... I will try again ...

[VisualMelon]

Minimal example using 2.1.0-Avalonia11 package; changes commented with the word "Added": https://gist.github.com/VisualMelon/d23a49b41ad020d8cb73ca8cec4ebd68

I can make a repo and put the changes from the template in a commit if it would help people.

---

Steps

1. Add OxyPlot.Avalonia 2.1.0-Avalonia11 package reference: any of these should work:
   • Add <PackageReference Include="OxyPlot.Avalonia" Version="2.1.0-Avalonia11" /> to the csproj
   • Run dotnet add package OxyPlot.Avalonia --version 2.1.0-Avalonia11, specifying the project if necessary
   • Add it via IDE (e.g. in VisualStudio)
     • If you can't see this version, make sure the UI isn't filtering pre-release nuget packages
2. Add StylesInclude to App.xaml styles: <StyleInclude Source="avares://OxyPlot.Avalonia/Themes/Default.axaml"/>
3. Add xml-namespace xmlns:oxy="using:OxyPlot.Avalonia" in XAML as necessary
4. Add a OxyPlot.PlotModel somewhere, and bind it to the Model of an oxy:PlotView: make sure it has at least the Title property set otherwise it will be blank
5. Run to make sure something is presented (or slap build and check the designer, though this hasn't always been 100% reliable)
6. If you want to use anything from OxyPlot.Core 2.1.2 that isn't in 2.1.0, you can add a separate reference to it: everything should be compatible