-
Notifications
You must be signed in to change notification settings - Fork 556
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
svcutil dosen't work with .NET6 #4766
Comments
Similar problem with the dotnet cli:
|
Any news on this? |
After further research, the issue appears to be when targeting netstandard2.0 results with this error (as shown in the original message in this thread)
Seems like the simple solution is to add to the generated csproj file |
Hello, there is some progress in remove this bug? |
@paulviks0x30 - While we wait for them to fix (or merge my pull request), you can pull / build from my fork. That fixed it for me, probably will fix your issue if the error message you see in this thread (lang version) was your error also. @imcarolwang had issued a run on it about 8 days ago, so they may merge the fix, but not sure how long. |
Thanks @TWhidden for the fork, works fine for me. Would like to see the fix in a release, is there any update/plan on when a fix will be released @imcarolwang ? |
When will this be available in a release? |
@HongGit & @imcarolwang—any comments/updates will be greatly appreciated. |
@HongGit, @imcarolwang Can you give any update on when the new version will be available? Is there anything currently holding back the release? |
+1 |
1 similar comment
+1 |
Just ran into this issue as well. Would be nice to have a net6 compatible version. |
+1 |
1 similar comment
+1 |
Same issue here |
Any news on this 👀 ? |
+1 |
1 similar comment
+1 |
apparently an unofficial refusal of support |
@HongGit or @imcarolwang Can you please release the update? The PR has been merged for a while now, we're all just waiting for the release 😕 As you can see more and more developers need this update... And there will probably be many more migrating to .NET 6 and wondering why it doesn't work anymore... |
Sorry for the delay, we're working on it, it's coming soon! |
Any update about the release date please? |
The version with .NET6 support is finally released, you can try out by reinstalling the tool with commandlines below. Uninstall existing version: Install the new version: |
Can confirm this is working perfectly. Thanks! |
related I believe #4961 |
Close as dotnet-svcutil 2.1.0 is already released. |
Hello, I have the same issue, by trying to add a WCF Service Reference from visual studio, in a project with netstandar2.0. If I change the TargetFramework to .net6 it works. I know that you close the issue, but maybe this can help you to find the issue.
|
After installing the new Visual Studio 2022 with its .NET 6 features the dotnet-svcutils tools doesen't work anymore.
What i did:
dotnet-svcutil.exe https://myDomain.org/MyService?wsdl --outputFile SvcClient.cs --targetFramework netstandard2.0 --serializer XmlSerializer --namespace *,My.Service --enableDataBinding
After updating to the new svcutil (version 2.0.3) the same problem occures with a much longer log. Let me know if you ned that log to .
Then i cloned the Repository and added the .NET 6 Framework as additional build Target and tested with that local build.
new csproj
With these changes i was able to use the dotnet-svcutil tool without problems.
Is there any plan to support .NET6?
The text was updated successfully, but these errors were encountered: