Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request for Angular Alternative #710

Closed
KTarun003 opened this issue Sep 28, 2022 · 10 comments
Closed

Request for Angular Alternative #710

KTarun003 opened this issue Sep 28, 2022 · 10 comments

Comments

@KTarun003
Copy link

I would like to have an option to choose between major SPA's like React, Vue etc.

@damikun
Copy link

damikun commented Oct 6, 2022

I agree that decoupling FE and BE is good idea... Currently app is serverd as static from API project which has also advantages with CORS etc...

Decoupling can be done by moving Angular from API to custom FE folder and create custom registration for serving static files... ( UseAngularFre(...), UseReactFe(..)... )

What you will lost, is ability to start frontend with backend... Or if you require to keep behaviour, than you need to handle some paths how to strat FE with Backend...

@KTarun003
Copy link
Author

If we are serving static files , can we build our FE to a folder and serve that folder?. If we can , can we do it while development too?

@damikun
Copy link

damikun commented Oct 19, 2022

If we are serving static files , can we build our FE to a folder and serve that folder?. If we can , can we do it while development too?

Ofcourse you can.. dotnet has some templeates for react: 'dotnet new react' or something similar.. snd you can integrate clean architecture to that templeate..

@jasontaylordev
Copy link
Owner

Thanks for the suggestion. I am considering adding options for Web API only, Angular (existing), and React (new). I need to try it out first, I might not have the capacity to maintain so many options.

@ghost
Copy link

ghost commented Nov 6, 2022

@jasontaylordev I'm converting it to an Web API (only) right now. I would appreciate that feature. I'm working with React Native clients. It is proving to be somewhat of a challenge to get a Web API (only) published into Azure using this template.

@Van-Dame
Copy link

In my case, I chose a different FE (Svelte) and replaced Microsoft.AspNetCore.SpaProxy with AspNetCore.SpaYarp. Lets me decide whether to serve the FE as a part of API or as a separate launch with minimal changes/config.

@JohanHeyvaert
Copy link

JohanHeyvaert commented Nov 17, 2022

In my case, I chose a different FE (Svelte) and replaced Microsoft.AspNetCore.SpaProxy with AspNetCore.SpaYarp. Lets me decide whether to serve the FE as a part of API or as a separate launch with minimal changes/config.

Hello @Van-Dame,
That sounds like a nice solution!
Would you care to publish an example of that? We also consider migrating to Svelte 😄. Traditional frameworks like Angular and React seem to be slowly losing ground. Thanks in advance for considering!

@pflajszer
Copy link

pflajszer commented Dec 15, 2022

VS 2022 allows creation of the below:
image

... and respective tutorials to get those running with a standalone API project with info how to let those two apps communicate via proxy:

https://learn.microsoft.com/en-us/visualstudio/javascript/tutorial-asp-net-core-with-angular?view=vs-2022

image

@jasontaylordev
Copy link
Owner

I've added support for React in #872

@jasontaylordev
Copy link
Owner

Support for API only covered by #786

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants