Skip to content

Using Microsoft WCF Web Service Reference Provider: "Reference cannot be loaded" errors #2326

@rpokrovskij

Description

@rpokrovskij

Class library AdminkaV1 (.NET Standard 2.0) is referenced in class library "WcfClient" (.NET Standard 2.0) (as well as in WCF App project .NET Framework 4.7). as "Project reference" and want to be used in "Reuse types in referenced assemblies" when Microsoft WCF Web Service Reference Provider (ver 0.5,10808.800, VS 2017) generates proxy.

Expected behavior: classes from AdminkaV1 are reused

Actual behavior: classes from AdminkaV1 where not reused (instead proxy classes were generated), and there are some strange entries in the log.

[10/3/2017 11:54:13.892 AM] Scaffolding service reference code ...
[10/3/2017 11:54:40.806 AM] Warning: Reference cannot be loaded: 'AdminkaV1.LoggingDom.WcfClient', Could not load file or assembly 'AdminkaV1.LoggingDom.WcfClient, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
[10/3/2017 11:54:40.806 AM]
[10/3/2017 11:54:40.806 AM] Warning: Reference cannot be loaded: 'AdminkaV1', Could not load file or assembly 'AdminkaV1, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
[10/3/2017 11:54:40.807 AM]
[10/3/2017 11:54:40.808 AM] Warning: Reference cannot be loaded: 'Routines', (.NET Standard 2.0) 'Routines, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.

So the question is: how libraries actually should be referenced to be accessed for "Microsoft WCF Web Service Reference Provider" if not "as project"?

P.S. If I reference AdminkaV1 library as a file (using Browse dialog to debug version) - classes from AdminkaV1 are reused (works nice). So only "project reference" doesn't work... Why?

Metadata

Metadata

Assignees

Labels

toolingAn issues related to any tool shipped from this repo.

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions