Does OxyPlot work in .NET 3.5?

Oct 11, 2013 at 6:14 PM
Is there any release of OxyPlot for .NET 3.5?

I couldn't find it in, but maybe there is an old version...
Oct 15, 2013 at 2:09 PM
No, there is no releases for .NET 3.5.
The core is PCL, and this is not supported by 3.5 (
You need to build the core for .NET 3.5 yourself.
The WPF, Winforms, pdf etc. libraries should also be possible to compile for 3.5.
Oct 15, 2013 at 8:17 PM
Hello objo,

I was also looking for any solution for .NET 3.5. So, could you please elaborate more on this how I can make my own libraries for .NET 3.5 (how to build the core for .NET 3.5 and so on)? I'm new to PCL stuff.

Thank you very much.
Oct 16, 2013 at 6:57 PM
Hi Objo

Can you clarify what you mean by "core" please?

Many thanks
Oct 17, 2013 at 11:14 PM
Hello Objo,

Based on your comment which said it should be possible to build oxyplot libraries for .NET 3.5, I started working on this.
I'm using 3 libraries (OxyPlot, OxyPlot.Wpf, OxyPlot.Xps) and I just made a new project with "Class Library" option for a OxyPlot and added all required files to the project to remove PCL stuff. (Seems you mentioned this to Core)
Now, it seems okay for this OxyPlot, but when I try to build WPF and XPS libraries by changing .net version to 3.5, it showed several errors which include "ManipulationCompletedEventArgs not defined"
I found that this was also supported from .NET 4.0, and others also looked something like this.
So, I would appreciate it if you could elaborate more on this procedure to make it working on .NET 3.5, and if I was doing something wrong, I hope you can correct me.

Thank you.
Oct 17, 2013 at 11:32 PM
Hello Andy and others,

I am no expert at Oxyplot, but as a developer I wouldn't try to change the source code to make it compatible to .NET 3.5.
  1. It will probably need tons of time to make it work, (if it work)
  2. There's going to be several bugs
  3. You will be by your on
  4. There is several other options, such as DynamicDataDisplay
If you do have time and you want to contribute to the community, go ahead, thats great. But wouldn't it be easier to just change your framework to .NET 4?
Also, if you want to contribute to the community, make sure your improvement or functionality is needed by other people. I suggested you contact the main developers of this project and try to include this feature in the product roadmap.
Oct 19, 2013 at 8:26 AM
I have added NET 3.5 project files for the core, WPF and XPS projects.
The WPF touch event handlers are moved into a partial class that is not compiled in the NET 3.5 project.
I am not adding the NET 3.5 solution into the build for NuGet, you need to build OxyPlot yourself if you want to use it with this version of the .NET framework.
Oct 19, 2013 at 4:25 PM
Thank you very much Objo.

So, if I understand correctly, maybe I should update to the latest build, then I can build my own NET 3.5 libraries without above issues.