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.

Dotnet-svcutil & VS extension fails with dotnet 1.1

See original GitHub issue

The dotnet-svcutil.exe tool keeps failing on me. The error in the VS from Visual Studio WCF Connected Service extension is:

Scaffolding Code ...
Error:Error: MSBUILD : error MSB1003: Specify a project or solution file. The current working directory does not contain a project or solution file.
An error occurred while bootstrapping svcutil. This usually happens when processing references.  You might be able to work around this problem by not providing reference parameters, and manually removing any types redefined in the generated proxy code.

Failed to generate service reference.

Reading in the comments at the announcement page I have tried digging into the internals at: C:\Users\<name>\AppData\Local\Temp\WCFConnectedService\2016_Nov_17_16_07_08\svcutil_bootstrap\dotnet-svcutil

From the console doing dotnet -v restore . fails with: Error: MSBUILD : error MSB1003: Specify a project or solution file. The current working directory does not contain a project or solution file.

So I dug deeper, and found out that since I have dotnet 1.1 it looks for csproj at restore. So I put in the sdk in the global.json at 2016_Nov_17_16_07_08\svcutil_bootstrap. But the command actually overwrites that global.json. Any pointers on how to use this extension with the latest bits?

Note: have copied this comment over from that page for greater visibility

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Reactions:1
  • Comments:21 (8 by maintainers)

github_iconTop GitHub Comments

1reaction
lucky3commented, May 12, 2017

@zhenlan @hongdai @masaeedu thank you all for your help. I managed to get it work with VS2017 and copying reference to VS2015 project. Thanks again.

1reaction
zhenlancommented, May 12, 2017

@lucky3, just an idea, you can download and install WCF Connected Service for VS 2017, create a dummy .NET Core project, generate reference.cs using the tool and then copy the reference.cs back to your VS2015 project.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Dotnet-svcutil & VS extension fails with dotnet 1.1
The dotnet-svcutil.exe tool keeps failing on me. The error in the VS from Visual Studio WCF Connected Service extension is:
Read more >
Troubleshoot .NET tool usage issues
Possible reasons for this include: * You misspelled a built-in dotnet command. * You intended to execute a .NET program, but dotnet-xyz does...
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 >
Fixing issue related to Package is not compatible with ...
It clearly states that One or more packages are incompatible with .NETCoreApp,Version=v2.1.) This struck me as odd, as I know for a fact...
Read more >
how to resolve "Unable to find package" nuget error
First go to in Visual Studio 2019, Tools>Nuget Package ... dotnet nuget add source "https://api.nuget.org/v3/index.json" --name "NuGet ...
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