Good Morning.

Will the Blazor UI still work after all these changes to the backend service?

Hi, yes the Blazor UI should still work. However, I am planning to build a POS Frontend completely on NextJs. Maybe I can build a dashboard app on Blazor as well.

Hi! You Refactor the frameworks again? v3? Good news :) .. I hope really want to show a complete framework including EventBus Messages, Microservices and Next.JS. A Complete framework in All in One Repository.. This template is very usefull for the community. Good Luck!!

In other hand, how are planned replace/add the MediaR and MassTransit (they will be comercial) ...? May be wolverinefx (https://wolverinefx.net/tutorials/from-mediatr.html), WolverineFX appears the natural lib to support both frameworks, mediators and message broker (with RabbitMQ)? , to avoid reinvent the whell and dedicate your limited time to another parts from the framework... What is your opinion? Thanks in advanced!

Another question, what motivate the new Project Phoenix, after a long period without any updated? Did you use this in the next solution or .NET courses?

Regards!

Hi @iammukeshm ! great job.. any estimated ETA?

Hi @iammukeshm ! great job.. any estimated ETA?

Same, just waiting for the next push, want to see the inter-module communication implementation. Would be of great help.

@iammukeshm, I loving this move away from mediator and embracing of vertical architecture.

Two thoughts.

1. Should infrastructure be a module or separate as in version Reasoning is that it contains cross cutting concerns and is used differently to a module. Program.js supports this thought with the separation of the two lines:

app.ConfigureFshFramework();
app.ConfigureModules();

2. Should request and responses be together with the other feature files rather than separate. Keeping them separate seems to go against the idea that vertical architecture keeps all files for a feature in one place.

Any new changes to Project Phoenix, anything need help with?

Please @iammukeshm .. the projects is dead? or give us the arquitecture guidelines ...so the community continue or help you to complete the project....

phoenix wake up, please

Hi @iammukeshm , we are waiting so long for this project ... Any update on this ?

Sorry guys for the delay. I had to take some personal time off. I am getting back into this, and no, the project is not dead! ;)
My current tasks are:

1. Analyzing the deps and framework
2. setting up extensions
3. working on intra module communication
4. setting up an example POS app with this framework and NextJs.

Very good, @iammukeshm!
A lot of people are waiting for this, including me.

Really good to hear about this.

Great news! Great! But it's 2025, with plenty of AI and Vibe Coding tools to accelerate this... So... I'm Googling for a .NET template + a Vibe Coding template to no avail... So... when I think it's a good opportunity, when this startup is complete or in beta, we can include some .MD files to give clear instructions to the AI agent to easily extend the architecture or define new features. Something like this: https://github.com/z3d/Starter-App-Dotnet-0/blob/main/CLAUDE.md

Imagine creating a message with VS Copilot like this: "Create a new brand CRUD with the attributes BrandId and Name. Please add the entities, DTO, and frontend changes to implement this feature. Add validation so the name doesn't exceed 100 characters." Blah, blah, blah, blah.
And the agent, knowing the project architecture and MD files, can code all the functionality.

What's the community's opinion on this feature?

I don't have much experience with AI agents. Do you have any ideas for leveraging tools like VS Copilot, Cursor, Windsoft, Claude, etc.?

Regards