Msbuild not copying a ProjectReference to bin folder
To prevent circular dependency, i had to make a reference from (lets say) project A, to B's bin folder. When i run a rebuild or build in Visual Studio it creates bin folder and required dll references by A, under B project.
But msbuild command does not work that way. It does not create bin and dlls under B. I investigate the problem, found some solutions like using dummy class user method to make msbuild copy references under bin. But it did not work too.
Project A -> Project B/bin/C Dlls ->Project C
Project C Dlls required by Project A.
What do i have to do to make msbuild command create bin folder under B project?
dll build msbuild bin
asked Nov 21 '18 at 9:14
metzeldermetzelder
118424
add a comment |
To prevent circular dependency, i had to make a reference from (lets say) project A, to B's bin folder. When i run a rebuild or build in Visual Studio it creates bin folder and required dll references by A, under B project.
But msbuild command does not work that way. It does not create bin and dlls under B. I investigate the problem, found some solutions like using dummy class user method to make msbuild copy references under bin. But it did not work too.
Project A -> Project B/bin/C Dlls ->Project C
Project C Dlls required by Project A.
What do i have to do to make msbuild command create bin folder under B project?
dll build msbuild bin
asked Nov 21 '18 at 9:14
metzeldermetzelder
118424
1
You're not preventing a circular dependency, you're propagating it by circumventing the safeguards. The only real solution is to refactor the projects to remove the circular dependency.
– daughey
Nov 27 '18 at 21:48
Yes, you are correct. I had to refactor all the project hierarchy and problem solved that way. You can post your comment as an answer.
– metzelder
Nov 29 '18 at 10:28
add a comment |
To prevent circular dependency, i had to make a reference from (lets say) project A, to B's bin folder. When i run a rebuild or build in Visual Studio it creates bin folder and required dll references by A, under B project.
But msbuild command does not work that way. It does not create bin and dlls under B. I investigate the problem, found some solutions like using dummy class user method to make msbuild copy references under bin. But it did not work too.
Project A -> Project B/bin/C Dlls ->Project C
Project C Dlls required by Project A.
What do i have to do to make msbuild command create bin folder under B project?
dll build msbuild bin
asked Nov 21 '18 at 9:14
metzeldermetzelder
118424
To prevent circular dependency, i had to make a reference from (lets say) project A, to B's bin folder. When i run a rebuild or build in Visual Studio it creates bin folder and required dll references by A, under B project.
But msbuild command does not work that way. It does not create bin and dlls under B. I investigate the problem, found some solutions like using dummy class user method to make msbuild copy references under bin. But it did not work too.
Project A -> Project B/bin/C Dlls ->Project C
Project C Dlls required by Project A.
What do i have to do to make msbuild command create bin folder under B project?
dll build msbuild bin
dll build msbuild bin
asked Nov 21 '18 at 9:14
metzeldermetzelder
118424
asked Nov 21 '18 at 9:14
metzeldermetzelder
118424
asked Nov 21 '18 at 9:14
metzeldermetzelder
118424
asked Nov 21 '18 at 9:14
metzeldermetzelder
118424
asked Nov 21 '18 at 9:14
metzeldermetzelder
118424
118424
1
You're not preventing a circular dependency, you're propagating it by circumventing the safeguards. The only real solution is to refactor the projects to remove the circular dependency.
– daughey
Nov 27 '18 at 21:48
Yes, you are correct. I had to refactor all the project hierarchy and problem solved that way. You can post your comment as an answer.
– metzelder
Nov 29 '18 at 10:28
add a comment |
1
You're not preventing a circular dependency, you're propagating it by circumventing the safeguards. The only real solution is to refactor the projects to remove the circular dependency.
– daughey
Nov 27 '18 at 21:48
Yes, you are correct. I had to refactor all the project hierarchy and problem solved that way. You can post your comment as an answer.
– metzelder
Nov 29 '18 at 10:28
1
1
You're not preventing a circular dependency, you're propagating it by circumventing the safeguards. The only real solution is to refactor the projects to remove the circular dependency.
– daughey
Nov 27 '18 at 21:48
You're not preventing a circular dependency, you're propagating it by circumventing the safeguards. The only real solution is to refactor the projects to remove the circular dependency.
– daughey
Nov 27 '18 at 21:48
Yes, you are correct. I had to refactor all the project hierarchy and problem solved that way. You can post your comment as an answer.
– metzelder
Nov 29 '18 at 10:28
Yes, you are correct. I had to refactor all the project hierarchy and problem solved that way. You can post your comment as an answer.
– metzelder
Nov 29 '18 at 10:28
add a comment |
1 Answer
1
active
oldest
votes
It looks like the circular dependency is still present. It has only been circumvented by going directly to the bin folder. This bypasses the safeguards that call out a circular dependency at build time.
As a general rule, if you need to go directly to the bin folder then there's a problem.
I suggest refactoring the projects to remove the circular dependency.
answered Nov 29 '18 at 12:00
daugheydaughey
43039
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53408646%2fmsbuild-not-copying-a-projectreference-to-bin-folder%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
It looks like the circular dependency is still present. It has only been circumvented by going directly to the bin folder. This bypasses the safeguards that call out a circular dependency at build time.
As a general rule, if you need to go directly to the bin folder then there's a problem.
I suggest refactoring the projects to remove the circular dependency.
answered Nov 29 '18 at 12:00
daugheydaughey
43039
add a comment |
It looks like the circular dependency is still present. It has only been circumvented by going directly to the bin folder. This bypasses the safeguards that call out a circular dependency at build time.
As a general rule, if you need to go directly to the bin folder then there's a problem.
I suggest refactoring the projects to remove the circular dependency.
answered Nov 29 '18 at 12:00
daugheydaughey
43039
add a comment |
It looks like the circular dependency is still present. It has only been circumvented by going directly to the bin folder. This bypasses the safeguards that call out a circular dependency at build time.
As a general rule, if you need to go directly to the bin folder then there's a problem.
I suggest refactoring the projects to remove the circular dependency.
answered Nov 29 '18 at 12:00
daugheydaughey
43039
It looks like the circular dependency is still present. It has only been circumvented by going directly to the bin folder. This bypasses the safeguards that call out a circular dependency at build time.
As a general rule, if you need to go directly to the bin folder then there's a problem.
I suggest refactoring the projects to remove the circular dependency.
answered Nov 29 '18 at 12:00
daugheydaughey
43039
answered Nov 29 '18 at 12:00
daugheydaughey
43039
answered Nov 29 '18 at 12:00
daugheydaughey
43039
answered Nov 29 '18 at 12:00
daugheydaughey
43039
43039
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53408646%2fmsbuild-not-copying-a-projectreference-to-bin-folder%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
You're not preventing a circular dependency, you're propagating it by circumventing the safeguards. The only real solution is to refactor the projects to remove the circular dependency.
– daughey
Nov 27 '18 at 21:48
Yes, you are correct. I had to refactor all the project hierarchy and problem solved that way. You can post your comment as an answer.
– metzelder
Nov 29 '18 at 10:28