Building multiple msbuild projects which inherit the same projects
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1k
- Forks
- 167
- PR merge metrics
- No merged PRs in 30d
Description
Hi, if I would do the case I listed in the title I get a issue where Build specification 'PATH\Components\X\X.csproj' is owned by two modules: 'Y' and 'Z'
To resolve the issue, remove ownership for module configuration files at 'PATH\Components\Y' or at 'PATH\Components\Z
Is there any way to get around this error without putting all my other 80 projects into one fileNameEntryPoints array which still builds each project each change.
Any help would be appreciated!
resolvers: [
{
kind: "MsBuild",
root: d`Components/Y`,
moduleName: "Y",
fileNameEntryPoints: [r`Y.csproj`]
},
{
kind: "MsBuild",
root: d`Components/Z`,
moduleName: "Z",
fileNameEntryPoints: [r`Z.csproj`]
}
]
});
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the MsBuild resolver configuration shown for Components/Y and Components/Z and trace how the shared X.csproj is assigned ownership. Done means separate module configurations can build the projects without the “owned by two modules” error, without requiring all projects in one fileNameEntryPoints array.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100