Activities of "rafael.gonzales"

Can't modify the templates of a module created in ABP Suite.

The project was created with ABP Studio and the module was created in ABP Suite then the module was added in ABP Suite and tried to modify the Templates but this exception happens

The Volo.Abp.Commercial.SuiteTemplates dll is not added when you create a new module

Can't modify the templates of a module created in ABP Suite.

The project was created with ABP Studio and the module was created in ABP Suite then the module was added in ABP Suite and tried to modify the Templates but this exception happens

The option "Add" -> "New Module" in ABP Studio follows the same concept as ABP Suite? There is no option to add it to the existing solution as in ABP Suite

If you create a "module" in ABP Suite, shouldn't be added in the Solution explorer in the ABP Studio? Right now, if you create a module in ABP Suite, it doesn't add it to the explorer

When you start windows and then use the option ABP Suite -> Open, It doesn't start the ABP Suite at all but if you run the command in your terminal "abp suite" and then close it, you will be able to use the ABP Suite -> Open option normally

Can we start using the full version of select2?

It only requires to change to full

context.Files.AddIfNotContains("/libs/select2/js/select2.full.min.js");

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

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.

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.

Found the issue,

the generated Controller from ABP Suite only adds a basic route like the following

[Route("[controller]/[action]")]
public class ClientsController : AbpController
{
    [HttpGet]
    public virtual async Task<PartialViewResult> ChildDataGrid(Guid clientId)
    {
        return PartialView("~/Pages/Shared/Clients/_ChildDataGrids.cshtml", clienteId);
    }
}

It makes the AbpServiceConvention class to ignore this part of the code

If the ConfigureRemoteService method is not initiated, there won't be any URL modification in the route's prefix.