Blazor | Please see the new repo | Frontend Framework library

Honestly, after days of research, I'm trying to talk the team into the idea of creating an API dedicated to Docs, and as part of that effort would migrate documents to AWS S3 or azure blob storage. We will introduce Aspose for rendering and separate the Issue.

Why? because all the solutions I have seen to support doc and Docx in .net5 are really hacky and I can see lacks in terms of security. And I would not recommend anyone to try to do the approach I was looking to do at the begging of this question.

I leave here what experience cause this research was pain and I hope this question can still help someone.

You need to include the using statement, either in the component.razor file, or in _Imports.razor (preferred if you are going to be using JSInterop often):

If the workSheetList object is null, I don't think it's a DLL problem - that would throw an Exception for a missing assembly. Is your "produitsTEST.xls" file on your QA server, and at the FilePath you specify? I would check that first.

I would also throw in some error handling in the event that workSheetList does come back as NULL.

You cannot apply a class to a Component. You can use splatting to capture attributes placed on a Component to pass as parameter to one of the components elements.

SomeComponent.razor

You dont have to use a setter. Just a computed property based on the bind value.

As far as I understood both your question and the Blazor concepts, the answer to your question is « no ». There is no possibility to retrieve statically the current HTTP context in Blazor. Because you never know if the context is an initial page load or just SignalR communication to update the current page. Here is the manner I save this situation:

• Create a cascading parameter that is shared by all razor components

• This cascading parameter is a class with many information coming from initial HTTP request, caught in the _Host.cshtml from the httpContextAccessor.HttpContext

• This cascading parameter class gets all the methods of my previous static methods.

• These methods can use the properties of the cascading parameter: RawUrl, UserAgent, ClientIp, …

This implies hard refactoring work to migrate legacy ASP web sites. But the performances of Blazor are worth it.

Finally got it running using the following code:

This is how I've been using Dapper. Works great:

1. Make your Dapper method async.
2. Make the method or event that CALLS your method an async Task as well, so you can await the Task.
3. To return a list, do return (await blah blah blah).ToList();
4. Use the Async versions of all SQL calls.

Something seems a little off with your foreach loop. Would you mind explaining what you're trying to achieve with it? It seems like your first query should return all the models you need.

Example:

You don't actually create a timer component as you post in the question title. What you actually want is to create a service class which you can inject into your components. You can do that in various ways, and provide whatever functionality you want.

Your timer service class may look something like this (Warning you should also implement the IDisposable interface to dispose the timer in order to prevent memory leaks):