Problem
Project of type PDPackage allows to specify dependencies - package references and project references (published projects of type Solution to a nuget feed and local projects of type Solution). These dependencies are ordered in the PDPackage .csproj file, because their order determines the solution import order during package deployment.
This order should be respected in the ImportConfig.xml file, which is auto-generated by the dotnet publish command. Currently, the ImportConfig.xml file does not respect the order of dependencies specified in the PDPackage .csproj file. The order seems to be random for package references, while project references are correctly at the end of the ImportConfig.xml file. I wasn't verifying if the order of project references is correct, but I can see the the package references definitely aren't.
Context
Priority: MEDIUM - this can be fixed by providing a custom ImportConfig.xml file in the PDPackage project.
Problem
Project of type
PDPackageallows to specify dependencies - package references and project references (published projects of typeSolutionto a nuget feed and local projects of typeSolution). These dependencies are ordered in thePDPackage.csproj file, because their order determines the solution import order during package deployment.This order should be respected in the
ImportConfig.xmlfile, which is auto-generated by thedotnet publishcommand. Currently, theImportConfig.xmlfile does not respect the order of dependencies specified in thePDPackage.csproj file. The order seems to be random for package references, while project references are correctly at the end of theImportConfig.xmlfile. I wasn't verifying if the order of project references is correct, but I can see the the package references definitely aren't.Context
Priority: MEDIUM - this can be fixed by providing a custom
ImportConfig.xmlfile in thePDPackageproject.