Building multiple msbuild projects which inherit the same projects
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- build-system
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.
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`]
}
]
});- Dominant language
- C#
- Stars
- 1k
- Forks
- 168
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from microsoft/BuildXL
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 28/100
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
All issues in microsoft/BuildXL
Similar issues
-
再現済み 要トリアージ 誤判定
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
yksr-melt/Meltype#421 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Facepunch/sbox-public#12063 · 1 comment ·
Maintainers usually reply within 2 days
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
facioquo/stock-indicators-dotnet#2316 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
eriknihlen/OpenAC#219 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ObsidianMC/Obsidian#548 ·
Maintainers usually reply within 1 day