Activities of "improwise"

So, looking at the source code for the open source version, it seems like the commercial template is lagging behind here. Looking at the latest app.module.ts there, it is actually updated with what does not seem to work in the commercial template.

In

https://github.com/abpframework/abp/blob/b86c3bee3a7926255c41f7ecc5266f58acdd19e5/templates/app/angular/src/app/app.module.ts

you have for example:

import { provideFeatureManagementConfig } from '@abp/ng.feature-management'; import { provideAbpOAuth } from '@abp/ng.oauth';

But int the ABP Commercial one you still have

import { FeatureManagementModule } from '@abp/ng.feature-management'; import { AbpOAuthModule } from '@abp/ng.oauth';

So the warnings here seems appropriate

Here is the checkin that seems to have updated this in the open source version 4 months ago

https://github.com/abpframework/abp/commit/3c3fb608fd81526c1bc23d391812c3d0787b320a#diff-b8168b298611b9de219c25b8486f54cedf89de46ebdf51c61aa285b97c05c3d5R14

Edit:

Seems to be the entire ABP Commercial Angular version that is lagging behind, including new UI etc.

Moved the LeptonX stuff to https://abp.io/support/questions/7947/ABPLeptonX-theme-breaks-as-specific-widths

Created a new ticket for problems related to LeptonX theme instead to keep this one focused on Angular problems, as they LeptonX bugs seem to be universal.

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.

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 ABP Studio, while showing great promise, also seems to have numerous bugs still, so we really need ABP Suite to keep all its functionality for now.

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?