search

dotnet-presentations / blazor-workshop

Blazor workshop
https://aka.ms/blazorworkshop
MIT License
3.49k stars 1.55k forks source link

Any reason to have the Client and Server projects? #301

Closed raulandresduque closed 3 years ago

raulandresduque commented 3 years ago

Hello,

More than an issue, it is a doubt (I didn't find another point to comment on) ...

About the need of having two projects, one for the server (MVC) and the other one client (Blazor).

Any technical reason / best practice for it instead of having only one blazor project?

devjinjin commented 3 years ago

It is practice project. The project you saw is no longer in use.

My other git project path is below : https://github.com/codingzombie82/Service

Use dotnet core api + blazor client.

2021년 2월 5일 (금) 오후 12:28, Raul Duque notifications@github.com님이 작성:

Hello,

More than an issue, it is a doubt (I didn't find another point to comment on) ...

About the need of having two projects, one for the server (MVC) and the other one client (Blazor).

Any technical reason / best practice for it instead of having only one blazor project?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/dotnet-presentations/blazor-workshop/issues/301, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACLBLRNY45KHKT7Z5EGLM43S5NQVNANCNFSM4XEAF3LA .

devjinjin commented 3 years ago

It is practice project. The project you saw is no longer in use.

My other git project path is below : https://github.com/codingzombie82/AppService

Use dotnet core api + blazor client.

2021년 2월 5일 (금) 오후 2:14, 이진영 devjinjin@gmail.com님이 작성:

It is practice project. The project you saw is no longer in use.

My other git project path is below : https://github.com/codingzombie82/Service

Use dotnet core api + blazor client.

2021년 2월 5일 (금) 오후 12:28, Raul Duque notifications@github.com님이 작성:

Hello,

More than an issue, it is a doubt (I didn't find another point to comment on) ...

About the need of having two projects, one for the server (MVC) and the other one client (Blazor).

Any technical reason / best practice for it instead of having only one blazor project?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/dotnet-presentations/blazor-workshop/issues/301, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACLBLRNY45KHKT7Z5EGLM43S5NQVNANCNFSM4XEAF3LA .

lohithgn commented 3 years ago

@raulandresduque If i understand your question correctly - You are asking about BlazingPizza.Server & BlazingPizza.Client. Blazor WebAssembly has 2 hosting models:

In this workshop the second model is showcased. Plus the BlazingPizza.Server is also used to house the APIs powering the Blazor WebAssembly application (lile pizza api endpoint, order end point, toppings endpoint etc).

This is a typical practice followed by most people.

Hope this helps.

lohithgn commented 3 years ago

@raulandresduque if you think your questions is answered - please consider closing this issue. Thanks.