Layered Blazor WASM Solution - Cookie #9603

2 Answer(s)

• 

  0

  AI-Bot created 2 months ago

  Support Team ABP Agent

  To implement an ICurrentCompany service similar to ICurrentTenant in a layered Blazor WASM solution, you can follow these steps:

  1. Define the ICurrentCompany Interface:

  public interface ICurrentCompany
     {
         Guid? CompanyId { get; }
         string CompanyCode { get; }
         Task ChangeAsync(Guid companyId, string companyCode);
     }
  

  2. Implement the Service:

     • Store the selected company in a cookie (or local storage) on the client.
     • On the server, read the cookie and set the current company context for each request.

     Example implementation for Blazor WASM (client-side):

  public class CurrentCompany : ICurrentCompany
     {
         private readonly IJSRuntime _jsRuntime;
         private const string CompanyCookieName = "CurrentCompany";
  
         public Guid? CompanyId { get; private set; }
         public string CompanyCode { get; private set; }
  
         public CurrentCompany(IJSRuntime jsRuntime)
         {
             _jsRuntime = jsRuntime;
         }
  
         public async Task ChangeAsync(Guid companyId, string companyCode)
         {
             CompanyId = companyId;
             CompanyCode = companyCode;
             await _jsRuntime.InvokeVoidAsync("BlazorCookies.Set", CompanyCookieName, companyId.ToString());
             // Optionally store companyCode as well
         }
  
         public async Task InitializeAsync()
         {
             var companyIdString = await _jsRuntime.InvokeAsync<string>("BlazorCookies.Get", CompanyCookieName);
             if (Guid.TryParse(companyIdString, out var companyId))
             {
                 CompanyId = companyId;
             }
         }
     }
  

  • Use a JS interop library (like BlazorCookies) to manage cookies in Blazor WASM.

  3. Register the Service:

  builder.Services.AddScoped<ICurrentCompany, CurrentCompany>();
  

  4. Set the Company from the UI:

     • When a user selects a company from the dropdown, call ChangeAsync on your ICurrentCompany service.

  5. Server-Side:

     • On the backend, create a middleware or a custom provider to read the company cookie from the request and set the company context for the current user/session.
     • You can use a custom data filter similar to ABP's multi-tenancy filter to restrict data by company.

  6. Data Filtering:

     • Implement a custom data filter for company-based filtering, similar to how ABP handles multi-tenancy:

  public interface ICompanyFilter
       {
           Guid? CompanyId { get; }
       }
  

   - Apply this filter to your entities and queries.
  

  References for Custom Filters and Claims:

  • Defining Custom Filters
  • Claims Principal Factory
  • ABP Multi-Tenancy

  This approach aligns with ABP conventions for context services and data filtering, allowing you to change the current company at runtime and persist the selection in a cookie, similar to how tenants are managed.

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Save Cancel
• 

  0

  maliming created 2 months ago

  Support Team Fullstack Developer

  hi

  This article has a similar feature.

  You can check it

  https://abp.io/community/articles/switching-between-organization-units-i5tokpzt#gsc.tab=0

  Thanks.

  Save Cancel