This changes from a viral copy of the ICU4N.targets file to putting the file in the buildTransitive folder within the NuGet package. The feature can be disabled by excluding the feature from the ICU4N PackageReference.
It would be best to allow the end consumer to be able to override this, but for now the best advice is to only exclude resources in the executable application that deploys them as files until we build more automation into the build process to pack custom resources. For all intermediate class libraries, it is best to leave the default settings.
This changes from a viral copy of the
ICU4N.targetsfile to putting the file in thebuildTransitivefolder within the NuGet package. The feature can be disabled by excluding the feature from the ICU4N PackageReference.It would be best to allow the end consumer to be able to override this, but for now the best advice is to only exclude resources in the executable application that deploys them as files until we build more automation into the build process to pack custom resources. For all intermediate class libraries, it is best to leave the default settings.