Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 12:11
    dotnet-maestro[bot] synchronize #4633
  • 12:11
    dotnet-maestro[bot] edited #4633
  • 12:11

    dotnet-maestro[bot] on darc-main-cf8995c2-4338-479a-8f1d-c34e2fbc962b

    Update dependencies from https:… (compare)

  • Jun 19 12:11
    dotnet-maestro[bot] synchronize #4633
  • Jun 19 12:11

    dotnet-maestro[bot] on darc-main-cf8995c2-4338-479a-8f1d-c34e2fbc962b

    Update dependencies from https:… (compare)

  • Jun 19 12:11
    dotnet-maestro[bot] edited #4633
  • Jun 18 21:48
    mconnew commented #4237
  • Jun 18 12:11
    dotnet-maestro[bot] synchronize #4633
  • Jun 18 12:11

    dotnet-maestro[bot] on darc-main-cf8995c2-4338-479a-8f1d-c34e2fbc962b

    Update dependencies from https:… (compare)

  • Jun 18 12:11
    dotnet-maestro[bot] edited #4633
  • Jun 18 08:46
    imcarolwang closed #4197
  • Jun 18 08:46
    imcarolwang commented #4197
  • Jun 18 08:06
    imcarolwang closed #4216
  • Jun 18 08:06
    imcarolwang commented #4216
  • Jun 17 12:11

    dotnet-maestro[bot] on darc-main-cf8995c2-4338-479a-8f1d-c34e2fbc962b

    Update dependencies from https:… (compare)

  • Jun 17 12:11
    dotnet-maestro[bot] synchronize #4633
  • Jun 17 12:11
    dotnet-maestro[bot] edited #4633
  • Jun 16 21:38

    HongGit on main

    Fix type reuse authentication i… (compare)

  • Jun 16 21:38
    HongGit closed #4093
  • Jun 16 21:38
    HongGit closed #4634
