✅ (Why) should you use SpaServices.Extensions?
Spaservices extensions allows you to put a spa like angular inside your .net api and publish it at the same time. But why would u want this? Wouldnt you want more seperation instead?
4 Replies
I've done this several times already
For simpler applications I really didn't feel like setting up a CDN or a second dedicated app which hosts nginx with the SPA
I just leveraged the fact that I already have a web server running within my asp.net core app
The question is, when WOULD you want more separation?
are you developing an API to be publicly used?
by third parties?
are you developing an API to be used by many different client apps of your own?
if not, if this is one application with tightly-coupled server and client components, what purpose is served by not maintaining them together?
or, more interestingly
setting them up as separate deployments, under separate hosts?
Was this issue resolved? If so, run
/close - otherwise I will mark this as stale and this post will be archived until there is new activity.I totally forgot I made this post, but thank you for your responses. It's clear to me now