-
Notifications
You must be signed in to change notification settings - Fork 561
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.NET Standard 2.0, WCF Connected Service (Could not load file or assembly 'System.ServiceModel.Primitives, Version=4.2.0.0) #2546
Comments
I uploaded a sample solution demonstrating this: |
Hi @cabadam |
I was experiencing the same problem but in my case the console test app is also .net core 2.0... but then I realised that if I added System.ServiceModel.Primitives (followed by System.ServiceModel.Http) with NuGet, which gave me version 4.4.1 of each it worked. I'm new to working with .Net core and finding this all a bit confusing right now! |
This is an issue for me because I have a 'connected service' in my ASP.NET Core 2 web application. If I remove the connected service. |
Same for me, but the exception is thrown when I connect to WCF service impersonated. Without impersonation works without issues. |
WCF Connected Service would add "System.ServiceModel.Http" NuGet package to your netstandard2.0 library but this dependency won't be picked up by your console app project even it does reference to that netstandard2.0 library. The workaround is adding the same "System.ServiceModel.Http" NuGet package to your console app project by yourself so it would be referenced correctly. You can do this by using "Manage NuGet Package" menu item or just updating the packages.config file, for example <?xml version="1.0" encoding="utf-8"?> Please let me know if this solution working for you. |
@MSGaryWang I'll try it next week |
@MSGaryWang I had the exact same problem as the issue creator and for me your advice was at least a workaround to get things done. Thank you for that! |
@MSGaryWang That solved the issue for me. Thanks. |
@MSGaryWang I can confirm this does workaround the issue. For clarity: Is manually adding these references the intended solution? Or is the dependency supposed to be picked up automatically? (I'm hoping for the latter) |
We will pass this issue to another team since this is not a WCF only problem but how netstandard library integrated with other project. |
I am also facing the same issue. I am using window forms not the WCF. Please could you assist to solve this issue. |
In my scenario I had a framework project referencing my netstandard library. I found that I had to add |
Which version you added reference for System.ServiceModel.Http and System.ServiceModel.Primitives from nuget packages. |
Actually - I believe that to use my Standard Library from netframework I only had to add I used System.ServiceModel.Http and System.ServiceModel.Primitives version 4.4.1 within my standard and dotnet core projects. Is your windows forms project netframework or standard? |
Related to dotnet/standard#410. |
What fixed the issue for me was adding:
After doing this I was finally able to use HttpClient in the WCF project. |
I have added these two packages from NuGet and its work for in .Net Console and MVC Core Web App but not working MVC 5 web application.
The application is just waiting for a response. So it's not supported for MVC 5 Application? |
This is essentially the same thing that was reported in #2111.
<TargetFrameworks>net462;netstandard2.0</TargetFrameworks>
Similar reports:
https://www.codeproject.com/Questions/1198295/Do-I-need-to-install-NuGet-package-on-NET-standard
https://social.msdn.microsoft.com/Forums/vstudio/en-US/954059c8-adb6-4fe2-939a-e60da1587545/do-i-need-to-install-nuget-package-on-net-standard-library-or-executable-project-or-both?forum=wcf
Even if the workaround were to work, I'm not sure that would be the right answer, as now two DLLs are created, one for .NET Standard 2.0, and one for .NET 4.6.2. That seems like it defeats the purpose of .NET Standard?
The text was updated successfully, but these errors were encountered: