Activities of "improwise"

I updated my Studio and Suite to the latest

And I couldn't see any errors like versions conflict etc...

can you pls check it with the latest version @improwise

Hi and thanks for responding,

It seems both ABP Studio and the new CLI has been updated now which was not the case when we tested this a few days ago (after you emailed about the new release of 8.3.1). ABP Studio now seem to have installed "ABP CLI 0.8.4 (Beta)" instead, not sure if that is supposed to be the same as the 8.3.1 even though it says beta?

I find it quite confusing with these 2 separate CLIs which are apparently both being maintained. Depending on where you look, ABP either recommends using ABP Studio and the new CLI, in other places, like GitHub, the old CLI is instead recommended and the new CLI isn't even mentioned. In this case, the old CLI was obviously updated before the new one.

What is the recommended approach to create production ready ABP solutions as an ABP Commercial customer?

Thanks.

Thanks for letting us know more about the process and thinking for these changes.

I've not used MVC in many years so never considered that, but I guess that could be solved with just a "dotnet" folder.

I am still unsure about this change, or rather how it was implemented, as an alternative to just having a root folder with a folder for "dotnet", "angular", "reactnative" etc. and the SLN files, .git folder etc could be there instead. It also feels a bit off to to have angular / reactnative folders right next to a folder for tests and a README file, both which I assume are just for the dotnet stuff (not in front of dev computer right now so can't check). One middle way could perhaps be to allow some kind of customization for this, like options when new solutions are created.

But that it just my opinion, would be interesting to hear from others as well. Also a confirmation that this new folder structure would work with older ABP solutions as well would be welcome (if that is the case).

Thanks

Why start template not published when a new version released?
it is a long time can not get the template 8.3.1 after it released, abp cli and abp studio also upgraded to latest version.

It seems like something weird is going on with the CLIs, see my other posts above. ABP needs to comment on this. Short version seem to be that in order to use latest version of ABP, we need to stop using ABP Studio and the new CLI and return to old CLI and ABP Suite. This assuming you can still actually create new versions in that with the old CLI installed. If not it seems we are back to only using the old CLI to create new solutions with the latest version of ABP :)

Edit:

Just tried to create a new solution with ABP Suite having only the old CLI installed (8.3.1) and you can only add existing solutions, not create new ones. Creating it using the old CLI you can then add it to ABPU Suite it seems, but perhaps not ideal DX.

@improwise Sometimes I respond to the feedback, sometimes not. But I'm reading all the feedback and reporting to the team.

Thanks for responding.

And how would we know if anyone at ABP is planing to do something about stuff being reported and also follow the progress?

I suggest just adding a new tag "ABP Commercial" to the normal flow of issues on GitHub and this forum can actually be a support forum instead of what seems mostly to be about reporting bugs/problems these days. Should be a win-win for everyone.

Thanks.

BTW, when creating the new solution with old CLI as described here, the old folder structure was still used even for 8.3.1

https://abp.io/support/questions/7844/Bugs--Issues-v83x?CurrentPage=2

Thanks for responding. My initial reaction to this was that it was a bad thing for a few reasons

1. I did not expect the change as I have not seen anything communicated about it
2. It mixed up .net with angular and react, basically making the latter part of the former instead of being independent
3. It creates one big repo for everything (don't remember if that was the case before, but I think it wasn't). That in itself should still be possible with the old structure as well.
4. I was (and still am) concerned about if these changes are backwards compatible, and if ABP Suite would be able to support both the old and the new structure, like if we install latest ABP Suite and then tries to open and older solution.

That said, I would imagine that if this isn't a but (which does not seem to be the case), there should be good reasons behind the changes and there might be advantages to it that I have simply missed. This is mainly why I want to know WHY things have changed and what improvements you think it will bring. So, I am not saying this is bad, more that it was unexpected and that I don't see the obvious reasons for it (and still doesn't), that does not have to mean it is a bad thing though :)

Regardless, unless I have just missed it and it does exist, making a change like this without communicating it I feel is not ideal regardless of what it might bring.

Why start template not published when a new version released? it is a long time can not get the template 8.3.1 after it released, abp cli and abp studio also upgraded to latest version.

It seems like something weird is going on with the CLIs, see my other posts above. ABP needs to comment on this. Short version seem to be that in order to use latest version of ABP, we need to stop using ABP Studio and the new CLI and return to old CLI and ABP Suite. This assuming you can still actually create new versions in that with the old CLI installed. If not it seems we are back to only using the old CLI to create new solutions with the latest version of ABP :)

Edit:

Just tried to create a new solution with ABP Suite having only the old CLI installed (8.3.1) and you can only add existing solutions, not create new ones. Creating it using the old CLI you can then add it to ABPU Suite it seems, but perhaps not ideal DX.

The instructions on the Github main page https://github.com/abpframework/abp still also contains instructions for installing the old CLI

`Quick Start Install the ABP CLI:

dotnet tool install -g Volo.Abp.Cli`

I find this quite confusing, especially now when ABP Studio is available for all versions as I understand it and ABP is telling us to use ABP Studio and the new ABP CLI, yet it is the old CLI that seems to be updated?

Edit:

If we upgrade to latest version of ABP Suite, we will actually get a warning in ABP Studio

For whatever reason, we had problems updating to the latest 8.3.1 version. Even after uninstalling and then doing a "dotnet tool install -g Volo.Abp.Studio.Cli" it still installed ABP CLI 0.8.3 (Beta) but still claimed it was the latest version of the CLI.

dotnet tool update -g Volo.Abp.Studio.Cli Tool 'volo.abp.studio.cli' is already installed.

abp cli check-version [13:49:48 INF] You are running the second generation of the ABP CLI. If you're interested in the legacy CLI, see https://abp.io/new-cli 📌 ABP CLI 0.8.3 (Beta) 📌 You are using the latest ABP CLI.

The old CLI can be installed as 8.3.1 though

dotnet tool install -g Volo.Abp.Cli You can invoke the tool using the following command: abp Tool 'volo.abp.cli' (version '8.3.1') was successfully installed.

Should we just wait?

BTW, do we still need to setup ABP as a Nuget Package Source if if so, what should it be? Same for free and commercial?

As it seems a bit uncertain how much attention posts in the "Bugs & Issues v8.3.x" thread gets, and I feel this is an important and kind of urgent question, I post it in a separate ticket. This is especially true if it isn't an intended change as it would most likely mean that solutions created now would not work with future updates of ABP Suite / ABP Studio.

What is the reasoning for the new directory structure of solutions created with ABP Suite / ABP Studio? It used to be that you got a folder for each "application" under the main directory like "MyApplication" = > "aspnet-core", "angular", "react-native" etc but now it seems to be that angular and react-native folders are moved within what used to be the aspnet-core folder. So now you have SLN file and "test" folder for aspnet-core stuff right next to your angular and react-native folders, even though they are stand alone applications (kind of).

Is this even an intended change or some kind of bug? There might be advantages of this as well, like using only one repo for everything etc (which could be both good or bad depending on personal preference).

You can of course change this after creation, but I would imagine that doing that would break code generation etc?

Is there a guide on if we want to tidy this up a bit and still make sure that ABP Suite etc works (and that won't break with updates etc)?

Hi Support Team,

Let me know when the issue will be fixed so that we can plan to deploy our application.

Best Regards

Not ABP Support but have you looked into if this is an ABP or Angular problem? Have never had time to do that myself, but recall that the warnings included links to Angular errors so might be worth checking into if you have not already. Please share any findings into how to solve this if you find them. Thanks.