2007 🙂
Matt Connew
@mconnew
There will be no difference on resource allocation on the server side as it won't actually close the connection any quicker using RS. If you call close asynchronously on WCF it won't hold any threads either.
Steve
@steve:ash.mn
[m]
except this is the opposite scenario being reported
they are saying when they turn RS on that it blocks
Matt Connew
@mconnew
That's because WCF runs fast and loose with some of the RS settings. For example, you can configure ordered execution to true or false, but it's always true. The original devs never implemented the unordered execution mode. It makes the session bookkeeping a lot harder to implement so everything is always ordered. And as RS basically undoes a little of the fire and forget as it ensures the method actually is completed (to make it reliable), making it ordered kills the fire and forget aspect.
But that post pre-dates my working on WCF so I never got to see it.
Matt Connew
@mconnew
I've done some playing with your repo and been thinking about it and this is actually expected behavior. When a channel is closed, it needs to wait for all outstanding requests to complete. This is because it would cleanup resources which might be used by the service call via OperationContext.Current. It's because TCP is a sessionful transport so it needs to wait for the session to complete it's work before the session can be closed. Basically you can't close a session when the session is in use.
Steve
@steve:ash.mn
[m]
That meshes - I seem to remember seeing documentation about it at some point that basically said you have to use RS for OneWay if you want an immediate return. I'm going to play with backgrounding the close and see how that works out.
Matt Connew
@mconnew
I doubt that was official documentation. RS is just backgrounding the close so doesn't buy you anything.
Willow
@DarkAngel766
Package 'dotnet-svcutil 2.0.3-preview1.20574.1' has a package type 'DotnetTool' that is not supported by project <Core 3.1 blazor site>.
Steve
@steve:ash.mn
[m]
@DarkAngel766: svcutil is a dotnet global tool, not a package to be referenced with <PackageReference>
You can install it with the command line: dotnet tool install --global dotnet-svcutil --version 2.0.3-preview1.20574.1 then run dotnet svcutil to generate service references
Willow
@DarkAngel766
unfortunately, I cannot run dotnet from command line and access nuget
this kind of kills me
Steve
@steve:ash.mn
[m]
What is is you are trying to do?
Willow
@DarkAngel766
Access an IBM SOAP service
I have the WSDL, but it just spins
the service requires credentials also
Steve
@steve:ash.mn
[m]
You should also might be able to add using the connected services feature in visual studio
Willow
@DarkAngel766
is what I'm doing
so, this started with "Unable to create deps.json". After running restore, it just started spinning, so debugging has led me to this package
image.png
this is where it hangs...
Willow
@DarkAngel766
is there another delivery method aside from nuget?
Steve
@steve:ash.mn
[m]
That I am not sure
Willow
@DarkAngel766
this is not a package issue. thanks. I understand my problem and I don't believe you guys can resolve it (it's an internal infosec nazi thing)
aka, problem is on my wire
Steve
@steve:ash.mn
[m]
😀 those are always fun problems to solve
Willow
@DarkAngel766
ikr?
80% of my issues are from those guys lol
yowl
@yowl
@DarkAngel766 Probably wont help, but I have some services that I can't add using the connected services feature in my solution, but if I create a new solution, then they work. I just have to patch up the classes where I want it to reuse types.
Willow
@DarkAngel766
I was able to get past that issue with the svcutil preview:
dotnet tool install --global dotnet-svcutil --version 2.0.3-preview1.20574.1
thanks though :)
Steve
@steve:ash.mn
[m]
mconnew (Matt Connew): any idea when the memory leak with reliable sessions one way will get resolved? I’m looking at possibly switching to manually backgrounding the close channel but there are some complexities with the deployment of this service that might make changing the binding service side difficult.
Matt Connew
@mconnew
I've got a couple of issues at the head of my queue, then I'll be returning to that. It's taken some time to mull around in my head how to solve it, and I think I know how to do it now.
Steve
@steve:ash.mn
[m]
Awesome. I wish I understood the WCF stack a bit better and could have taken a better stab at it myself.
Matt Connew
@mconnew
The issue is AsyncLock. Getting it correct so that it's reentrant is the tricky bit. But you can't just be naively reentrant as Task's can fork, so a generation value needs to be tracked and incremented every time it's re-entered. It's some tricky bookkeeping.
yowl
@yowl
@mconnew Thanks for https://www.nuget.org/packages/Capri/ . It has saved me a lot of effort
Matt Connew
@mconnew
You doing async message inspectors?
yowl
@yowl
I'm using it to add a forms authentication cookie to a request from a netcoreapp. Mixing some old stuff with some new stuff
Not exciting, but useful nonetheless
Arnas Kučinskas
@Arnas-Kucinskas
WCF connected service references does not interact with your project references in any way?
Let's say service is using a lot of similar packages, but uses old version of them. My project uses newest versions of same packages. It shouldn't matter, right?
Matt Connew
@mconnew
The package management system will use the highest dependency in the transitive set with one exception. Your main executable project (the one with the Main method) overrides any transitive versions. So if AppA references LibA which references nuget package Foo v2.0.0, and AppA also references LibB which references nuget package Foo v2.5.0, then the app will use Foo v2.5.0. But if AppA has a direct dependency on package Foo v1.0.0, then that overrides the indirect dependencies and will force downgrade everyone to using Foo v1.0.0
Matt Connew
@mconnew
If your question is about compatibility of types between client and server, it's all kind of duck typed. The actually used type is generally not even emitted as part of the xml (it can in some situations like when the property is an Object and using KnownTypeAttribute), but even when it is provided, the type info isn't .NET type info, it's XML Schema types. If the DOM types in the assemblies haven't changed, or haven't changed in an incompatible way (eg renaming of fields), then WCF doesn't care about the exact assembly version.
Billy Mumby
@mumby0168
Hi all, anyone able to help with a proxy authentication issue, have a WebProxy object populated with a NetworkCredential that on an old .net framework wcf client could be assigned via a property, using .net core this option does not seem to be available. Anyone know the alternative in .net core?
Billy Mumby
@mumby0168
After some more playing around I want to be using Ntlm proxy auth but no matter what properties I set on it nothing get's passed out via the header any ideas?
Matt Connew
@mconnew
We'll be adding the api for WebProxy in an upcoming release. In the meantime, you can modify the HttpClientHandler directly to set the WebProxy using a technique similar to what's mentioned in this blog post (cached from Bing as original seems to be down right now): https://cc.bingj.com/cache.aspx?q=https%3a%2f%2fjustsimplycode.com%2f2019%2f11%2f02%2fdisable-header-100-continue-in-net-core-wcf-client%2f&d=4644406031231684&mkt=en-US&setlang=en-US&w=5CQTrI2_39lACFghB6Q_yONgBWqE1Xt9
It shows how to modify the HttpClientHandler. You don't need the intercepting handler, you can just modify the passed in HttpClientHandler in the GetHttpMessageHandler method.