-
-
Notifications
You must be signed in to change notification settings - Fork 20
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
PR for fundamental core structure changes #51
Conversation
…rageFileEventListener as obsolete. Also added additional extra methods for EventLogger to support passing exceptions.
…ated for minimum target support.
…olete attribute. Updated MvvmLight library to use .NET Standard variant
…form specific locators.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me, can't see any issues.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some changes need to be made here and added some questions.
...iews.Controls.HeaderedTextBlock.Forms/MADE.App.Views.Controls.HeaderedTextBlock.Forms.csproj
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good for these to be merged
Describe the changes made
This PR contains fundamental changes to the MADE App Components libraries which are described below.
Changes to minimum target version
Changes have been made to target the lowest minimum target version of .NET Standard and UWP so that the libraries can be installed with more projects.
This change sees the .NET Standard version lower from 2.0 to 1.4 and the UWP version to cover all versions instead of Fall Creators Update+
Changes to incorporate XPlat
Other changes associated with this PR include adding support for XPlat where MADE was using custom built alternatives. These changes have been kept to a minimum but as a co-owner of the project, I suggest that we start incorporating XPlat as the base API layer for building controls and other functions in MADE.
Some examples include:
MADE has a helper class for UI action dispatching which uses native APIs. XPlat contains a CoreDispatcher which does the same thing so has been replaced with it for consistency.
MADE has a color, thickness and orientation class. XPlat contains alternatives which are cross-platform and have been replaced where used.
Changes to NuGet package references
All package references have been updated to the latest versions.
The UWP libraries have been downgraded to a supported version (6.1.9).
Included as part of this change has been to replace the older PCL variant of MvvmLight with the .NET Standard version. This will have a breaking change on users who are currently using this as the CommonServiceLocator is no longer used which is described here: http://www.mvvmlight.net/std10
There currently is an issue outstanding in the MvvmLight project that users who are implementing Android functionality and use the MvvmLight android support extension cannot use this. There is an active PR for this (lbugnion/mvvmlight#25) but has been open since March last year.
There is also an open PR from myself with MvvmLight regarding Android support packages references (lbugnion/mvvmlight#60) with a PR (lbugnion/mvvmlight#61) which have not yet been resolved.
@tom-made would it be wise if we forked MvvmLight and created our own internal packages to resolve these issues?
What issues are associated?
No associated issues