Closed Barsonax closed 4 years ago
Is there already an issue for updating sample packages to have a link to their source path on GitHub, so people can browse it easily? If not, please create and link to this one.
There is now #794, still open for creative ideas.
In order to move forward with duality we have to find a way to make dualities way of managing packages compatible with .netnstandard en .netcore.
As it already turned out the nuget upgrade is very painful, so much that I don't really see this upgrade happening anymore.
This issue is to research a completely different approach in which we actually remove the build in package manager from duality. Instead managing packages will be done like any other .NET project, from a csproj.
This has a number of advantages:
Some disadvantages:
Most optimal solution would be to stay as close to a default csproj as possible, which means I would lean more towards modifying duality to fit with the default instead of csproj wizardry.
Work has begun on a poc duality template https://github.com/Barsonax/DualityProjectTemplate