question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unable to add connected services in 2.1 Preview (Error: Version for package dotnet-svcutil could not be resolved)

See original GitHub issue

Create New Web Application using Core 2.1 Preview. (Angular Application)

Attempt to add connected services.

Error: Version for package dotnet-svcutil could not be resolved.

Switch version to Core 2.0 attempt to add service (Completes successfully)

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:3
  • Comments:30 (14 by maintainers)

github_iconTop GitHub Comments

8reactions
mlacouturecommented, Apr 25, 2018

Hi @sliceofbytes Thank you again for reporting this problem; it is very unfortunate that this was not fixed; I’m sorry about it.

I can offer a workaround while the fix for this issue is released in case you absolutely need to run this for NET Core v2.1:

Locate the temporary folder created by the WCF Web Service Reference connected service after the failure, and fix up the nuget.config file generated on this folder, the folder path should look like the following:

%USERPROFILE%\AppData\Local\Temp\WCFConnectedService\2018_Apr_24_16_00_36\svcutil_starter

Edit the nuget.config to fix the location (directory) of the svcutil nuget package, it should look like the following after the fix:

<configuration>
  <packageSources>
    <add key="SvcUtilLocalFeed" value="<VSINSTALLDIR>\Common7\IDE\EXTENSIONS\MICROSOFT\WCF Connected Service\svcutil" />
  </packageSources>
</configuration>

Now from this directory restore the dotnet-svcutil NuGet package by running the following command: >dotnet restore

Once you complete all these steps you should be able to run the WCF Web Service Reference wizard successfully.

Observe that this workaround is not a supported scenario so it should not be treated as a permanent solution.

I hope this helps,

1reaction
mlacouturecommented, Oct 25, 2018

Hi @avesse Based on the error message it seems you are adding the tool as a PackageReference to the project instead of a DotNetCliToolReference,. See the Getting Started page for details on how to setup the tool. If that’s not the case, can you run the tool with the debug verbosity and provide the log file? you may want to restore nuget packages for the project first. thanks,

Read more comments on GitHub >

github_iconTop Results From Across the Web

c# - Cannot install dotnet-svcutil with VIsual Studio 2019 to ...
1 Answer 1 · i don't have admin rights and neither proxy url... IT said me that i have to tell vs to...
Read more >
WCF dotnet-svcutil tool for .NET Core
NET tool that retrieves metadata from a web service on a network location or from a WSDL file, and generates a WCF class...
Read more >
dotnet-svcutil 2.1.0
dotnet tool install --global dotnet-svcutil --version 2.1.0. This package contains a .NET tool you can call from the shell/command line.
Read more >
VS2022 Service Reference Error MSBuild & ...
I'm using VS 2022 (17.3.4) to add a Connected Service WCF Web Servcie to a .net standard 2.0 project. The Service reference configuration ......
Read more >
Using CoreWCF to Move WCF Services to .NET Core
If you've ported to CoreWCF and you find operational bugs (not missing features), Product Support coordinates a fix. Using CoreWCF in Practice.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found