Activities of "alper"

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

Windows:

%UserProfile%\.abp\suite\appsettings.json

MAC:

~/.abp/suite/appsettings.json

The solutions and paths are written in this file. If this is corrupted, you can manually fix the json file. Or you can delete it. And add your solutions again.

NuGet.Config must be like this

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <packageSources>
        <add key="nuget.org" value="https://api.nuget.org/v3/index.json" />
        <add key="BlazoriseMyGet" value="https://www.myget.org/F/blazorise/api/v3/index.json" />
        <add key="ABP Commercial NuGet Source" value="https://nuget.abp.io/***-your-api-key-***/v3/index.json" />
    </packageSources>
</configuration>

Guys I realized that the below package is used in the Blazor project

Microsoft.AspNetCore.Components.WebAssembly.DevServer

Before you publish your project, change this package to the below one

Microsoft.AspNetCore.Components.WebAssembly.Server

I guess the second one provides more performance, the first one is for development (hot reload, rebuild on change, etc...)