NuGet status for OxyPlot.Metro package?

Oystein Bjorke 6 years ago 0
This discussion was imported from CodePlex

cureos wrote at 2014-04-15 22:58:

Dear Oystein,

many many thanks for developing and sharing this terrific library!

I have planned to use it in my Windows Store application. However, I note that whereas the OxyPlot.Core library on NuGet is currently at version 2014.1.277.1 (from April 10), the OxyPlot.Metro library is still at version 2014.1.1.1 from January 7. Why is this? And what is the current status of the Metro library on CodePlex?

It seems like the latest Core library is not fully compatible with the latest Metro library; I get a "Method Not Found" exception when trying to plot a line series (unfortunately I do not have all the data for the crash right now, but I can bring it forward if you want me to).

Best regards,
Anders @ Cureos

objo wrote at 2014-04-16 07:44:

thanks for the notice! I will investigate this. We should also address this related issue:

cureos wrote at 2014-04-16 22:46:

I just checked OxyPlot.Metro on NuGet,, and I see that a new version is now released in sync with the latest Core library! Great job, Oystein, many many thanks for taking care of this issue so quickly.

I will upgrade to the latest version as soon as possible and give it some serious testing :-)

Best regards,
Anders @ Cureos

objo wrote at 2014-04-16 23:20:

yes, the package is updated, but I have not had time to test it yet. I only noticed that the generic.xaml file is no more generated.
Let us know if it is working or not!

cureos wrote at 2014-04-17 07:12:

Hmm, there seem to be a few issues with OxyPlot.Metro 2014.1.283.1:
  • My Windows Store app is targeted at Windows 8(.0), and it could successfully use version 2014.1.1.1. When I update OxyPlot.Metro to the latest version, the NuGet manager does not complain. But when I build the project, I get a warning that the OxyPlot.Metro package was built with an incompatible version, and I also get a compilation error in the auto-generated file related to my XAML view, claiming that "the namespace OxyPlot could not be found". Ideally, this incompatibility should have spotted already by NuGet Manager, right?
  • After retargeting my Windows Store app to Windows 8.1, building succeeds, except that the method "Plot.RefreshPlot()" is no longer available. In principle, I guess this is a good sign (I assume the plot is meant to update automatically in the general case)? However, all I see is a white sheet covering the entire plot area. No axes, no curves, no nothing. I tried to replace the "RefreshPlot()" call with "InvalidatePlot()", but to no avail.
I realize that this is not much to build debugging on. If you want more detailed information, just let me know what you need and I'll try to provide it. But for the time being I feel that it is best for me to revert to version 2014.1.1.1 again.

Best regards,

objo wrote at 2014-04-25 11:44:

  1. Is it possible to build for Windows 8.0 in VS 2013? The "target platform version" selector seems to be disabled.
  2. RefreshPlot has been removed, use InvalidatePlot. The plot is not updating automatically, you need to use the invalidate method.

cureos wrote at 2014-04-25 11:56:

Thanks for the response!
  1. The project was originally created with VS 2012, and I have not yet performed the upgrade for this project. I am not sure, but I believe that MS intends to support Windows 8.0 for a while longer, even though they encourage users to upgrade. Would it be possible to "downgrade" OxyPlot.Metro to Windows 8.0, or is it relying on new functionality in 8.1?
  2. OK, good to know.
As soon as possible, I will give the latest NuGet release another try. I'll report my findings after having tested it.

Best regards,

objo wrote at 2014-04-25 22:07:

  1. No, it is not relying on any 8.1 functionality. The build machine only has VS 2013 installed and I am worried that it will be difficult to build for 8.0 there. If anyone really needs support for 8.0, please add a request in the issue tracker.