Activities of "smansuri"

• ABP Framework version: v8.2.1
• UI Type: Angular / MVC
• Database System: EF Core (MySQL)
• Tiered (for MVC) or Auth Server Separated (for Angular): Auth Server Separated
• Exception message and full stack trace:
• Steps to reproduce the issue: migrate to .net framework 9

What are database changes introduced in each release? How do we track it if we want to have database first approach for my application?

Any update on this?

The issue is in the test process.

Any tentative date of release?

The new modules will continue being DDD layered.

Then why not provide a param in the add microservice command to use DDD layer solution or the new one which will be default while adding microservice?

Hi @smansuri

Sorry for our late reply. I think what @yekalkan means, you need to do this in new microservice template. If you follow this approach https://abp.io/support/questions/8755/ABP-studio-not-able-to-add-Wi new-micro-service-in-the-existing-solution#answer-3a180b89-76d4-b0ff-a534-dd45c2339225, you should be able to work on new microservice solution template.

Are you having this issue on new microservice template as well ?

with new micro service template i have seen the DDD layer is removed now. We already have a application developed using DDD domain and now you have remove the option to generate DDD layered from new template. So if we do not migrate to latest microservice template and if you introduce the new module like payments in future it will follow the new micro service template right? and what if we need to customize the features in the newly introduce module? how do we achieve this if we do not migrate to new template and only upgrade the abp version to latest version. And how am i supposed to maintain the source code of these modules in case in case if stop using the abp license?

Do we have any update on fixing the expo web issue?

Any update on this?

Hi @smansuri

It is a prioritized issue. We aim it to be resolved in the next release.

i was asking about web version not building at first.

Any update on this?

Hi @smansuri

It is a prioritized issue. We aim it to be resolved in the next release.

i was asking about web version not building at first.

suite does not allow to load the whole microservice solution template as existing solution

You can add service by service. And then generate code on the services.

issue is it does not allow new service to be added.

Any update on this? web version also not working.

Hi, we updated the react-native template versions and changed to TypeScript (all .js files to .tsx) for the react-native applications except for the microservice template. I will create an internal issue for this.

Regards.

With layered application template the web version throws error and unable to run.

If you are talking about React-Native application, yes there is a known issue due to expo migration. We are currently working on that and will try to fix and release a patch version asap. Thanks for your understanding.

Regards.

Can you guide me where can i follow the progress of this work so that i do not have to keep asking you on this ticket?