dotnet / dotnet/wcf

dotnet-svcutil failing when the project references a project reference to a .vbproj project

Open
#4,785 2 comments 1 reaction 2 assignees Assigned to @mconnew View on GitHub
Dominant language
C#
Stars
1.8k
Forks
576
Avg merge
6d 9h
Merged PRs (30d)
2

Description

We recently updated our .net 4.5 project to .net 4.8 and choose to update the project file to an SDK style project and that broke our service references. We cannot update the service references anymore from visual studio.

After a long search found this link to a community issue and that pointed us to us the "dotnet-svcutil" cli tool

This is how our project file looks like:

```


net48
..\..\..\Binaries\




----
-----
------




----
----
----



```

Tried to run the svcutil tool to update the service reference of one of the service references and we are running into this error:

```
pathtoprojectfile>dotnet-svcutil -u ServiceReferenceName
Microsoft (R) WCF Service Model Proxy Generation Tool for .Net Core platform
[Microsoft.Tools.ServiceModel.Svcutil, Version 2.0.3]
Copyright (c) Microsoft Corporation. All rights reserved.

This tool collects information about how it is used in order to improve the tool. This functionality can be disabled by setting the environment variable "DOTNET_SVCUTIL_TELEMETRY_OPTOUT" to 1.

Error: The specified parameter value '..\..\..\folder1\folder2\project1.vbproj' is not valid. Parameter name: 'filePath'.

If you would like more help, type "dotnet-svcutil -h"
```

Is this because we have a vb project referenced? Is there any workaround for this issue?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.