@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);
}
@tony after v4.0 we started to use code flow. that's why the login screen moved to MVC project. you can customize the MVC login screen.see https://gist.github.com/ebicoglu/ce0f0425bab806d0ee1a87d0073af96b
besides I suggest you to check out the following doc. You can copy the Lepton Theme and create your own theme. If you choose this option, let me know to discuss this https://community.abp.io/articles/creating-a-new-ui-theme-by-copying-the-basic-theme-for-blazor-ui-qaf5ho1b
what is your version?
@bbertechini your question credit has been refunded.
for the question 2 check out => https://support.abp.io/QA/Questions/306/Custom-Login-Page-For-Angular
When you see this error update your EF Core CLI with the below command
dotnet tool update --global dotnet-ef