4,103 questions
It is discussed here.
Adding Connected WCF Service to .NET 3.1 project results in access denied error
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(41.6, 74%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
ScottM
331
Reputation points
I have a .NET core 3.1 project in VS2019. Attempting to add a connected service reference for a legacy WCF service. However, it blows up during scaffolding with access denied error even though I am running VS2019 as administrator.
Importing web service metadata ...
Scaffolding service reference code ...
ErrorAccess to the path 'C:\Users\myuser\AppData\Local\Temp\WCFConnectedService\2021_Oct_29_11_01_02\svcutil_starter\nuget.config' is denied.
Done.
ErrorFailed adding service reference(s). Index (zero based) must be greater than or equal to zero and less than the size of the argument list.
Looking at the nuget.config, you can clearly see that it is a readonly file. I can remove the readonly attribute and try again but it doesn't affect the outcome since this folder is auto generated on each service reference attempt.
Please help.
Microsoft Visual Studio Professional 2019
Version 16.11.5
VisualStudio.16.Release/16.11.5+31729.503
Microsoft .NET Framework
Version 4.8.04084
Installed Version: Professional
Windows 10 19042.1165
Developer technologies .NET Other
Developer technologies C#
11,568 questions
3 answers
Sort by: Most helpful
-
-
ScottM 331 Reputation points
2021-10-29T18:14:46.143+00:00 I checked but neither my solution or project level folders have a nuget.config. So no idea how the nuget.config is causing a readonly error.
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 32%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMT%3C/text%3E%3C/svg%3E)
Michael Taylor 60,161 Reputation points2021-10-29T18:18:52.91+00:00 If you're relying on any packages then you have a global nuget.config that it is using. Follow the recommendation given in the issue to create a brand new, empty solution and project to generate the svc reference (or just run the svcutil tool directly) and the move that code into your project.
You can use the aforementioned link to report the issue to the team for your specific scenario.
Sign in to comment -
-
ScottM 331 Reputation points
2021-10-29T18:38:29.227+00:00 Checked and the global nuget.config does not have a readonly attribute.
-
Michael Taylor 60,161 Reputation points
2021-10-29T19:43:14.787+00:00 Please use the Reply option when replying to answers so it is easier to track the conversations.
Taking a look at the
svcutilcode the tool is creating a temp project in order to build the code. This requires some Nuget work so it is looking for the file to use. The bootstrapper creates the temp directory and then tries to copy theglobal.jsonandnuget.configfiles from the current project to the temp directory. It only does that if there is not already a file in the temp directory. Clearly it is getting past this point.I think you might be able to see more information if you run the tool directly so you can enable more detailed logging. Try running the dotnet-svcutil tool from your project directory. It should replicate what the UI is doing I believe. You can pass parameters to enable more detailed logging and whatnot.
-
ScottM 331 Reputation points
2021-10-30T00:14:29.047+00:00 Running svcutil manuallly from the cli prompt works for some reason.
Sign in to comment -