Problem
Currently, the original MS targets for publishing a package expect an ImportConfig.xml being present in the package folder. The SDK however builds the import config based on the PDPackage project's dependencies - project references and package references.
This forces the standard template ImportConfig.xml to be present in the repository, while it's not expected to be manually edited ever.
Proposal
Build the ImportConfig.xml in the intermediate directory and allow this file to be missing so it doesn't pollute the repository.
If the ImportConfig.xml is present, it should be respected as it might force some changes against the auto-calculated import config. I believe that's the current behavior.
Context
Priority: LOW - not causing any issues right now.
Problem
Currently, the original MS targets for publishing a package expect an
ImportConfig.xmlbeing present in the package folder. The SDK however builds the import config based on thePDPackageproject's dependencies - project references and package references.This forces the standard template
ImportConfig.xmlto be present in the repository, while it's not expected to be manually edited ever.Proposal
Build the ImportConfig.xml in the intermediate directory and allow this file to be missing so it doesn't pollute the repository.
If the
ImportConfig.xmlis present, it should be respected as it might force some changes against the auto-calculated import config. I believe that's the current behavior.Context
Priority: LOW - not causing any issues right now.