dotnet / dotnet/msbuild

Allow wildcard in AllowedReferenceRelatedFileExtensions

Open
#4,037 0 comments 0 reactions 0 assignees View on GitHub
triaged
Dominant language
C#
Stars
5.5k
Forks
1.5k
Avg merge
1d 13h
Merged PRs (30d)
133

Description

https://github.com/Microsoft/msbuild/blob/b630e674c729787d57a485ef5338915643eb1cea/src/Tasks/AssemblyDependency/ReferenceTable.cs#L873

When it comes to copying configuration files of referenced projects into the final output directory (of a solution's startup project), it would be nice if the startup project didn't need to list every possible configuration file extension that it needs to look for explicitly (such as `.development.json`, `production.json`, etc.). It would be much nicer to be able to write `.*.json` instead. Or just `.*` instead of `.json;.xml;.yml`, in the case that you don't want the project to be picky about what kind of config that it accepts. The same goes for files other than configuration.

This wouldn't be an issue if setting the config file properties to "copy always" did the trick, but this only works if the referenced project needs building. If it doesn't need building, then the build for the startup project will just skip it altogether and the config file doesn't get copied into the final output directory.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.