Directory.Build.props not working when solution contains Framework and Core projects
I want all the projects within a solution to share the same version number. If I add a Directory.Build.props file at the root of the solution, it copies the file to each project as expected. While all the projects will build fine, I get a "publish" error on the Core projects. It says:
Directory.Build.props could not be loaded. '', hexadecimal value 0x1A, is an invalid character. Line 5, position 11
Line 5, position 11 is the end of the file.
I believe this is the end-of-file marker. If, however, I create the same Directory.Build.props file in the root of the Core project, it's fine. The issue is "where" I create the file.
All the other projects (Framework 4.7.1) publish fine with the Directory.Build.props file created in the root of the solution.
I know I could change the folder structure of my solution so Core projects are in one folder, and framework projects are in another. Then create a separate Directory.Build.props file for each "type" of project, but that's a hassle. Is there a workaround for this?
c# .net-core version
asked Jan 2 at 18:09
MatthewMatthew
1
add a comment |
I want all the projects within a solution to share the same version number. If I add a Directory.Build.props file at the root of the solution, it copies the file to each project as expected. While all the projects will build fine, I get a "publish" error on the Core projects. It says:
Directory.Build.props could not be loaded. '', hexadecimal value 0x1A, is an invalid character. Line 5, position 11
Line 5, position 11 is the end of the file.
I believe this is the end-of-file marker. If, however, I create the same Directory.Build.props file in the root of the Core project, it's fine. The issue is "where" I create the file.
All the other projects (Framework 4.7.1) publish fine with the Directory.Build.props file created in the root of the solution.
I know I could change the folder structure of my solution so Core projects are in one folder, and framework projects are in another. Then create a separate Directory.Build.props file for each "type" of project, but that's a hassle. Is there a workaround for this?
c# .net-core version
asked Jan 2 at 18:09
MatthewMatthew
1
add a comment |
I want all the projects within a solution to share the same version number. If I add a Directory.Build.props file at the root of the solution, it copies the file to each project as expected. While all the projects will build fine, I get a "publish" error on the Core projects. It says:
Directory.Build.props could not be loaded. '', hexadecimal value 0x1A, is an invalid character. Line 5, position 11
Line 5, position 11 is the end of the file.
I believe this is the end-of-file marker. If, however, I create the same Directory.Build.props file in the root of the Core project, it's fine. The issue is "where" I create the file.
All the other projects (Framework 4.7.1) publish fine with the Directory.Build.props file created in the root of the solution.
I know I could change the folder structure of my solution so Core projects are in one folder, and framework projects are in another. Then create a separate Directory.Build.props file for each "type" of project, but that's a hassle. Is there a workaround for this?
c# .net-core version
asked Jan 2 at 18:09
MatthewMatthew
1
I want all the projects within a solution to share the same version number. If I add a Directory.Build.props file at the root of the solution, it copies the file to each project as expected. While all the projects will build fine, I get a "publish" error on the Core projects. It says:
Directory.Build.props could not be loaded. '', hexadecimal value 0x1A, is an invalid character. Line 5, position 11
Line 5, position 11 is the end of the file.
I believe this is the end-of-file marker. If, however, I create the same Directory.Build.props file in the root of the Core project, it's fine. The issue is "where" I create the file.
All the other projects (Framework 4.7.1) publish fine with the Directory.Build.props file created in the root of the solution.
I know I could change the folder structure of my solution so Core projects are in one folder, and framework projects are in another. Then create a separate Directory.Build.props file for each "type" of project, but that's a hassle. Is there a workaround for this?
c# .net-core version
c# .net-core version
asked Jan 2 at 18:09
MatthewMatthew
1
asked Jan 2 at 18:09
MatthewMatthew
1
asked Jan 2 at 18:09
MatthewMatthew
1
asked Jan 2 at 18:09
MatthewMatthew
1
asked Jan 2 at 18:09
MatthewMatthew
1
1
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Why not put the version attribute(s) in one file e.g. Version.cs, and reference that file using the "Add As link" drop down option in the "Add existing item..." window? this way you have the version only in one file
answered Jan 2 at 18:48
SirafSiraf
466314
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%2f54011140%2fdirectory-build-props-not-working-when-solution-contains-framework-and-core-proj%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
Why not put the version attribute(s) in one file e.g. Version.cs, and reference that file using the "Add As link" drop down option in the "Add existing item..." window? this way you have the version only in one file
answered Jan 2 at 18:48
SirafSiraf
466314
add a comment |
Why not put the version attribute(s) in one file e.g. Version.cs, and reference that file using the "Add As link" drop down option in the "Add existing item..." window? this way you have the version only in one file
answered Jan 2 at 18:48
SirafSiraf
466314
add a comment |
Why not put the version attribute(s) in one file e.g. Version.cs, and reference that file using the "Add As link" drop down option in the "Add existing item..." window? this way you have the version only in one file
answered Jan 2 at 18:48
SirafSiraf
466314
Why not put the version attribute(s) in one file e.g. Version.cs, and reference that file using the "Add As link" drop down option in the "Add existing item..." window? this way you have the version only in one file
answered Jan 2 at 18:48
SirafSiraf
466314
answered Jan 2 at 18:48
SirafSiraf
466314
answered Jan 2 at 18:48
SirafSiraf
466314
answered Jan 2 at 18:48
SirafSiraf
466314
466314
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%2f54011140%2fdirectory-build-props-not-working-when-solution-contains-framework-and-core-proj%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
