Skip to content

Cannot use "new" library in .net 4.8 #4735

Closed
@Danielku15

Description

@Danielku15

Describe the bug
Currently the NuGet libraries provided by this project for .net 4.8 are forwarding the implementation to the System.ServiceModel coming with .net 4.8 itself. This makes migration really hard because there is no good way to already start using dotnet/wcf + CoreWCF already.

To Reproduce
Steps to reproduce the behavior:

  1. Setup a .net 4.8 solution with a server and client project inside.
  2. Use CoreWCF for the server and the NuGet System.ServiceModel.* for the client
  3. Notice that the NuGet Packages are actually causing a reference to the .net 4.8 built-in System.ServiceModel
  4. Struggle migrating your code to the next-gen libraries to upgrade to .net core as a next step.

Expected behavior
We need a way to enforce usage of the new client-side-only libraries through NuGet without pulling the full-framework WCF including the server parts.

Screenshots

Additional context
We cannot yet change our project to actually be .net5.0 or .net6.0 due to a bigger scale rework ongoing which we need to do gradually across all our company wide products and libraries. We would like to first migrate to the new CoreWCF for Server and System.ServiceModel NuGets for client but stay on .net4.8.

Even if we make a .netstandard2.0 library project and consume the nugets and then use it in our main .net 4.8 application, the main application still pulls/references the .net 4.8 WCF libs.

NuGet does not provide a proper way to force usage of .netstandard2.0 libs for individual packages. There are only hacks where you need to spoil your whole solution tree with additional custom references. Therefore my hope lies here on the package authors side to provide a way to consume the new packages and provide a migration path away from the full framework WCF.

Metadata

Metadata

Assignees

Labels

customer assistanceHelp customers with questions regarding usage of WCF features.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions