Improvements in network configuration storing procedure

[MateuszKlatecki]

Description

Added check whether something changed in the network configuration and only in this case, write to Flash memory

Motivation and Context

• Removal of unnecessary write operations to Flash memory

How Has This Been Tested?

Screenshots

Types of changes

• Improvement (non-breaking change that improves a feature, code or algorithm)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

Signed-off-by: GITHUB_USER <GITHUB_USER_EMAIL>

[nfbot]

Hi @MateuszKlatecki,

I'm nanoFramework bot.
Thank you for your contribution!

A human will be reviewing it shortly. 😉

[josesimoes]

Nice improvement!

Can we improve this a bit further?
If, besides these, we compare the new settings with the existing ones and they are the same, there is no need to go through the update as there is nothing to actually update, right?!

As it is, on targets with flash storage, it's burning the config sector over and over needlessly.

[MateuszKlatecki]

You are right, we can go further and check whether any change has occurred and then save the configuration. I will try to code it.

[josesimoes]

Now it's much better and efficient! 👏