This is the first of the Windows implementation code that will be merged. This is only the driver code.
Also note the updates to the appveyor configuration. It now builds, installs and queries the status of driver directly on the build machine. Then it builds an 'artifact' which is essentially the binaries packaged up.
* Store active dataset and pending dataset in non-volatile memory.
* Retrieve active dataset and pending dataset from non-volatile memory after each reboot.
* Leader will generate the active dataset if it is not initialized.
* Clear pending dataset after it replaces active dataset.
* Create different pseudo flash files for posix nodes.
* otPlatform: New non-volatile settings API
This is the new API for the storage and retrieval of non-volatile
settings. Platforms would implement this API in order to allow various
types of information to be preserved across resets or power loss.
* fixup! otPlatform: New non-volatile settings API
Nick Banks