Activities of "alper"

According to the framework rules, you cannot disable the UnitOfwork pipeline. The only reason to disable the UnitOfWork is managing the UnitOfWork on your own with IUnitOfWorkManager with the following code

 using (var uow = _unitOfWorkManager.Begin(requiresNew: true, isTransactional: false ))
 {
        //.....
        await uow.CompleteAsync();
 }

You might want to disable transaction for the corresponding method. To do this basically add the following attribute

[UnitOfWork(isTransactional: false)]

If you really want to disable the UnitOfWork, you can use FindAsync() instead of FirstOrDefaultAsync()

Related document https://docs.abp.io/en/abp/latest/Unit-Of-Work

let us check it. subscribe the question to get email notification

@jackmcelhinney see => https://support.abp.io/QA/Questions/740/ObjectDisposedException-when-UnitOfWork-disable

Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling 'Dispose' on the context instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances.
Object name: XXXX

System.ObjectDisposedException: Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling 'Dispose' on the context instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances.
Object name: 'WebPlatformDbContext'.

@jackmcelhinney asks here

thanks we got your solution. it's under investigation.

you need to create the entity again. I guess you did so.

yes the command is correct. To fix that Blazor issue, see https://support.abp.io/QA/Questions/626/Bugs--Issues-v4X#answer-4c30b02d-0072-c6a2-5223-39f94063fb2b

I reproduced what you faced and created an issue to the team. sorry for the problem.

hi @Riley,

Our goal is to make the modules customizable with extension points and updatable without touching your business code. The balance between two are critical. Therefore any structural change on the razor page needs to be done within the module source-code. For example if you want to move an existing div into another one, you need the code. (I don't count making this via JavaScript). But some cosmetic changes can be done via CSS. In the link I sent you, explains how to add your custom CSS to the login page. So you can overwrite the existing styles (with CSS !important attribute).

For your specific example;

By doing the below, you add your custom CSS.

@section styles{
    <abp-style src="/Pages/Account/login.css" />
}

But if you need radical changes, you need the source code. By the way this is the latest login.cshtml (v4.1.0)

Also see this document. It explains UI Customization https://docs.abp.io/en/abp/latest/UI/AspNetCore/Customization-User-Interface

For the Angular part @Mehmet can answer it.

there's a 500 errror which means this request is handled and couldn't be executed nicely. there must be the log for it.

if you have no time to wait for v4.2, you can download the source-code and customize according to your requirements. when we release v4.2 you can go return back to the original package and customize it in the recommended way.