When will the new version of abp studio be released that supports the new abp release?
The new version(0.9.2) of ABP Studio has been released, FYI 🥳🥳
Thank you for the information, it will be very useful. I am forwarding the information you have given to the relevant team-mate.
The problem with not being able to access external dependencies and Suite not opening the first time should be fixed with new version(0.9.1). I would appreciate it if you could confirm these and close this issue.
Finally, however, we could not reproduce the angular code generation problem, but since this question is getting complicated, you can create a new question about this problem you are experiencing. Credit for your question will be refunded if deemed necessary.
Regards, Berkan
How am I supposed to send screen shots of something I have never seen? :)
Sorry about that, I thought you saw something :)
I can imagine that this problem is very frustrating for you, but to be honest, we cannot reproduce it at the moment. Intuitively, we don't seem to have enough information to solve it. All I can do at the moment is to go through the code and try to find the problem, but if you can give us more information in the process, we would appreciate it. It seems difficult to find the problem at the moment, but it is worth a try. Thank you for your understanding.
Regards, Berkan
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?
Hello, unfortunately, we couldn't reproduce the problem, but could you open the file in a text editor and send us its content so we can understand the problem? This way we can understand which file it is trying to open and proceed accordingly.
Thank you for your detailed response and for sharing your thoughts on the mono-repo vs. multi-repo approach and the new folder structure. I understand that these changes can feel a bit different, especially when transitioning from what we're used to, like the previous folder structure.
We’ve had a thorough discussion, and I believe we’ve covered the key aspects. Ultimately, it comes down to personal preferences and workflows, and I understand that the new folder structure may not fit everyone’s needs perfectly. That said, we’ll certainly take your feedback into consideration.
Thanks again for the constructive conversation!
Regards, Berkan
Closing the issue. Feel free to re-open or create a new issue if you have further questions.
FYI, the new version has been released 🥳🥳
You mentioned that there are several disadvantages compared to the previous approach, but I would appreciate some clarification on this.
For instance, in the scenario where we didn’t use a mono-repo setup, you would move the Angular folder to a new repository. Has this process changed with the new template? Or do you find it more challenging to set up CI/CD pipelines with the new folder structure? What specific aspects are causing more difficulties compared to the old approach?
Please know that we thoroughly considered these factors during the design phase, as the new structure is a significant change for us. If there are substantial disadvantages, we are open to reconsidering the folder structure. However, most of the issues raised so far were already present in the previous setup.
While customizing the folder structure might seem like it breaks the 'intended workflow,' it doesn’t pose any issues for future updates or maintaining the template, as we're only changing the folder structure without affecting core functionalities.
In summary, both approaches have their pros and cons, but we opted for the current design based on the reasons I mentioned earlier.
Lastly, the ABP framework is inherently more aligned with a mono-repo setup. For example, the microservice solution leans towards this approach by default. However, if preferred, it's straightforward to work with multiple repositories. You can find more information here: https://abp.io/docs/latest/solution-templates/microservice/mono-repo-vs-multiple-repository-approaches.
It seems like the when using the "old" CLI, it still creates solutions using the aspnet-core folder with react-native etc folders being at the same level as the aspnet-core folder. Does this mean that ABP Suite now supports both folder structures, and if so, is there a way we can choose ourselves which one we prefer?
Yes, the Suite supports both folder structures. Only when the template itself is first created, it is created in a different folder structure than before. So, we expect you to have no problems with the Suite. If you are, you can create a new question with the details of the problem you are experiencing.
Unfortunately, the feature of choosing the structure of the template as you mentioned is not part of our plans. However, we have developed ABP Studio's infrastructure to support custom templates. This means that developers will be able to create their own templates. But we need to work more on this feature, so there is no deadline for this and it is not prioritized. However, you can manually perform the related changes in the template you created for now and there should be no obstacle to this.
