Hi @NicoZhu-MSFT,
Thanks for replying.
Regarding my scenario, with the progress event i cannot determine which operation is running. Only it's percentage.
I'll study a way by using localsettings.

Thanks.

Hi @Viorel-1 ,
Thanks for commenting.
Like using a static class?
I've done it, and the result is the same.

Like i said, subscribing from the main app to a class in the background task works nicely when using BackgroundTaskCompletedEventHandler. I get events fired to the main app. I don't understand why does not work with a custom EventHandler declared in the BackgroundTask. Even though, it is the requirement stated by the documentation.

Hi @vb2ae,
Thanks for commenting.
Actually i looked to that kind of solution, but it does not fit the purpose because i need to return BadRequest in case of "work2Invalid" gets true.
That is the problem.

By using threads, do you know if there's a way to pass context of the caller?

Thanks.

Just posted an update on GitHub, since it is related to this question. 1471

No one is assigned to that issue @ChristosGeorgiou-4000
And that is the problem.

Let's give @Deva-MSFT some time to reply to this thread.

Any news @Deva-MSFT?

Thank you @JanardhanaVedham-MSFT
This must be recent. I didn't test before posting recently so i thought it was in the same state as before, because i was testing daily.
Thanks.

Already did that but using Import-PfxCertificate cmdlet.
It imported without needing a password. Also i did not mention the password parameter.

Hi,
This question it's not related to set a certificate binding on a IIS website.
It's related to how the application loads the certificate to authenticate using Azure.Identity on Azure AD. It uses DI, as i stated earlier and that's the point of this question.

I'm trying to figuring out the need of using PEM certificate file instead of PFX.
Here it only mentions PEM, but here mentions PFX.

Hello, thanks for asking.
No, there aren't any.
Is the delegate a nested type?
I don't think so, but if i remove that codeblock, it compiles.

 namespace App1
 {
      public static class Class1
      {
            
                  public delegate EventHandler<BackgroundTaskProgressEventArgs> BackgroundTaskInProgress();
                  public delegate EventHandler<BackgroundTaskCompletedEventArgs> BackgroundTaskCompleted();
                  public static event BackgroundTaskInProgress InProgress;
                  public static event BackgroundTaskCompleted OnCompleted;
     }
 }

Hi @AryaDing-MSFT , i'm ironing things out to make it work the way i want. But it's this way. Declaring sealed. Posting more later.

Hi @AryaDing-MSFT , it works. Thanks for the tip.

So, do we have a way to change the order? Thanks for posting here.

Hi @RoyLi-MSFT , thanks for answering.
I have to clarify.
The trial period has ended, since it was 1 month only. It is suppose to end on April 22th. Since i subscribed on March 22th.
A note i would like to add is related to the cancelation. It was made by a WebAPI made by myself which calls the Microsoft Store Services API using the implementation mentioned on this link: https://docs.microsoft.com/en-us/windows/uwp/monetize/change-the-billing-state-of-a-subscription-for-a-user
The article you mentioned, i already know it, and i implemented the same way as described.
As you can see, the problem might be right here on the expiration date, since it mentions year 9999.
I guess this date is when the individual does not have canceled anything yet.
In this case, this is not true, since i canceled it on the same day i subscribed.

@RoyLi-MSFT i've updated the main post, with relevant information. However, i guess i have to contact someone from the Microsoft Account team, am i right? It seems i have a problem with my MSA, since i subscribed the InApp Product i created, but your services are returning a wrong expiration date.