Skip to main content
Participant
November 13, 2022
Question

The SDKs do not appear to work well or at all within a Blazor Server environment

  • November 13, 2022
  • 2 replies
  • 597 views

I can confirm this because I extracted the core logic used into a Blazor WASM and even a console app, and it worked fine. These were .Net 6 version apps. Is there something about Signal-R that is interfering with the calls?

    This topic has been closed for replies.

    2 replies

    Participant
    June 5, 2023

    Hi,

    I also experienced this issue. I think it is the Signal-R issue. Because Signal-R is not dependent on http(s) protocols. Hence the communication goes blonkers. I trying to find any other work around. Three ways  1) JS Interop or 2) Create API  or 3) Background Services. Let me know your thoughts.

    Raymond Camden
    Community Manager
    Community Manager
    June 5, 2023

    I'd _highly_ recommend switching to the REST APIs if possible. 

    Participant
    April 27, 2023

    I can confirm after roughly 20 hours of testing and refactoring that the WordToPdf does not work with Blazor.  I am running .net 7 Blazor server.

    I had not tried the WordToPdf function, but for months I have had the ExcelToPdf conversion running in a production environment with no issues.

    Now I need to convert Word documents and it fails.


    This call:

    FileRef result = createPdfOperation.Execute(exc);

    goes out to lunch and never returns.

     

    Things I have tried:

    1) UnitTested : success

    2) Create a bare blazor server app and run this call : fails

    3) Create a separate dll to run this call (from the bare test app): fails

    4) Execute on new thread: fails

    5) Both Static and not Static class calls fail

    6) Stream or reading from file makes no difference

    Participant
    June 5, 2023

    Did you try Client config with timeout?