Activities of "alper"

@alexander.nikonov I created a new question for this seperate issue. https://support.abp.io/QA/Questions/876/Suite-module-page-is-not-loading

can you open the developer console and check if there's a log. 1- open Chrome Developer Console and refresh page 2- see if there's an error or awaiting XHR request 3- check the CMD window (which you have started the Suite). is there any error there?

reported here https://support.abp.io/QA/Questions/287#answer-0eb2a565-8f43-115b-3e34-39fa7f9c1875

@alexander,

the --version parameter came to ABP CLI after v4.0. so when you are using an older version than 4.0 you cannot use --version parameter. use the below command:

dotnet tool uninstall --global Volo.Abp.Suite
dotnet tool install -g Volo.Abp.Suite --version 3.3.2 --add-source https://nuget.abp.io/<your-api-key>/v3/index.json

@vasile thanks for your feedback. generating CRUD pages from an existing database table is on the roadmap. but there's no exact date to implement this.

and can you explain in details what kind of master-detail table? (this is a broad topic)

@scott7106

Hi @alper,

After upgrading my CLI and Suite to 4.2 and everything worked correctly. For future reference, does Suite always generate based on the latest stable version regardless of which version I have installed? I do not see an option to tell Suite to use --preview or a specific version.

Suite has a --preview option but not for generating code. you can install the preview version of the Suite like below

abp suite install --preview

If you are using a preview ABP version, then you can install the Suite preview version.

@gexiaoxu are you working on a module? if so we have fixed this in the latest relese. check that you don't have a preview version.

@armagan how to work with CSS variables here?

Hello @alper,

I was hoping this bug to be fixed in 4.2 (first saw it in 4.1.2) but it seems to want to stay. My problem is, when I build a Blazor + separate Identity Server project, the basic DateTimePicker is not behaving how it should. Tried both Sql and Mongo and results are as follows:

SQL: -starts from 01/01/01 and allows you to manually modify only date or month. If you attemp to modify both date and month it turns back to 01/01/0001.The year is untouchable , as it appears you can only modify the last 2 digits of it. -The today button however, works ok, but it is unpleasent to scorll down to the required year starting from 2021 -Saves date exactly

Mongo: -same problem with DateTimePicker and manual modifications -saves not the chosen date, but the day before that (eg: I pick 05.02.2021 and it saves 04.02.2021)

Must mention the project and CRUD pages were generated by the abp suite and there were no modifications whatsoever to the page rendering the grid, nor were there any modifications to the AppService Create method.

Thank you in advance for your response and keep up the good work!

@ilitzy yeah it's a bad experience and I also didn't like that. I created an issue for Blazorise date component issue.

ABP Framework version: v4.2.0 UI type: Blazor DB provider: EF Core Tiered (MVC) or Identity Server Seperated (Angular): no Exception message and stack trace: Steps to reproduce the issue: Step 1: Create a module using ABP suite. Step 2: Add an entity to the module using ABP suite.

Problem: ABP suite does not update Blazor UI when adding a new entity. It only updates Angular and MVC.

@anthonyh , ABP Suite doesn't support BlazorUI module code generation right now. As BlazorUI is a new feature, code generation for Blazor modules will be implemented on the next version. On the other hand, code generation for Blazor application is available.