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

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,

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,

I’ve been unable to get it to work. I have the latest version installed as done an update already. Currently using Visual Studio 2017 v15.8 Preview 2. Any idea on how I would be able to add this service reference?

@mlacouture Thanks a lot, I looked up the installation folder by looking at the file properties of Visual Studio shortcut and it seems to be installed in another folder than I expected: C:\Program Files\Microsoft Visual Studio\2017\Professional\Common7\IDE\Extensions\Microsoft\WCF Connected Service\svcutil\

I confirm now that the workaround works! So we also await Visual Studio 2017 v15.8 Preview 2.

We are planning to provide a fix for this with the release of Visual Studio 2017 v15.8 Preview 2 which is currently scheduled for 05/30.

This issue still persists in VS 15.7 preview 4. The project is using .NET Core version 2.1.300-preview2-008533