Skip to content

Conversation

@imcarolwang
Copy link
Contributor

@imcarolwang imcarolwang commented Dec 15, 2023

Linked issue: #4381.

@imcarolwang imcarolwang marked this pull request as draft December 15, 2023 08:18
@imcarolwang imcarolwang marked this pull request as ready for review December 15, 2023 09:59
@imcarolwang imcarolwang marked this pull request as draft March 14, 2024 07:13
@HongGit HongGit added the PR DO NOT MERGE If for whatever reason you do not want a PR merged. label Aug 22, 2024
@InteXX
Copy link

InteXX commented Dec 17, 2024

I missed the 1-year anniversary for this PR, but only by a few days.

We're still hoping for its adoption.

@InteXX
Copy link

InteXX commented Oct 24, 2025

@imcarolwang

Hi Carol, what's the status with this? Is there still a possibility that it might make it into production?

@DualBrain
Copy link

+1

1 similar comment
@skurth
Copy link

skurth commented Oct 27, 2025

+1

@InteXX
Copy link

InteXX commented Oct 27, 2025

@HongGit

Could you tell us more about the DO NOT MERGE label that you added?

What does that signal regarding the intent for this PR?

@geneb
Copy link

geneb commented Oct 30, 2025

This needs to happen. :)

@InteXX
Copy link

InteXX commented Oct 30, 2025

@KathleenDollard

Hi Kathleen, do you have any visibility into this?

@InteXX
Copy link

InteXX commented Nov 18, 2025

@skurth

Thank you for your participation in this. It's an important feature.

What's next? Is there a way to follow its progress up the pipeline?

@skurth
Copy link

skurth commented Nov 18, 2025

@InteXX Sorry, I just tried something, I'm not from Microsoft.
I also hope there is finally a reaction from them...

@InteXX
Copy link

InteXX commented Nov 18, 2025

@skurth

Sorry, I just tried something, I'm not from Microsoft

Oh, OK.

@InteXX
Copy link

InteXX commented Nov 18, 2025

@skurth

I also hope there is finally a reaction from them

Also, in case you haven't seen it, I've submitted this as a Visual Studio feature request (although oddly things seem to be progressing slowly over there as well).

You can follow it and vote on it if you like here.

@InteXX
Copy link

InteXX commented Nov 18, 2025

@imcarolwang

Carol, it'd be nice to hear from you regarding your pull request.

Is there a way we can get this to the attention of the people who can make it happen?

@skurth
Copy link

skurth commented Nov 18, 2025

@skurth

I also hope there is finally a reaction from them

Also, in case you haven't seen it, I've submitted this as a Visual Studio feature request (although oddly things seem to be progressing slowly over there as well).

You can follow it and vote on it if you like here.

Thank you, I have already done it some days ago.

Hi @mconnew
Maybe you can help us here. Reference: #4381
You wrote:

There are two possible solutions for you, the hard one and the easy one. The hard one is to contribute the code to the dotnet-svcutil utility that the connected services tool is based on (it's in this repo now) to support those other languages. If on the other hand you can't spare several months of your life to this noble cause, you could generate your WCF client into a library project of it's own and then reference that project from your F# or VB applications.

There has been a PR open for two years to generate WCF client code in VB, so the work already appears to be done. Is it possible to merge this PR?

@InteXX
Copy link

InteXX commented Nov 18, 2025

@skurth

Thank you, I have already done it some days ago.

Aha. Yes, I saw that one. Well stated. I remember being impressed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

PR DO NOT MERGE If for whatever reason you do not want a PR merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants