.NET Core published app fails with FileNotFoundException
up vote
3
down vote
favorite
I have a .NET Core console app with target netcoreapp2.1. It calls into an existing WCF service using the Windows Compatibility Pack.
When I run it through Visual Studio, or if I use dotnet run to run it from the command line, it works fine.
However, I want to publish it to a .exe file so that I can run it by double-clicking it.
So, I ran the Publish which appears to succeed, but when I try to run the published .exe file it fails with the following exception:
System.IO.FileNotFoundException: Could not load file or assembly
'System.Private.ServiceModel, Version=4.1.2.1, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.
This error happens on the machine that I ran the publish on, and also if I try copying the published folder to another machine. I believe that System.Private.ServiceModel is some sort of deep dependency of the Microsoft.Windows.Compatibility package, but why is this not working? Surely it should have been copied to the output folder automatically?
Is there additional configuration or setup required to get the publish to pull in dependencies automatically?
If it matters, the reference in the csproj file looks like this:
<ItemGroup>
<PackageReference Include="Microsoft.Windows.Compatibility" Version="2.0.1" />
</ItemGroup>
c# .net-core publish
add a comment |
up vote
3
down vote
favorite
I have a .NET Core console app with target netcoreapp2.1. It calls into an existing WCF service using the Windows Compatibility Pack.
When I run it through Visual Studio, or if I use dotnet run to run it from the command line, it works fine.
However, I want to publish it to a .exe file so that I can run it by double-clicking it.
So, I ran the Publish which appears to succeed, but when I try to run the published .exe file it fails with the following exception:
System.IO.FileNotFoundException: Could not load file or assembly
'System.Private.ServiceModel, Version=4.1.2.1, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.
This error happens on the machine that I ran the publish on, and also if I try copying the published folder to another machine. I believe that System.Private.ServiceModel is some sort of deep dependency of the Microsoft.Windows.Compatibility package, but why is this not working? Surely it should have been copied to the output folder automatically?
Is there additional configuration or setup required to get the publish to pull in dependencies automatically?
If it matters, the reference in the csproj file looks like this:
<ItemGroup>
<PackageReference Include="Microsoft.Windows.Compatibility" Version="2.0.1" />
</ItemGroup>
c# .net-core publish
add a comment |
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I have a .NET Core console app with target netcoreapp2.1. It calls into an existing WCF service using the Windows Compatibility Pack.
When I run it through Visual Studio, or if I use dotnet run to run it from the command line, it works fine.
However, I want to publish it to a .exe file so that I can run it by double-clicking it.
So, I ran the Publish which appears to succeed, but when I try to run the published .exe file it fails with the following exception:
System.IO.FileNotFoundException: Could not load file or assembly
'System.Private.ServiceModel, Version=4.1.2.1, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.
This error happens on the machine that I ran the publish on, and also if I try copying the published folder to another machine. I believe that System.Private.ServiceModel is some sort of deep dependency of the Microsoft.Windows.Compatibility package, but why is this not working? Surely it should have been copied to the output folder automatically?
Is there additional configuration or setup required to get the publish to pull in dependencies automatically?
If it matters, the reference in the csproj file looks like this:
<ItemGroup>
<PackageReference Include="Microsoft.Windows.Compatibility" Version="2.0.1" />
</ItemGroup>
c# .net-core publish
I have a .NET Core console app with target netcoreapp2.1. It calls into an existing WCF service using the Windows Compatibility Pack.
When I run it through Visual Studio, or if I use dotnet run to run it from the command line, it works fine.
However, I want to publish it to a .exe file so that I can run it by double-clicking it.
So, I ran the Publish which appears to succeed, but when I try to run the published .exe file it fails with the following exception:
System.IO.FileNotFoundException: Could not load file or assembly
'System.Private.ServiceModel, Version=4.1.2.1, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.
This error happens on the machine that I ran the publish on, and also if I try copying the published folder to another machine. I believe that System.Private.ServiceModel is some sort of deep dependency of the Microsoft.Windows.Compatibility package, but why is this not working? Surely it should have been copied to the output folder automatically?
Is there additional configuration or setup required to get the publish to pull in dependencies automatically?
If it matters, the reference in the csproj file looks like this:
<ItemGroup>
<PackageReference Include="Microsoft.Windows.Compatibility" Version="2.0.1" />
</ItemGroup>
c# .net-core publish
c# .net-core publish
asked Nov 22 at 0:38
gallivantor
185129
185129
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
1
down vote
accepted
I had the same problem and I've manually added from nuget the missing file by installing the System.Private.ServiceModel package.
Link on nuget.org.
This is a hack though, because from the description of the package you can see that it's meant for .Net internal usage, but I didn't find any other options.
Yep that works - but it worries me what other assemblies have potentially been missed and might then cause runtime errors in the application. I've raised this with the dotnet team here: github.com/dotnet/cli/issues/10381
– gallivantor
Nov 23 at 4:04
add a comment |
up vote
0
down vote
Add in vsstudio nuget package
Install-Package System.Private.ServiceModel
Now when you publish dll will be included.
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',
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%2f53422385%2fnet-core-published-app-fails-with-filenotfoundexception%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
I had the same problem and I've manually added from nuget the missing file by installing the System.Private.ServiceModel package.
Link on nuget.org.
This is a hack though, because from the description of the package you can see that it's meant for .Net internal usage, but I didn't find any other options.
Yep that works - but it worries me what other assemblies have potentially been missed and might then cause runtime errors in the application. I've raised this with the dotnet team here: github.com/dotnet/cli/issues/10381
– gallivantor
Nov 23 at 4:04
add a comment |
up vote
1
down vote
accepted
I had the same problem and I've manually added from nuget the missing file by installing the System.Private.ServiceModel package.
Link on nuget.org.
This is a hack though, because from the description of the package you can see that it's meant for .Net internal usage, but I didn't find any other options.
Yep that works - but it worries me what other assemblies have potentially been missed and might then cause runtime errors in the application. I've raised this with the dotnet team here: github.com/dotnet/cli/issues/10381
– gallivantor
Nov 23 at 4:04
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
I had the same problem and I've manually added from nuget the missing file by installing the System.Private.ServiceModel package.
Link on nuget.org.
This is a hack though, because from the description of the package you can see that it's meant for .Net internal usage, but I didn't find any other options.
I had the same problem and I've manually added from nuget the missing file by installing the System.Private.ServiceModel package.
Link on nuget.org.
This is a hack though, because from the description of the package you can see that it's meant for .Net internal usage, but I didn't find any other options.
answered Nov 22 at 5:57
Mihail Stancescu
3,42411018
3,42411018
Yep that works - but it worries me what other assemblies have potentially been missed and might then cause runtime errors in the application. I've raised this with the dotnet team here: github.com/dotnet/cli/issues/10381
– gallivantor
Nov 23 at 4:04
add a comment |
Yep that works - but it worries me what other assemblies have potentially been missed and might then cause runtime errors in the application. I've raised this with the dotnet team here: github.com/dotnet/cli/issues/10381
– gallivantor
Nov 23 at 4:04
Yep that works - but it worries me what other assemblies have potentially been missed and might then cause runtime errors in the application. I've raised this with the dotnet team here: github.com/dotnet/cli/issues/10381
– gallivantor
Nov 23 at 4:04
Yep that works - but it worries me what other assemblies have potentially been missed and might then cause runtime errors in the application. I've raised this with the dotnet team here: github.com/dotnet/cli/issues/10381
– gallivantor
Nov 23 at 4:04
add a comment |
up vote
0
down vote
Add in vsstudio nuget package
Install-Package System.Private.ServiceModel
Now when you publish dll will be included.
add a comment |
up vote
0
down vote
Add in vsstudio nuget package
Install-Package System.Private.ServiceModel
Now when you publish dll will be included.
add a comment |
up vote
0
down vote
up vote
0
down vote
Add in vsstudio nuget package
Install-Package System.Private.ServiceModel
Now when you publish dll will be included.
Add in vsstudio nuget package
Install-Package System.Private.ServiceModel
Now when you publish dll will be included.
answered Nov 23 at 13:54
Grzegorz J
133
133
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53422385%2fnet-core-published-app-fails-with-filenotfoundexception%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