Activities of "alper"

https://community.abp.io/articles/how-to-customize-the-login-page-of-an-abp-blazor-application-by4o9yms

1- I want to have a navigation property that is mandatory but I don't see any option on abp suite to specify it.

This is not supported for now but it's on the roadmap (probably in v4.2). for now you can do it manually.

In the same subject if I add manually a navigation object property (Shopfloor) in addition of my navigation id property (ShopfloorId) on my entity when I make an update on abp suite this navigation object is deleted.

Suite overwrite all its own created files. So when you edit a Suite generated file, it will be overwritten if you generate the same entity.

actually the problem is related to using module source-code inside the main application and creating CRUD pages with your hybrid structure. A module consists of several database providers and UI frameworks. Therefore Suite is trying to generate code for each of them. What's the official way of doing this; create your CRUD pages inside your module solution. If you reference entities between your modules, you are breaking all best practises because after that you strictly depend on your module.

as I learnt from the Angular team, this is in the milestone and you can achieve this with v4.2-preview. Current version 4.1-preview.

can you try with the 4.1.0-rc.2

dotnet tool install --global Volo.Abp.Cli --version 4.1.0-rc.2 && abp suite update

@gterdem he's project is not seperated IDS

willignicolas@gmail.com:

Thanks @alper, we will do that. And for the parsing error when there is comment on enum value ?

that's not supported. but you can temporarily remove comments before the code generation. then add it again after it completes.

@jackmcelhinney I adviced you 2 things; one of them is using Async method and one is adding await to ExampleGetAsync

hi @trendline,

This happens when you debug your project from different computers (including Virtual Machines)... So if you don't need to debug your application, then just use the release mode and set your environment to production. I'll send your message to the license team they will help you.

@bqabani we'll check that. there's 4.1.0-rc.2 , meantime you can test it in the latest RC.

@willignicolas@gmail.com, assign values to your enum. this is best practise and Suite supports this.

enum eTest {
  None = 1,
  Standard = 2,
  Anonymous = 3,
}

@jackmcelhinney can you try this; I guess there's async-await issue.

[UnitOfWork(IsDisabled = true)]
[HttpGet]
[Route("test/{id}")]
public virtual Task<WorkItemDto> ExampleGetAsync(Guid id)
{
    return await _workItemAppService.ExampleGetAsync(id);
}

[UnitOfWork(IsDisabled = true)]
[AllowAnonymous]
public virtual async Task<WorkItemDto> ExampleGetAsync(Guid id)
{
    var test = await _workItemRepository.Where(w => w.Id == id).FirstOrDefaultAsync(); //<<-- Error thrown here

    return ObjectMapper.Map<WorkItem, WorkItemDto>(test);
}