Blazor Web App template issue #9964

5 Answer(s)

• 

  0

  AI-Bot created 21 days ago

  Support Team ABP Agent

  The issue you are experiencing with the Blazor Web App (tiered) template and InteractiveWebAssembly render mode is related to the remote service configuration for your CRUD page. In tiered ABP solutions, especially with Blazor WebAssembly or InteractiveWebAssembly, the client-side app communicates with the backend via HTTP API endpoints. If the remote service is not properly configured or exposed, you will encounter the "Could not find remote action for method" exception.

  Solution Steps

  1. Ensure RemoteService Attribute is Set Correctly
     • For your application service (e.g., BookAppService), make sure it is decorated with [RemoteService] (or not explicitly disabled). If you use [RemoteService(IsEnabled = false)], the service will not be exposed to the client, causing this error.
     • Example:

  [RemoteService] // or simply omit this if you want it enabled by default
       public class BookAppService : ApplicationService, IBookAppService
       {
           // ...
       }
  

  2. Check API Controller Generation

     • ABP automatically generates API controllers for application services marked as remote services. Ensure that your service interface and implementation are public and not internal.
     • If you have a custom controller, ensure it is properly routed and implements the correct interface.

  3. Verify API Endpoint Accessibility

     • Start your HttpApi.Host project and check the Swagger UI (e.g., https://localhost:44331/swagger). Ensure that the endpoint for your CRUD service (e.g., /api/app/book) is present and accessible.

  4. Check AppSettings for Remote Service Configuration

     • In your Blazor Web App's appsettings.json, ensure the RemoteService:BaseUrl is set to the correct API host URL.

  "RemoteService": {
         "BaseUrl": "https://localhost:44331"
       }
  

  5. Rebuild and Restart All Projects

     • After making changes, rebuild the solution and restart both the HttpApi.Host and Blazor Web App projects to ensure all changes are applied.

  6. Known Issue with Module Template

     • There is a known issue where the module template does not set up the remote service correctly for tiered apps. If you used the module template, you may need to manually add the [RemoteService] attribute or check the generated code for missing configuration.
     • Reference: https://abp.io/support/questions/4300

  Additional Notes

  • If you have both a controller and an app service, ensure that at least one is exposed as a remote service for the client to access.
  • A clean and rebuild of the solution can sometimes resolve issues after upgrades or template changes (see: https://abp.io/support/questions/1735).

  ---

  Sources:

  • https://abp.io/support/questions/4300
  • https://abp.io/support/questions/1735

  ---

  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 21 days ago

  Support Team Fullstack Developer

  hi

  I will check this case.

  Thanks.

  Save Cancel
• 

  0

  maliming created 21 days ago

  Support Team Fullstack Developer

  hi

  Please try to use AddStaticHttpClientProxies in your .HttpApi.Client project,

  context.Services.AddStaticHttpClientProxies(
      typeof(AbpSolution1ApplicationContractsModule).Assembly,
      RemoteServiceName
  );
  

  .HttpApi.Client> abp generate-proxy -t csharp -m app --url https://localhost:44332 --without-contracts

  https://localhost:44332 is your api website url.

  

  Thanks

  Save Cancel
• 

  0

  marek.sidlo created 21 days ago

  That works, thanks. :)

  Will there be some fix with dynamic proxies in template itself?

  Save Cancel
• 

  0

  maliming created 21 days ago

  Support Team Fullstack Developer

  Hi

  I will fix it in template. Thanks

  Save Cancel