Splitting library to remove dependency of Windows.Storage

[Ellerbach]

Description

Adjusting to remove Windows Storage by System.IO.FileSystem. Creating 2 nugets with one nanoFramework.WebServer which is independent of storage and one nanoFramework.WebServer.FileSystem which is dependant on it.

Motivation and Context

• Adjusting to remove Windows Storage by System.IO.FileSystem
• Will work on much more devices and Windows Storage is obsolete
• Creating 2 nugets with one nanoFramework.WebSer which is independent of storage and one nanoFramework.WebServer.FileSystem which is dependant on it

• Need to be tested
• Need to adjust the README
• Need to adjust the Samples repository

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 with code or algorithm)
• New feature (non-breaking change which adds functionality to code)
• Breaking change (fix or feature that would cause existing functionality to change)
• Config and build (change in the configuration and build system, has no impact on code or features)
• Dependencies (update dependencies and changes associated, has no impact on code or features)
• Unit Tests (add new Unit Test(s) or improved existing one(s), has no impact on code or features)
• Documentation (changes or updates in the documentation, has no impact on code or features)

Checklist:

• My code follows the code style of this project (only if there are changes in source code).
• My changes require an update to the documentation (there are changes that require the docs website to be updated).
• I have updated the documentation accordingly (the changes require an update on the docs in this repo).
• I have read the CONTRIBUTING document.
• I have tested everything locally and all new and existing tests passed (only if there are changes in source code).
• I have added new tests to cover my changes.

[josesimoes]

J

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[josesimoes]

LGTM! Another step towards a better quality in our libraries.
Thanks.