Activities of "MichelZ"

We have tried this with the application before-upgrade now (v6.0.2) and it worked (I stated previously that it didn't, but I executed it in the wrong directory)

So it seems there is some issue with the upgrade from 6.0.2 to 7.4.2? Any pointers?

We have tried with version 7.4.2 now, with the same result.

Hi,

Above stack overflow discussion is about 2 scenarios

1. If there is no model/service then also you are trying to generate proxy
2. If you are targeting to live API address instead of local one

1. We do have services of course
2. We are not targeting live API, abp generate-proxy -t ng -u http://localhost:5101 <--- Localhost!

> If these are not the case then please check

1. Check your ABP Framework and CLI version are same or not?

CLI is .1 newer (7.4.3 vs 7.4.2)

2. or once run npm install to install all the necessary dependencies and then try

The frontend builds fine with ng build / ng serve. Packages are all installed

yarn install v1.22.19 [1/4] Resolving packages... success Already up-to-date. Done in 0.42s.

Hello,

Have you checked this https://stackoverflow.com/questions/70278156/abp-io-angular-cannot-read-property-replace-of-undefined

Have you followed these migration guides https://docs.abp.io/en/abp/latest/Migration-Guides/Index

Please check once and let me know if found helpful.

Thanks

We have followed the migration guides. The application does work when deployed, but we have the need to generate the proxies now for added functionality, which does fail.

I'm not sure what that stackoverflow thread is trying to tell me.

• ABP Framework version: v7.4.2
• UI Type: Angular /
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): yes
• Exception message and full stack trace:
• Steps to reproduce the issue:

After updating from v6.x we are now trying to generate the Angular proxies, but we are getting: Cannot read properties of null (reading 'replace') when executing: abp generate-proxy -t ng -u http://localhost:5101

We can reach the api-definition document on: http://localhost:5101/api/abp/api-definition

Any pointers how to troubleshoot this? Does the abp cli generate logs or something we can use?

I want on shutdown of the Application that hosts the Background Workers to issue a cancellation token that can somehow be used/injected as ICancellationTokenProvider,

Currently not possible.

OK, thank you

Hi, I don't think this is what I need, altough might be helpful.

Maybe I need to describe it differently what I want. I want on shutdown of the Application that hosts the Background Workers to issue a cancellation token that can somehow be used/injected as ICancellationTokenProvider, as we (currently) exclusively use the ICancellationTokenProvider to cancel work in the Repositories.

How would AddBackgroundWorkerAsync with a CancellationToken parameter work here?

Thanks

Thanks, but this is not what I'm asking (I think)

Background WORKERS already support CancellationTokens:

public abstract class HangfireBackgroundWorkerBase : BackgroundWorkerBase, IHangfireBackgroundWorker`
{
    public string RecurringJobId { get; set; }
    public string CronExpression { get; set; }
    public TimeZoneInfo TimeZone { get; set; }
    public string Queue { get; set; }
    public abstract Task DoWorkAsync(CancellationToken cancellationToken = default);
    protected HangfireBackgroundWorkerBase()
   {
        TimeZone = null;
        Queue = "default";
    }
}

But here, I have to pass the CancellationToken down to my repository methods (which I don't have to do in the normal Http project, as it uses the HttpContextCancellationTokenProvider)

My question is if I can somehow make BackgroundWorkers work the same, without adding CancellationToken overloads to the Repository methods, as my Repository methods use GetCancellationToken() to pass the token from the ICancellationTokenProvider

Thanks

• ABP Framework version: v6.0.0
• UI type: Angular
• DB provider: EF Core
• Tiered (MVC) or Identity Server Separated (Angular): yes

We are using ICancellationTokenProvider for our repositories with the GetCancellationToken() method, so we don't have to sprinkle the CancellationTokens into every method. This works well with the HttpContext Token Provider.

We would like to do the same thing with Background Workers (we are using HangfireBackgroundWorkerBase) - but we are not sure how to... any pointers? Or do we need to convert our Repositories to take CancellationTokens as parameters for this to work properly?

Thanks

OK, I don't think OpenIDDict has anything to do with the actual login... I was mislead by the migration removing the reference to Microsoft.AspNetCore.Authentication.OpenIdConnect (as it was referenced by Identity Server), so I thought it was functionality provided by Identity Server when the .AddOpenIdConnect() call was not available anymore.