Activities of "improwise"

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?

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?

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

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.

Restore the button "Create a new solution" , thanks

It is still available in my ABP Suite, just tried it with 8.2.1. Not sure if things might have changed in the last couple of days though.

Hi,

Ah, so it is only a "typo" where it should have been "key" but instead was "AccessTokenKey"? Seems reasonable when looking at the code more in detail now, was a bit stressed last time around just trying to get it to work and the name AccessTokenKey made it look like something more than just the usual keypair.

Is storage actually used anywhere in the MAUI app currently?

Please also note the part about Exported = true being needed (or implemented / solved elsewhere)

BTW, at least for me, the small emoji icon seems broken now but worked fine before, so you will have to imagine a thumbs up here :)