.Net project build successful through VSTS. Deployment on Azure cloud gets failed because of Newtonsoft.json...
I am building a .Net project through VSTS (Azure DevOps) using the Visual Studio build plugin. The build is successful but when I am trying to deploy it shows the below error:
Could not load file or assembly Newtonsoft.json or its dependencies.
The located assembly's manifest definiton does not match the assembly
reference. (Exception from HRESULT: 0x80131040)
azure-devops edited Nov 26 '18 at 9:14
Shayki Abramczyk
4,32231129
asked Nov 26 '18 at 8:23
MuditMudit
1
add a comment |
I am building a .Net project through VSTS (Azure DevOps) using the Visual Studio build plugin. The build is successful but when I am trying to deploy it shows the below error:
Could not load file or assembly Newtonsoft.json or its dependencies.
The located assembly's manifest definiton does not match the assembly
reference. (Exception from HRESULT: 0x80131040)
azure-devops edited Nov 26 '18 at 9:14
Shayki Abramczyk
4,32231129
asked Nov 26 '18 at 8:23
MuditMudit
1
add a comment |
I am building a .Net project through VSTS (Azure DevOps) using the Visual Studio build plugin. The build is successful but when I am trying to deploy it shows the below error:
Could not load file or assembly Newtonsoft.json or its dependencies.
The located assembly's manifest definiton does not match the assembly
reference. (Exception from HRESULT: 0x80131040)
azure-devops edited Nov 26 '18 at 9:14
Shayki Abramczyk
4,32231129
asked Nov 26 '18 at 8:23
MuditMudit
1
I am building a .Net project through VSTS (Azure DevOps) using the Visual Studio build plugin. The build is successful but when I am trying to deploy it shows the below error:
Could not load file or assembly Newtonsoft.json or its dependencies.
The located assembly's manifest definiton does not match the assembly
reference. (Exception from HRESULT: 0x80131040)
azure-devops azure-devops edited Nov 26 '18 at 9:14
Shayki Abramczyk
4,32231129
asked Nov 26 '18 at 8:23
MuditMudit
1
edited Nov 26 '18 at 9:14
Shayki Abramczyk
4,32231129
asked Nov 26 '18 at 8:23
MuditMudit
1
edited Nov 26 '18 at 9:14
Shayki Abramczyk
4,32231129
edited Nov 26 '18 at 9:14
Shayki Abramczyk
4,32231129
edited Nov 26 '18 at 9:14
Shayki Abramczyk
4,32231129
4,32231129
asked Nov 26 '18 at 8:23
MuditMudit
1
asked Nov 26 '18 at 8:23
MuditMudit
1
asked Nov 26 '18 at 8:23
MuditMudit
1
1
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
from the screenshot you posted i guess that this error is after a successful deploy to you wepp application. You should check if newtonsoft dll is on the server(and which version). Also, if there is newtonsoft dll it might not be the same as on your local computer. Most likely you have the right version on your computer but you did not set the right parameters in app.config and package.config so the actual output package you got after building the solution does not have the right dll in it.
I would do clean rebuild, delete obj, bin and package folder on local machine and try to build it to see if there will be this error. After that you just need to set the right dependencies
answered Nov 26 '18 at 15:26
Angel StankovskiAngel Stankovski
11
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%2f53477109%2fnet-project-build-successful-through-vsts-deployment-on-azure-cloud-gets-faile%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
from the screenshot you posted i guess that this error is after a successful deploy to you wepp application. You should check if newtonsoft dll is on the server(and which version). Also, if there is newtonsoft dll it might not be the same as on your local computer. Most likely you have the right version on your computer but you did not set the right parameters in app.config and package.config so the actual output package you got after building the solution does not have the right dll in it.
I would do clean rebuild, delete obj, bin and package folder on local machine and try to build it to see if there will be this error. After that you just need to set the right dependencies
answered Nov 26 '18 at 15:26
Angel StankovskiAngel Stankovski
11
add a comment |
from the screenshot you posted i guess that this error is after a successful deploy to you wepp application. You should check if newtonsoft dll is on the server(and which version). Also, if there is newtonsoft dll it might not be the same as on your local computer. Most likely you have the right version on your computer but you did not set the right parameters in app.config and package.config so the actual output package you got after building the solution does not have the right dll in it.
I would do clean rebuild, delete obj, bin and package folder on local machine and try to build it to see if there will be this error. After that you just need to set the right dependencies
answered Nov 26 '18 at 15:26
Angel StankovskiAngel Stankovski
11
add a comment |
from the screenshot you posted i guess that this error is after a successful deploy to you wepp application. You should check if newtonsoft dll is on the server(and which version). Also, if there is newtonsoft dll it might not be the same as on your local computer. Most likely you have the right version on your computer but you did not set the right parameters in app.config and package.config so the actual output package you got after building the solution does not have the right dll in it.
I would do clean rebuild, delete obj, bin and package folder on local machine and try to build it to see if there will be this error. After that you just need to set the right dependencies
answered Nov 26 '18 at 15:26
Angel StankovskiAngel Stankovski
11
from the screenshot you posted i guess that this error is after a successful deploy to you wepp application. You should check if newtonsoft dll is on the server(and which version). Also, if there is newtonsoft dll it might not be the same as on your local computer. Most likely you have the right version on your computer but you did not set the right parameters in app.config and package.config so the actual output package you got after building the solution does not have the right dll in it.
I would do clean rebuild, delete obj, bin and package folder on local machine and try to build it to see if there will be this error. After that you just need to set the right dependencies
answered Nov 26 '18 at 15:26
Angel StankovskiAngel Stankovski
11
answered Nov 26 '18 at 15:26
Angel StankovskiAngel Stankovski
11
answered Nov 26 '18 at 15:26
Angel StankovskiAngel Stankovski
11
answered Nov 26 '18 at 15:26
Angel StankovskiAngel Stankovski
11
11
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%2f53477109%2fnet-project-build-successful-through-vsts-deployment-on-azure-cloud-gets-faile%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
