Activities of "improwise"

Even after you have done the necessary corrections to get the Angular app to even run, there seem to be numerous problems with lag, poor performance etc. This seem to happen in all Chromium based browser but not in Firefox. Notice how the left bar hides the content of the application, and also the very poor performance numbers. Also, when you click the "change container width" in a Chromium browser, nothing seems to happen, but when you do it in Firefox, you can see the changes directly. Also notice the large number of warnings reported.

Unless we are doing something really wrong here, it seems like the Angular template in ABP is a no go at the moment for various reasons. There could of course be other causes of this than ABP, but non of our other Angular applications display any problems like this running on the same dev machines, same browsers etc.

Edit:

Correction, it seems like the problems here are not caused by browser engine but rather browser width. It seems like for certain width, the LeptopX theme, at least for Angular, simply breaks which cause both visual distortion as well as at least some of the performance problems. This can be verified by simply adjusting the width of the browser windows (tested on Windows 11, Firefox, Chrome and Edge, all show the same behavior).

Edit 2:

It seems to be the LeptonX theme that is broken in general for certain screen width so those specific problems are probably not related to Angular, even though the other ones are. This is how it looks with Blazor

The packages really seem to be marked with deprecated, even though they were just recently updated

• @deprecated FeatureManagementModule is deprecated .
• @description use provideFeatureManagementConfig function for config settings.
• You can import directives and pipes directly whichs were belongs to FeatureManagementModule are switched to standalone.

https://www.npmjs.com/package/@abp/ng.feature-management/v/8.3.0

Having looked further into this, it seems like packages.json is missing several dependencies including but not limited to @abp/ng.feature-management.

• ABP Framework version: v8.3
• UI Type: Angular
• Database System: EF Core (SQL Server, Oracle, MySQL, PostgreSQL, etc..) / MongoDB
• Tiered (for MVC) or Auth Server Separated (for Angular): no

It used to be that we could only fire up ABP Suite and tell it to create an Angular application it that would be it. Now that option seems to be gone in ABP Suite and ABP Studio only seems to create an Angular application that won't even build due to several missing packages and also quite a lot of deprecated ones. Weirdly enough, creating single layer Angular application does not seem to have this problem, or at least that one you can build even though it also contains numerous packages marked as deprecated. This even if you deselect all additional modules like GDPR, chat etc.

Only using default settings in latest ABP Suite except that we selected Angular as UI and layered application and this is what we got

How are we supposed to create a new working layered Angular application in ABP Commercial 8.3?

Edit: Please note that we don't know exactly why some packages are marked as deprecated and if that is actually true, but still it won't even build when using the layered Angular template due to missing packages.

Hello,

I recently updated to ABP Suite 8.3, and I noticed that the "Create a new solution" button is missing from the interface. This feature was available in previous versions, and I used it frequently to quickly create new solutions.

Could you please confirm if this feature has been moved, removed, or if it is a bug in this version? I would appreciate any guidance on how to create new solutions within the latest version of ABP Suite.

Thank you for your assistance!

Best regards,

I guess you are supposed to use ABP Studio these days but so far that has only been one problem after another for us with both Blazor and Angular.

When creating Blazor Server - single layer solutions via ABP Studio the SLN gets littered with these files. What are those and if needed, why do we need to be on root level?

I am also look for information here regarding the status in general of the React Native / Expo mobile client. Seems like currently the React Native app offered by ABP is using Expo SDK 47 which is by now almost 2 years old. It is also using JS instead of Typescript. Sadly, MAUI does not seem to be close to an viable alternative yet. if ever.

And how come this issue is 15 days old and yet still has noone from ABP assigned to it?

I believe we need an 8.3 thread now that it has been released.

Please update the contents of the page RoadMap
https://docs.abp.io/en/commercial/latest/road-map#backlog-items

This page should also be updated
https://docs.abp.io/en/commercial/latest/aspnet-zero-vs-abp-commercial

So, we can understand what the next releases will be.

Example, when will this feature be implemented?

Thanks

2 months later, the Road map page is still severely outdated, claiming that 8.2 will be released in June

https://abp.io/docs/latest/release-info/road-map

the road map is already updated

It wasn't when I posted my comment but seems to be now, thanks.

Latest version now gives this error (assuming it is trying to use mkcert without installing it)

Some pre-requirements are missing. If you want the application to work as expected, you need to install the following tool(s):

- mkcert. (Installation link: https://github.com/FiloSottile/mkcert)    

If you have already installed the tool(s), please check the PATH environment variable.

As seen in the error message, we're using the mkcert command during the solution creation process. So you should download mkcert by following the installation guide.

Is this a new feature as it has not been needed before from what I can remember?

No, it's not. If you create a microservice or app project with Kubernetes Configuration checked in the Additional Options step, then it uses the mkcert command to create the certificate.

That might be true but I get this error message now as soon as I start the ABP Studio which I have not gotten before. If it is only required for Kubernetes it perhaps should not be required?