Trying to figure out what project preset type is best for deploying my project.
Could use some tips; I'm looking at deploying a project at work towards a Linux server. i currently have an ASP.NET Web API project (for the backend) and i've got an MVC project for the Frontend.
I've been recommended to use a Blazor app for the frontend; Which makes me wonder if it's generally considered good practice to place both the Front and Backend into the same Project for easier deployment? Or should i keep them separated in their own projects under the same Solution?
10 Replies
I wouldn't even put them in the same solution
Oh? How come?
All of the solutions has at least a backend and a frontend project under it. So i'm just following that.
Im new to Blazor so the question here is now if i do create a Blazor app for the frontend; should i redo the backend as well?
Uh really? I've never seen anyone benefit from splitting things into multiple solutions. Even Roslyn is one gigantic solution
We have things like solution filters for if solutions become too large. Noone recommends multiple solutions
Yeah, i dont think i've seen any projects be like that within our systems. Each Solution has at least a backend and a frontend, they're never separated like that. 😮
The backend needs multiple projects and the frontend needs multiple projects. I just think it's a lot more organized in 2 repos
+ tests and everything
Configs specific to front and backend
My rule of thumb for whether to split things into multiple repos is: do these different bits need to be released and versioned independently?
well in this instance there's just a backend and a frontend project that will be deployed. No Class libraries or SQL projects, as they are handled separately.
Would you guys:
A) Have a Blazor project for the frontend and keep the Backend in an ASP.NET Web API project
B) Integrate both frontend and backend into Blazor projects?
I think the idea of why they wanted Blazor was because they're trying to take a step back from JavaScript in their projects.
Either way, it's not something I'd recommend to someone out of the blue
In this instance they do not.
The backend and frontend are just there to showcase data coming from the database. So there's no separate versioning.
Yeah, exactly.