-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version rollback needs investigating and sample; app cast filtering needs sample #294
Comments
Applicable code: NetSparkle/src/NetSparkle/Configurations/Configuration.cs Lines 26 to 29 in e2eacf9
NetSparkle/src/NetSparkle/AppCastHandlers/XMLAppCast.cs Lines 172 to 178 in e2eacf9
Might be just as easy as adding a public setter (don't want to break things by changing |
Really need to also add a sample for how to use the new filtering process on beta/stable channels along with this, as version rollback and a beta/stable channel feature can both use the new filtering process. |
Oh, and also please look at MainWindow.xaml.cs in the
NetSparkle.Samples.HandleEventsYourself - I started with an implementation
there, I could just extend that.
…--
John Clayton
On Mon, 6 Jun 2022 at 00:06, Deadpikle ***@***.***> wrote:
Really need to also add a sample for how to use the new filtering process
on beta/stable channels along with this, as version rollback and a
beta/stable channel feature can both use the new filtering process.
—
Reply to this email directly, view it on GitHub
<#294 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKXDUU7FYMLVBDVT72XV53VNUQEPANCNFSM5PPS74NQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
From @johncclayton on Gitter:
Need to investigate whether or not rollback to an old version of the app(s) is working as intended. Initially, the intent was that a user could always do this by loading the app cast into app cast items and then just manually choosing the version to load, but if the configuration setup with the current version is not allowing you to see old versions or versions less than the current binary, than we have a problem. Obviously, default behavior should be to only view newer versions.
The text was updated successfully, but these errors were encountered: