Activities of "ptaylor"

Dear Team,

Type - ASP.NET Core & Angular(Separate) Version - 13.3.0

We have been deploying the product in IIS and Azure App Services from a long time wherein Angular and API are deployed in two websites/azure app services and database is in a separate SQL server or Azure SQL Database. The team is planning to move to containerization deployment. We followed your document https://docs.aspnetzero.com/aspnet-core-angular/latest/Deployment-Angular-Docker to try out the deployment and were able to deploy the app in three containers, one for angular/web server, one for API/backend and one for SQL Server Database. There are few queries related to this before moving forward with staging and production.

1. Can we have a single container with all three components(web server, API and Database)? If yes, what are pros and cons compared to three separate containers?
2. We expected a better performance in containerization deployment but after testing we found its not better than IIS deployment. Both machines are of same configuration and in the same location with only difference being Operating System. Is this something due to the product architecture or in the way how containerization is deployed?
3. What are other problems we would face in production if we have containerization deployment using Kubernetes? As per documentation moving to distributed cache Redis and using Hangfire for background jobs is mentioned. Are there any other changes we need to do in the application code?

Regards

I see some of the examples from the boilerplate code that class that inherits from [ProjectName]ServiceBase (mostly helpers) and [ProjectName]DomainServiceBase (Managers) resides in the [ProjectName].Core Project and can be injected in the classes that inherits from AppServiceBase (AppServices) and is placed under [ProjectName].Application Project.

So, what's the difference between the classes that inherits from [ProjectName]ServiceBase and the classes that inherits from [ProjectName]DomainServiceBase. In what condition should we prefer ServiceBase over DomainServiceBase and vice versa.

For example: UserPolicy that inherits from [ProjectName]ServiceBase.
I could not get the difference between Application Layer and Domain layer citing this class.

My question is why couldn't it inherit from [ProjectName]DomainServiceBase? What changes/complications it would have caused if inherited from [ProjectName]DomainServiceBase?

Version - 10.5.0 Product type - .Net Core + Angular

Hi Team, I have enabled Stripe to purchase/subcribe to a paid Edition while creating a new tenant. When a stripe payment gets Failed(due to any reason) or Cancelled(by clicking on back button on stripe payment page), how this payment/transaction can be restarted or another transaction can be kick-started so the user can purchase the edition and tenant can be activated? I am unable to find in both documentation as well as source code where this can be done. Please guide.

Regards.

Product type: ASP.NET Core + Angular Version: 7.0.0

I have a requirement to add a new property to History related table, AbpEntityChange to be precise. I am able to do this by following Extending Existing Entities. I just couldn't find the file where I can modify the newly added property i.e. I want to modify or add value to this property when a new entity of AbpEntityChange is created.

Please let me know the area where these changes are currently being made in my application.

Thanks