Update to target .NET 5.0 with this PR: #39

It might be better idea to split the Blazor functionality to it's own issue as there are still things that should be investigated (for example where to load the plugins).

Hey there!

First I would like to state my appreciation for the project. From what I can see, it looks solid :)
We (as in my team and I) are very much looking forward to the .NET 5 version of the framework and plan to use in in our hosted WASM app.

Thus my questions would be, is there an ETA on the new version and is it going to fully support Webassembly?

In our research we also stumbled over this project which appears to have a similar focus but is missing the NuGet feed option, you guys have. Maybe there are some ideas that can be found here, if that helps.

Thanks in advance for the answer and for the project.

Kind regards,
Chris

Hey Chris,

Thank you for the message. We've been doing some work with the .NET 5 support and actually there's a PR which adds a support for it. But, like @mikkou-adafy suggested, we decided to split things into two:

• First we add the simpler stuff, meaning the basic .NET 5 support. This is basically done.
• Then we add better WASM Blazor support.

We have done some drafts related to WASM support but it is not the most straightforward thing to do properly. Compiling things on the fly or loading Nuget packages runtime are causing some issues at the moment.

Currently the ETA is February but I hope that we can release the first beta in the next couple of weeks.

Best regards,
Mikael

That sounds very promising. Thank you for the information. We are looking forward to the update :)

Sorry that things are slow with this one. Things are progressing, but currently we are in a little crunch phase in getting these two released: https://weik.io/apiframework/ & https://weik.io/eventframework/

The good news is that it's mainly the documentation which is missing.

Hi @mikoskinen any updates on the event framework?
I'm trying to build a system that will have 2 elements: ASP.NET 5 API and a windows console app, both on two separate machines.
The idea is that the API should act as a "proxy", so it should receive requests, pass them to the console app, wait for the responses and pass them to the API and finally the API should return them to the caller.
This will allow exposing data from systems that are behind firewalls or don't have a static IP.
I'd like to use your PluginFramework to be able to dynamically add/replace/remove endpoints from API and from console APP.

Not sure if this is the right place to ask, but I can't find a repo for the event framework.