❓ Is your feature request related to a problem?
Currently, solution files require explicitly listing each individual file. This becomes tedious and hard to maintain, especially when working with directories containing many files or frequently changing content.
For example, instead of being able to use a wildcard pattern like:
<Solution>
<Folder Name="/Documentation/">
<File Path="docs/Documents/*.md" />
</Folder>
</Solution>instead of
<Solution>
<Folder Name="/Documentation/">
<File Path="docs/Documents/architecture.md" />
<File Path="docs/Documents/detailed-design.md" />
</Folder>
</Solution>💡 Describe the solution you'd like
Add support for wildcard patterns (e.g., *.md) in the File path within solution files. This would allow developers to include multiple files dynamically without listing each one explicitly.
This feature would:
- Reduce manual effort
- Improve maintainability
- Make solution definitions more flexible and concise
Alternatives considered
It is possible to add a csproj to the solution that points to the files as a workaround:
<Project>
<ItemGroup>
<None Include="**\*.md;**\*.png;**\*.jpg;**\*.jpeg;**\*.gif;**\*.svg;**\*.bmp;**\*.ico;**\*.webp" Exclude="bin\**\*;obj\**\*;node_modules\**\*;dist\**\*;*.csproj" />
</ItemGroup>
</Project>Please see the following screenshot:
❓ Is your feature request related to a problem?
Currently, solution files require explicitly listing each individual file. This becomes tedious and hard to maintain, especially when working with directories containing many files or frequently changing content.
For example, instead of being able to use a wildcard pattern like:
instead of
💡 Describe the solution you'd like
Add support for wildcard patterns (e.g., *.md) in the File path within solution files. This would allow developers to include multiple files dynamically without listing each one explicitly.
This feature would:
Alternatives considered
It is possible to add a csproj to the solution that points to the files as a workaround:
Please see the following screenshot:
