H-Net | H-Net : Neural Network for Cross-domain Image Patch Matching

I am trying to query some local gRPC services running on HTTP. This is my net core 3.1 console app:

I want to trace complete execution of an HTTP request in golang. For any non trivial operation the request will eventually call many different functions. I would like to have logs from the entire execution stack tagged with a unique request id. e.g.

I'm trying to build a service into my .NET Core 3.1 application that runs hourly. My service runs each hour (i.e. hits a breakpoint in StartAsync()), but the implementation throws the following error immediately:

A task was canceled

I've searched quite a bit, however I'm having difficulty finding helpful responses; it seems these are most commonly thrown when using HttpClient, which is not relevant to my case.

That said, I have a hunch that I should be awaiting something, but my attempts to add await resulted in the application hanging on startup (I imagine I was unintentionally awaiting the full hourly iteration...?). The tutorial I've been following does not use await anywhere; barring an oversight (very possible), my code seems identical to the example shown.

I've pulled out the guts of ExecuteAll() to confirm the code within works.

Thanks.

I am migrating a medium-sized Win10 app (.NET Framework 4.8) to net5-windows. The solution contains about 30 projects.

While the migration process worked rather straightforward in Visual Studio 2019 (Version 16.8.3) the only problem remained to package everything in a self-contained exe. Instead of struggling with the project entries in VS, I am using the command-line method discussed by Scott Hanselmann in his blog. This also worked smooth and produced an exe of about 140MB size.

One issue remains: Not all of the system dll's are included in the exe. The following ones have to be copied manually to the directory of choice:

Without these DLLs the app does not work.

My question: What is the reason for this behavior, and how can these dll's be included in the self-contained exe?

I've seen this problem on SO, but I cannot seem to work out why it exists.

I am following the tutorial from here

I am using useState but when I try to update the state, the array is empty. I am using state to create initially an empty array. on message received, I am trying to add the message to the array, using the spread operator, which I have used countless times to add an object to an array (but never inside useEffect).

If I uncomment the commented lines, "chat" gets updated as it should do, but I cannot understand why the spread operator is not working and I need to use a useRef to make this work. I don't want to have loads of useRef for every corresponding useState (at least not knowing why it is necessary)

Can anyone see what I am doing wrong, or explain why I need the useRef?

I have a .NET core application that uses the library of PortSip. So far everything worked fine both locally in my Windows 10 laptop and in an EC2 AWS instance with Windows Server 2019 installed, and now I would like to make this work in a Docker container.

So I used a Dockerfile similar to what's mentioned it this link https://schwabencode.com/blog/2018/08/30/ASP-NET-Core-with-NET-Framework-on-Docker to have a Windows Server Core image with both .NET framework (what PortSip needs) and .NET core (what my app needs) as well as added commands to install C++ Redistributable.

The result is that I'm getting the following error when trying to run my app:

At the time of this post there are two Azure Service bus SDKs sitting within sdk/servicebus:

• Microsoft.Azure.ServiceBus
• Azure.Messaging.ServiceBus

They have both been updated very recently (past week).

This ms doc (written two weeks ago) states;

This quickstart uses the new Azure.Messaging.ServiceBus package. For a quickstart that uses the old Microsoft.Azure.ServiceBus package, see ....

Where as this document (also written two weeks ago) says;

There are two supported Azure Service Bus .NET SDKs. Their APIs are similar, and it can be confusing which one to choose. Refer to the following table to help guide your decision. We suggest using the Microsoft.Azure.ServiceBus SDK as It's more modern, performant, and is cross-platform compatible. Additionally, it supports AMQP over WebSockets and is part of the Azure .NET SDK collection of open-source projects.

This document goes on to mention Microsoft.Azure.ServiceBus as newer and (yet another SDK) WindowsAzure.ServiceBus as older. It does not mention Azure.Messaging.ServiceBus at all.

Does anyone have any advice on which SDK should be used for a new .NET Core 5.0 project?

(I have already reviewed this question which has not helped)

I use Azure Functions with Queue triggers in my backend and up to this point, I'd been using the Microsoft.WindowsAzure.Storage package to handle all Azure Storage operations i.e. queues, blobs, etc. With this package, I'd simply send a MyQueueRequest object to my queue and everything worked fine.

Because the Microsoft.WindowsAzure.Storage package has been deprecated, I swithched to Azure.Storage.Queue and my Azure Function started throwing the following error:

Microsoft.Azure.WebJobs.Host: Exception binding parameter 'message'. System.Private.CoreLib: The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters.

I've found this article that suggests that the new library requires JSON objects to be encoded in Base64 (https://briancaos.wordpress.com/2020/10/16/sending-json-with-net-core-queueclient-sendmessageasync/).

Up to this point, I actually never even serialized my MyQueueRequest object to JSON. The model binder took care of that for me automatically.

Does this mean, going forward, before sending the message to my queue, I need to first serialize MyQueueRequest object and then Base64 encode it and then reverse the process in my Azure Functions?

Using Nuget Package Manager in Visual Studio 2019 I attempted to install Microsoft.Toolkit.Uwp.UI.Controls and was met with this message/error:

"Could not install package 'Microsoft.Toolkit.Uwp.UI.Controls 6.1.1'. You are trying to install this package into a project that targets '.NETFramework,Version=v4.8', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author."

Unfortunately, I probably can't change the .NETFramework version (it's a shared project). However, it occurred to me that an earlier version of Microsoft.Toolkit.Uwp.UI.Controls might work just fine. But how does one determine which version of .NETFramework a particular version of Microsoft.Toolkit.Uwp.UI.Controls requires? I suppose I could just start trying them and see what happens but that seems like a lot of work. Even if I do that, it's not clear how you figure out what version of .NETFramework it uses. This answer How to find out which .NET framework nuget package targets? , suggested looking in packages.config but all I see in that is: