OpenSource library–Dependencies

Part 1

Implement Open-source library guidance

Part 2

OpenSource library – Cross-platform targeting

Part 3

OpenSource library-Dependencies

Part 4

OpenSource library- Source Link

Part 5

OpenSource library-versioning

Part 6

OpenSource library- Breaking changes

Part 7

OpenSource library- conclusion

Now trying to respect what it says at https://docs.microsoft.com/en-us/dotnet/standard/library-guidance/dependencies .

Nr

Recomandation

AOP Roslyn

1

DO review your .NET library for unnecessary dependencies.

 Done manually(1)

2

DO NOT have NuGet package references with no minimum version

 Done already(2)

3

AVOID NuGet package references that demand an exact version

 Done already(2)

4

AVOID NuGet package references with a version upper limit

 Done already(2)

5

CONSIDER referencing shared source packages for small, internal pieces of functionality

 N/A(5)

6

CONSIDER making your package a shared source package if it provides small, internal pieces of functionality.

 N/A(5)

7

DO reference shared source packages with PrivateAssets=”All”.

 N/A(5)

8

DO NOT have shared source package types in your public API.

 N/A(5)

9

DO NOT publish shared source packages to NuGet.org.

 N/A(5)

For (1): Reviewing .NET library for unnecessary dependencies is practically a manual process. Could be a dotnet global tool – but for the moment I just inspected the .csproj for references and see that all are ncessary

For (2): As I read from documentation “Typically, the package reference version in the project file is the minimum version and there’s no maximum.” .So doing nothing I am at the good point

For (5), I usually put a new dll or NuGet package – I do not share code source. So this is done also without friction.