65 Answer(s)
-
0
It would be nice if there was a solution wide option for multi tenant so that you did not have to manually select it each time you create a new entity. I would assume that if you have some entities that are multi tenant, you would probably want most of them to be that as well. Of course there would need to be an option to still deselect it for each entity when you create it.
-
0
I'd like either an improved version of chat module or guide on customizing it. Default version is nice for demo but we should be able to customize things like:
- Who can users search for, and in which tenant(s). For example, we might want to only allow chat between existing tenant or only to open chat with HOST tenant users
- Groups and roles. For example, customer service group that is a shared inbox for a group of users. Customer roles should be only able to open chat with this roles, not every other client
-
0
Restore the button "Create a new solution" , thanks
-
0
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.
-
0
Restore the "Create a new solution" button, abp suite version 8.3.0-rc.1.
-
0
Restore the "Create a new solution" button,
abp suite version 8.3.0-rc.1.I hope this gets fixed in the next Release Candidate because old personal license holders lost many features and this I guess It goes against many terms and conditions. In the last ABP Community was answered a question I did to Halil Ibrahim Kalkan and He compromised we will get these features (if not in ABP Suite but in ABP Studio). I sent an email asking for confirmation but didn't get one. Sincerely, I hope these changes they are doing to their license configuration don't affect us.
-
0
I hope this gets fixed in the next Release Candidate because old personal license holders lost many features and this I guess It goes against many terms and conditions. In the last ABP Community was answered a question I did to Halil Ibrahim Kalkan and He compromised we will get these features (if not in ABP Suite but in ABP Studio). I sent an email asking for confirmation but didn't get one. Sincerely, I hope these changes they are doing to their license configuration don't affect us.
As I understand it, you now have to do this via the studio. And as I heard in the last Community Talk, "old" license holders still have the same options as before.
In any case, I can still create solutions via Studio. Have you tried it yet?
-
0
Restore the "Create a new solution" button,
abp suite version 8.3.0-rc.1.
I hope this gets fixed in the next Release Candidate because old personal license holders lost many features and this I guess It goes against many terms and conditions. In the last ABP Community was answered a question I did to Halil Ibrahim Kalkan and He compromised we will get these features (if not in ABP Suite but in ABP Studio). I sent an email asking for confirmation but didn't get one. Sincerely, I hope these changes they are doing to their license configuration don't affect us.
Hi @rafael.gonzales, as @ageiter mentioned you can create new solutions via ABP Studio and there is not a single feature that is limited for the old license holders. It's recommended and much easier to use. You can download the ABP Studio and even generate CRUD pages by using ABP Suite that is integrated into the ABP Studio desktop app.
-
0
Restore the "Create a new solution" button,
abp suite version 8.3.0-rc.1.
I hope this gets fixed in the next Release Candidate because old personal license holders lost many features and this I guess It goes against many terms and conditions. In the last ABP Community was answered a question I did to Halil Ibrahim Kalkan and He compromised we will get these features (if not in ABP Suite but in ABP Studio). I sent an email asking for confirmation but didn't get one. Sincerely, I hope these changes they are doing to their license configuration don't affect us.
Hi @rafael.gonzales, as @ageiter mentioned you can create new solutions via ABP Studio and there is not a single feature that is limited for the old license holders. It's recommended and much easier to use. You can download the ABP Studio and even generate CRUD pages by using ABP Suite that is integrated into the ABP Studio desktop app.
In ABP Studio, we have blocked features that we used to have in ABP Suite. If ABP is migrating their old existing and active license holders to ABP Studio at least give us the same possibility we used to have in ABP Suite but we have blocked features.
You said that personal or team license holders, why do they need microservice? why do they need a tiered version?
why do they need those features? I didn't have the chance to answer in the last Community speech but it's because at least in my case (personal license holder), Prototyping. In any project, we all start with a proof of concept with the basics for whatever size of the project we are aiming for and do not always start with a monolith, I went to some big companies that needed a microservice project, presented a prototype of a microservice project, and proposed the idea and the requirements (buy a license of ABP, hosting, etc) and also in my case, I am working in a tiered personal project that will take me another year because I am doing solo and of course, whenever it's the need I will upgrade my license to a higher tier because I will need those extra licenses, I will need that extra support for all people and of course, I will require more private tickets because It will be target specific those questions because the project will be growing but right now I feel like you will be cutting our wings in the feature with those features blocked. The framework is awesome took me time to understand every aspect of it directly from their source code and understand how can make the ABP Suite work well with my workflow and loved to support during that path with many bug reports and I will continue doing as much as I can but feels like a downgrade. -
0
Restore the "Create a new solution" button,
abp suite version 8.3.0-rc.1.
I hope this gets fixed in the next Release Candidate because old personal license holders lost many features and this I guess It goes against many terms and conditions. In the last ABP Community was answered a question I did to Halil Ibrahim Kalkan and He compromised we will get these features (if not in ABP Suite but in ABP Studio). I sent an email asking for confirmation but didn't get one. Sincerely, I hope these changes they are doing to their license configuration don't affect us.
Hi @rafael.gonzales, as @ageiter mentioned you can create new solutions via ABP Studio and there is not a single feature that is limited for the old license holders. It's recommended and much easier to use. You can download the ABP Studio and even generate CRUD pages by using ABP Suite that is integrated into the ABP Studio desktop app.
In ABP Studio, we have blocked features that we used to have in ABP Suite. If ABP is migrating their old existing and active license holders to ABP Studio at least give us the same possibility we used to have in ABP Suite but we have blocked features.
You said that personal or team license holders, why do they need microservice? why do they need a tiered version?
why do they need those features? I didn't have the chance to answer in the last Community speech but it's because at least in my case (personal license holder), Prototyping. In any project, we all start with a proof of concept with the basics for whatever size of the project we are aiming for and do not always start with a monolith, I went to some big companies that needed a microservice project, presented a prototype of a microservice project, and proposed the idea and the requirements (buy a license of ABP, hosting, etc) and also in my case, I am working in a tiered personal project that will take me another year because I am doing solo and of course, whenever it's the need I will upgrade my license to a higher tier because I will need those extra licenses, I will need that extra support for all people and of course, I will require more private tickets because It will be target specific those questions because the project will be growing but right now I feel like you will be cutting our wings in the feature with those features blocked. The framework is awesome took me time to understand every aspect of it directly from their source code and understand how can make the ABP Suite work well with my workflow and loved to support during that path with many bug reports and I will continue doing as much as I can but feels like a downgrade.k8s integration is a new feature and introduced with ABP Studio. Therefore, it's normal to not be able to use it with a personal license. For the other features, there should be not a single limitation. So, please answer the following questions and apply the necessary ones:
- What is your ABP Studio version?
- Can you update the ABP Studio to the latest version?
- When did you buy the personal license? Is it before 23.07.2024 or later?
-
0
Restore the "Create a new solution" button,
abp suite version 8.3.0-rc.1.
I hope this gets fixed in the next Release Candidate because old personal license holders lost many features and this I guess It goes against many terms and conditions. In the last ABP Community was answered a question I did to Halil Ibrahim Kalkan and He compromised we will get these features (if not in ABP Suite but in ABP Studio). I sent an email asking for confirmation but didn't get one. Sincerely, I hope these changes they are doing to their license configuration don't affect us.
Hi @rafael.gonzales, as @ageiter mentioned you can create new solutions via ABP Studio and there is not a single feature that is limited for the old license holders. It's recommended and much easier to use. You can download the ABP Studio and even generate CRUD pages by using ABP Suite that is integrated into the ABP Studio desktop app.
In ABP Studio, we have blocked features that we used to have in ABP Suite. If ABP is migrating their old existing and active license holders to ABP Studio at least give us the same possibility we used to have in ABP Suite but we have blocked features.
You said that personal or team license holders, why do they need microservice? why do they need a tiered version?
why do they need those features? I didn't have the chance to answer in the last Community speech but it's because at least in my case (personal license holder), Prototyping. In any project, we all start with a proof of concept with the basics for whatever size of the project we are aiming for and do not always start with a monolith, I went to some big companies that needed a microservice project, presented a prototype of a microservice project, and proposed the idea and the requirements (buy a license of ABP, hosting, etc) and also in my case, I am working in a tiered personal project that will take me another year because I am doing solo and of course, whenever it's the need I will upgrade my license to a higher tier because I will need those extra licenses, I will need that extra support for all people and of course, I will require more private tickets because It will be target specific those questions because the project will be growing but right now I feel like you will be cutting our wings in the feature with those features blocked. The framework is awesome took me time to understand every aspect of it directly from their source code and understand how can make the ABP Suite work well with my workflow and loved to support during that path with many bug reports and I will continue doing as much as I can but feels like a downgrade.k8s integration is a new feature and introduced with ABP Studio. Therefore, it's normal to not be able to use it with a personal license. For the other features, there should be not a single limitation. So, please answer the following questions and apply the necessary ones:
- What is your ABP Studio version?
- Can you update the ABP Studio to the latest version?
- When did you buy the personal license? Is it before 23.07.2024 or later?
About the k8s integration, as far as I know, we got a year of updates with every renewal. Since ABP Suite is being integrated into ABP Suite and I've acquired a license to get full features of ABP Suite, at least I would expect to get the same treatment in ABP Studio.
I have been a license owner since August 16, 2022 The ABP Studio version is 0.7.5
-
0
Hi everyone.
Are there any future plans to add support for the Volo.Forms module for Blazor? If so, is there a timeframe? It's kind of odd that this premium module is not supported in either Blazor WebAssembly, Blazor Server, or Angular. Was very upset to see that after spending ages debugging why it wasn't working, I stumbled upon a one-liner in your documentation to say it's not supported. I don't really want to have to spin up a separate site to host unsupported modules...
Maybe don't let users add the Forms module if it's not supported, or throw up a warning or something.
-
0
For the template it would be cool if you would provide the KeyPrefix for the cache configurable. I use the same cache for different deployments of the application (testing, production, ...). And then of course I would like to use different KeyPrefixes.
I have added this to my code as follows:
Configuration of service:
private void ConfigureCache(IConfiguration configuration) { Configure<AbpDistributedCacheOptions>(options => { options.KeyPrefix = configuration["Redis:KeyPrefix"] ?? "MyApp:"; }); }appsettings.json (for development):
"Redis": { "IsEnabled": "true", "Configuration": "127.0.0.1", "KeyPrefix": "MyApp:Development:" }, -
0
Hi,
It would be great if we could have a suite-custom-code-block in the OnInitializedAsync method of Blazor files/components because this method can't be overwritten. More than this at this moment from me any code added in the razor extended file (Extended.razor.cs) is deleted anytime I regenerate the entity code from Abp Suite.
Thank you
-
0
Hi,
It would be great if we could have a the possibility to decide if for certain property (simple or navigation) the UI code (UI control) will be generated or not. Or at least to be able to decide if the UI control will face a @ref= attribute and with this we can control the visibility and other things of that control.
Thank you
