With the latest version of abp studio (0.9.1) I can't create a version of ABP 8.3.2.
It always creates version 8.3.1When will the new version of abp studio be released that supports the new abp release?
Can you find a solution so that when a new version of ABP is released, the version of abp studio that supports it will be released almost at the same time?
Thanks
It's happening since many versions before, ABP Studio never uses the latest version of ABP Framework while creating a project and it's a problem It doesn't get fixed and we don't have an answer from ABP Team of whether they have addressed it or not
We reverted to using old CLI + ABP suite instead, mostly as the code produced is also different. This is far from ideal for many reasons.
Any news on this, ie having Docker support in solutions created by new CLI / ABP Studio just like with old CLI?
Thanks.
Yes, you can open abp studio and click File -> Initialize Existing Solution
Thanks, will give it a try.
Please let us know with regards to Docker support in the new CLI / ABP Studio once you have had that discussion.
Maybe just trying to actually open the suggested file in something like Notepad could provided some clues on what it is?
Have never seen it myself but thinking perhaps its something trying to render a HTML page or similar with no default browser selected but that is just a guess.
Could you send screenshots if possible?
How am I supposed to send screen shots of something I have never seen? :)
@ABP
Until ABP Studio is out of beta and actually ready for production, can you PLEASE bring back the possibility to create new solutions in ABP Suite?
I realize that this might not be ideal in some regards, but while really promising, ABP Studio and the new CLI just isn't there yet to feel like a safe environment to start new projects intended for actual production and also misses features like Docker-support etc. There is also still a lot of documentation that seem to be missing in the new documentation that is only available in the old one and also parts of the new documentation that is incorrect (mixing what is correct for new CLI with what is correct for the old CLI, like folder structure etc). This back and forth between different tools and CLIs as well as constant bug hunting honestly has us considering our options ATM.
Thanks.
Migrate react native to latest expo version with type script compatibility
Totally agree with this. I almost get the feeling that the React Native mobile project has been dropped in ABP in favor of MAUI, which would have been a logical decision if Microsoft ever got MAUI to be a serious alternative. Current state of MAUI is of course not ABPs fault but it leaves us in a situation where there really isn't a viable mobile option in ABP besides creating your own
Not sure if anyone actually read these threads but here is some more information about the actual ongoing work with this so there seem to be things happening
https://abp.io/support/questions/7625/React-EXPO--migration
Hi,
Yes, old and new CLI use different template sources.
Thanks. What about going forward then, would solutions created with old CLI work with ABP Studio?
Hi,
You are right; ABP should have full support for docker; we'll discuss it internally and get back to you
Thanks for responding.
This should for now mean that if you want Docker support, you would have to use the old CLI (or rather the startup templates for that but they seem to be tied together)?
Maybe just trying to actually open the suggested file in something like Notepad could provided some clues on what it is?
Have never seen it myself but thinking perhaps its something trying to render a HTML page or similar with no default browser selected but that is just a guess.
Hi all, it seems like ya are not read my comment well, I'll migrate to 51 but if you guys read the migration guid react expo recommend to update version incrementally. I'll migrate today to 51
https://reactnative.dev/docs/upgrading#expo-projects
Thanks, Masum
Thanks for the clarification.
And it will be TypeScript as well then going forward?
